[BUG] NEed an ability to rename the claude code sessions

Resolved 💬 9 comments Opened Jul 16, 2025 by tushar2708 Closed Jan 21, 2026

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.53 (Claude Code)
  • Operating System: macOS 15.5
  • Terminal: iTerm2 / MAc Terminal

Bug Description

Currently, once resumed, a session gets a very generic name in the "claude --resume" list. Currently, we don't have a way to explicitly rename the session, but for new sessions, there's a partial workaround, that name gets decided by the first question. Ideally, we should be able to name a session, so that resuming itis eariser, instead of going of hit and trial. But the resumed session overwriting that name makes it harder, even without this feature.

Steps to Reproduce

  1. Start a session, do some work and close it.
  2. Resume it (for now, it has somewhat sensible name in the "--resume" list), and then close it again.
  3. Close it again, and then try to resume. All the sessions that go through this flow, end up with a generic "This session is being continued from a previous conversation..." name.
  4. Even timestamp doesn't help, if there were multiple sessions resumed around the same time. (very common, when resuming work after a system or IDE restart)

Expected Behaviour

  1. We should persist the session name, even after resume.
  2. Even better, we should either have a way to explicitly give a name to a session (which persists across resuming)

Actual Behavior

Session names are lost after resume.

Additional Context

<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->

View original on GitHub ↗

This issue has 9 comments on GitHub. Read the full discussion on GitHub ↗