Allow persisting /color setting per-project in settings.json
Resolved 💬 2 comments Opened Mar 26, 2026 by dacox Closed Mar 26, 2026
Feature Request
Allow the /color session color to be persisted in settings files (e.g., settings.json or settings.local.json) so it automatically applies when opening Claude Code in a specific project.
Use Case
When working across multiple repos, it's helpful to visually distinguish sessions by color. Currently /color blue must be run manually every time a new session starts. A persistent setting would make this automatic.
Proposed Solution
Add a color field to the settings schema:
{
"color": "blue"
}
This could be set in any settings scope:
~/.claude/settings.json(global default).claude/settings.json(project-wide).claude/settings.local.json(personal per-project)
Alternatively, make /color work from a SessionStart hook.
Current Behavior
/color blueworks per-session but resets on next session- No
colorfield exists in the settings schema SessionStarthooks cannot invoke internal CLI commands like/color
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗