Rename the conversation
Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 13 comments · opened Sep 11, 2025 · closed Jan 9, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Claude Code conversations cannot be renamed after they are created. Users are limited to conversation management through /clear and /compact commands, but have no way to organize or identify conversations with meaningful names.
Users should be able to rename conversations to help organize their work sessions with descriptive names (e.g., "Bug Fix - Authentication", "Feature - Dark Mode", "Refactor - Database Layer").
Proposed Solution
Add a /rename slash command that allows users to update the conversation title:
/rename "New Conversation Name"
Implementation suggestions:
- Command should accept quoted strings to handle names with spaces
- Provide confirmation message when rename is successful
- Consider adding /name as an alias for consistency
- Optional: Show current conversation name before renaming
- Optional: Add validation for name length/characters
Alternative Solutions
Alternative approaches:
- Add rename option to conversation management UI (if applicable)
- Allow setting name during conversation creation
- Provide /info command to show current conversation metadata
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
13 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Hey, this is a great feature request. I've often found myself wanting the exact same thing to better organize my sessions.
From what I can tell in the docs, the current way to manage past sessions is with
claude --resume(orclaude -r). When you run that, it brings up a list of your recent conversations and tries to identify them using the "initial prompt or conversation summary."So, as a temporary workaround, what I've been doing is starting my sessions with a really descriptive first prompt that acts like a title. For example:
Then, when I run
claude --resume, that descriptive prompt shows up in the list and makes it much easier to find the right session to jump back into.It's not as clean as a dedicated
/renamecommand, but it helps a lot. A proper rename feature like you're suggesting would be a huge improvement for managing multiple workstreams.Fingers crossed the team sees this and adds it to the roadmap
I also was about to submit this feature request. We really need this because when I use the resume feature, a lot of times the sentence is, "this is from a previous conversation", which isn't useful. And often I have to guess which conversation.
Please add this. Please.
It was an interesting decision to just use the first few lines of the jsonl. For the time being, we just need to remember to actually title our prompts with the first thing we say. And that is fine. Probably good habit anyway.
@bZichett That works until you reach the conversation limit, I've raised this as a follow-up from this issue, here: https://github.com/anthropics/claude-code/issues/12613
Also, threads are often renamed to some unusable text from the IDE, like:
<ide_opened_file>The user opened the file /Users/patrick/theapp/familydiagram/pkdiagram/resources/qml/Personal/DiscussView.qml in the IDE. This may or may not be related to<ide_opened_file>The user opened the file /Users/patrick/theapp/btcopilot/btcopilot/personal/routes/diagrams.py in the IDE. This may or may not be related to the current tas…This session is being continued from a previous conversation that ran out of context. The conversation is summarized below: Analysis: Let me analyze the conversation chronol…So it is not possible to tell conversations apart. I would say resuming is unusable in this context. Being able to try one and then rename it accordingly would be a nice workaround for this.
While this doesn't land on main CLI, feel free to check out this lil wrapper I released recently: https://github.com/fgrehm/clotilde. It has support for naming chats and also for forking.
</shameless-plug>That seems quite... perfect. I will give it a try.
I see the following line in the CHANGELOG file, but I do not see the slash command even after updating to the latest version of CC (2.0.64):
Added named session support: use /rename to name sessions, /resume <name> in REPL or claude --resume <name> from the terminal to resume themhttps://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
I updated to 2.0.65 and can see the slash command.
<img width="779" height="294" alt="Image" src="https://github.com/user-attachments/assets/12808465-56be-4810-9d10-7e2e135d88af" />
I have raised a similar issue here: https://github.com/anthropics/claude-code/issues/12613 — shall we get it closed or any chances we can still improve this feature?
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.