[BUG] --name doesn't match the behavior of /rename

Resolved 💬 3 comments Opened Mar 18, 2026 by mauriziodepascale Closed Mar 22, 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?

--name and /rename both set a session name, but they produce different UI results:

executing /rename foo
displays the name with a blue border around the input box

while launching with --name "foo"
only sets the terminal title bar, no blue border

What Should Happen?

Since both features serve the same purpose (naming a session), --name should produce the same blue-border result that /rename does.

Error Messages/Logs

Steps to Reproduce

  1. run a claude code session with this argument:

--name foo
the session is named foo, and that name is also visible on the terminal title.
however, the input box at the bottom keeps the same format (two gray lines).

  1. inside a claude code session execute the command:

/rename foo
the session becomes named foo, that name is visible on the terminal title.
in addition the input box becomes blue and clearly shows the session name on the right in the same color.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.77 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

/rename
<img width="296" height="323" alt="Image" src="https://github.com/user-attachments/assets/5fd313bd-f7ac-4ec0-8ee2-b27f43824884" />

--name
<img width="296" height="323" alt="Image" src="https://github.com/user-attachments/assets/267ee245-e753-41e3-b980-8d97782384e7" />

View original on GitHub ↗

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