[BUG] /clear inherits the previous conversation's /rename name instead of starting a fresh conversation

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 24, 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?

I'm reporting a bug in Claude Code CLI v2.1.280.

After I use /rename to set a custom name for the current conversation and then run /clear to start a new conversation, the new conversation inherits the old custom name. Since /clear is supposed to start a new conversation, this looks like a bug.

What Should Happen?

The new conversation should start with a fresh/default name. The custom name set with /rename on the previous conversation should not carry over.

Error Messages/Logs

Steps to Reproduce

  1. Start a conversation in Claude Code.
  2. Run /rename <custom-name> to rename the current conversation.
  3. Run /clear to start a new conversation.
  4. Check the name of the new conversation.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.1.280

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗