Terminal Tab Title Setting / Claude Code v2.1.26

What

New terminalTitleFromRename boolean setting that controls whether the terminal tab title is pinned to the value from /rename or auto-updated based on conversation topic.

Usage

Set in settings.json or settings.local.json:

{
  "terminalTitleFromRename": true
}

Details

When true, the terminal tab title is set from /rename and not auto-updated based on the conversation topic
When false or absent, the previous auto-update behavior continues
This is useful for users who use /rename to set a meaningful session name and don't want it overwritten

Evidence

Zod schema setting description (search for "terminal tab title is set from /rename")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.26 →

The build it came inv2.1.26

30 Jan 2026 · 12 entries, this one is #2.

Either side of it

v2.1.25Older
v2.1.27Newer

Open the release →

Names in this entry

settingterminalTitleFromRename
Stop /rename and --name from changing the terminal tab title
slash/rename
Rename the current session and show the name on the prompt bar. Without a name, auto-generates one from conversation history. Also available in non-interactive mode (-p); requires Claude Code v2.1.205 or later. From every rename surface, including claude.ai and the desktop app, Claude Code replaces control and invisible characters in the new name with spaces and caps the name at 200 characters. If the name is empty once invisible characters are removed, Claude Code rejects it and shows That name is empty once invisible characters are removed. Usage: /rename <name>. The character replacement and length cap require Claude Code v2.1.221 or later. If another live session on this machine already uses a name you pass, Claude Code applies a variant of it instead
settingsettings.json
Resumed sessions now carry your settings files along, with plugin registrations stripped out.
settingsettings.local.json
The runner can warn about or block repo-committed settings that grant access outside the workspace.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.47 Improved /rename Behavior Setting