Feature request: allow renaming/labeling conversations
Resolved 💬 2 comments Opened Mar 31, 2026 by lina-saleh Closed Apr 23, 2026
Summary
There's no way to rename or label a Claude Code conversation. Sessions are identified only by internal IDs, which makes it difficult to find and return to specific conversations — especially when running multiple concurrent terminals on different workstreams.
Use case
- Running parallel terminals on different tasks (e.g., one for frontend work, one for infra)
- Returning to a prior session days later and needing to identify it by topic
- General session management when conversation count grows
Proposed behavior
Allow users to assign a human-readable name/label to a conversation, e.g.:
/rename "Fortify auth middleware refactor"
The name would appear in /conversations output and any session-listing UI (VS Code sidebar, web app, etc.).
Alternatives considered
- Manual tracking via external notes or scratchpad files — works but adds friction
- Session journals — useful for context reconstruction but doesn't solve the discoverability problem in the conversation list itself
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗