[Feature Request] Allow programmatic session naming via CLI flag or model tool
Resolved 💬 3 comments Opened Jan 29, 2026 by KahunaCodes Closed Feb 2, 2026
Currently, the only way to name a conversation is via the interactive /rename slash command typed manually by the user. This limits automation and workflow integration.
Requested capabilities (either or both):
- CLI flag --name — Set a session name at launch:
claude --name "auth-refactor" --resume
- This would enable scripts, wrappers (like tm/cc session managers), and automation tools to create meaningfully-named sessions without manual interaction.
- Expose a rename tool to the model — Allow the AI to name/rename the current session programmatically. This would enable the model to auto-name conversations based on the task being
performed (e.g., after the user describes what they want to work on).
Use cases:
- Status line integrations that display session names — the name needs to exist for this to be useful, and manual naming adds friction
- Session management scripts that create pre-named sessions for specific projects/tasks
- Auto-naming workflows where the model names the session based on context (e.g., "statusline-setup" after configuring the status line)
- Cross-machine session tracking where human-readable names matter more than UUIDs
Current workarounds:
- Manual /rename after session start (friction, easy to forget)
- --session-id accepts UUIDs but not human-readable names
- No config, env var, or hook mechanism available
Platform: macOS (darwin), Claude Code 2.1.23
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗