--name flag does not display TUI session badge
Status Fixed / completed
Maintainer reply ✓ Yes — ashwin-ant
Activity 3 comments · opened Apr 16, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Description
The --name CLI flag sets the session name in metadata (visible in /resume picker and in the session JSONL as customTitle) but does not display the session name badge in the bottom-right corner of the TUI.
The /rename slash command sets the same customTitle field AND displays the badge. Expected behavior: --name should also display the badge.
Steps to reproduce
- Launch Claude Code with
--name:claude --name myname - Observe: no session badge in the bottom-right of the TUI
- Type
/rename mynamein the same session - Observe: cyan badge appears in the bottom-right
Expected behavior
--name myname should display the same TUI badge as /rename myname.
Evidence
Session JSONL confirms --name correctly writes {"type": "custom-title", "customTitle": "myname"} as the first record. The data is there, just not rendered in the TUI.
Environment
- Claude Code (latest, installed via CLI)
- macOS 15.7.4 (Sequoia), Apple M4
- Terminal: Ghostty
Screenshots
Without badge (--name only)
The status bar shows the project folder but no session name badge in bottom-right:
Opus 4.6 1M | 📁 tigh | 🌿 main ● | ⚡ 4.7% · 46.5k tokens
▸▸ bypass permissions on (shift+tab to cycle)
With badge (after /rename)
Same session after running /rename tigh — cyan badge appears bottom-right:
Opus 4.6 1M | 📁 tigh | 🌿 main ● | ⚡ 4.7% · 46.5k tokens [tigh]
▸▸ bypass permissions on (shift+tab to cycle)
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This was fixed in v2.1.113 — Sessions started with
--namenow display the session name badge in the prompt box from startup. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.