Preflight Checklist
Problem Statement
When working on multiple projects or tasks, I rely on the conversation history to revisit previous sessions. However, the auto-generated titles are often vague or unhelpful (e.g., "explain this function", "fix bug"), making it difficult to identify the right conversation later.
There is currently no way to rename or edit these titles. The /rename command returns "Unknown skill", and pressing R in the session picker opens the search field instead of a rename action.
Being able to set a meaningful title (e.g., "auth-refactor", "payment-integration") would significantly improve the experience of navigating conversation history.
Proposed Solution
I'd like two ways to rename a conversation:
-
During an active session:
- Type
/rename my-new-title to rename the current conversation
- A confirmation message appears: "Session renamed to 'my-new-title'"
-
From the history/session picker:
- Open history list via
/resume or the UI
- Hover or navigate to a conversation
- Press
R or click a rename icon to edit the title inline
- Type the new name and press Enter to confirm
The renamed title should persist and be searchable in the history list.
Alternative Solutions
I haven't found any viable workaround. The only options currently are:
- Starting a new conversation with a clear first message, hoping the auto-generated title will be descriptive enough
- Scrolling through the history list and previewing each conversation to find the right one
Neither of these is practical when you have many conversations across different projects.
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
Scenario: Working on multiple features across a project
-
I start a Claude Code session to refactor the authentication module. The auto-generated title becomes something like "help me with this code".
-
Later, I start another session to fix a payment bug. Its title becomes "there's a bug here".
-
The next day, I need to revisit the auth refactoring session to continue the work.
-
I open the history list and see:
- "help me with this code"
- "there's a bug here"
- "explain this function"
- "fix this error"
-
I can't tell which one is which. I have to open and preview each conversation to find the right one.
Additional Context
Similar features in other tools:
- ChatGPT: Allows renaming conversations by clicking on the title in the sidebar
- GitHub Copilot Chat in VSCode: Allows renaming chat sessions from the history panel
- Cursor AI: Supports renaming composer/chat sessions
These are all AI coding assistants with conversation history, and renaming is a standard feature across all of them.
No special technical constraints expected — the title is likely stored as a simple string in the session metadata and just needs an edit mechanism exposed to the user.
Preflight Checklist
Problem Statement
When working on multiple projects or tasks, I rely on the conversation history to revisit previous sessions. However, the auto-generated titles are often vague or unhelpful (e.g., "explain this function", "fix bug"), making it difficult to identify the right conversation later.
There is currently no way to rename or edit these titles. The
/renamecommand returns "Unknown skill", and pressingRin the session picker opens the search field instead of a rename action.Being able to set a meaningful title (e.g., "auth-refactor", "payment-integration") would significantly improve the experience of navigating conversation history.
Proposed Solution
I'd like two ways to rename a conversation:
During an active session:
/rename my-new-titleto rename the current conversationFrom the history/session picker:
/resumeor the UIRor click a rename icon to edit the title inlineThe renamed title should persist and be searchable in the history list.
Alternative Solutions
I haven't found any viable workaround. The only options currently are:
Neither of these is practical when you have many conversations across different projects.
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
Scenario: Working on multiple features across a project
I start a Claude Code session to refactor the authentication module. The auto-generated title becomes something like "help me with this code".
Later, I start another session to fix a payment bug. Its title becomes "there's a bug here".
The next day, I need to revisit the auth refactoring session to continue the work.
I open the history list and see:
I can't tell which one is which. I have to open and preview each conversation to find the right one.
Additional Context
Similar features in other tools:
These are all AI coding assistants with conversation history, and renaming is a standard feature across all of them.
No special technical constraints expected — the title is likely stored as a simple string in the session metadata and just needs an edit mechanism exposed to the user.