Feature: Auto-name and auto-color new sessions
Resolved 💬 3 comments Opened Apr 5, 2026 by xmd512 Closed Apr 9, 2026
Problem
There's no way to automatically name or color new Claude Code sessions. Currently, /rename and /color are interactive-only commands that must be invoked manually each time.
Users who want differentiated sessions (e.g., when running multiple sessions in parallel) have to remember to run these commands at the start of every conversation. The only workaround is adding a prompt instruction in CLAUDE.md asking Claude to remind the user — which is fragile and easy to forget.
Proposed Solution
Support automatic session naming and coloring via one or more of the following:
- Settings-based auto-naming — a config option (e.g.,
autoNameSession: true) that generates a random memorable name (e.g., "crimson-falcon") and color on session start. - Programmatic access to
/renameand/color— allow these to be called fromSessionStarthooks so users can script their own naming logic. - CLI flags — e.g.,
claude --session-name "my-task" --session-color blueto set name/color at launch.
Use Case
- Running multiple Claude Code sessions simultaneously and needing to visually distinguish them.
- Keeping session history organized and identifiable.
- Automating workspace setup without manual steps each time.
🤖 Generated with Claude Code
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗