[BUG] /rename session name is lost when conversation is auto-continued due to context limit

Resolved 💬 3 comments Opened Mar 31, 2026 by iripple Closed Apr 3, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When a conversation reaches the context limit and is automatically continued with a summary, the custom session name set via /rename is reset. The resumed session no longer shows the user-defined name in the /resume picker.

What Should Happen?

The custom session name set via /rename should persist across context continuations.

Error Messages/Logs

Steps to Reproduce

  1. Start a session: claude
  2. Rename it: /rename my-task-name
  3. Verify the name appears correctly in /resume picker — works as expected
  4. Continue working until the conversation hits the context limit and auto-continues with a summary
  5. Exit the session
  6. Run /resume — the custom name my-task-name is gone, replaced by auto-generated name

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.1.88

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

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