[Feature Request] Persist prompt color across sessions via settings.json
Status Open
Reported on v2.1.75
Maintainer reply None cached
Activity 6 comments · opened Mar 13, 2026
Bug Description
Feature request: Persist /color across sessions via settings.json
Currently /color is session-only with no way to persist it. It would be great to have a promptColor setting in .claude/settings.json
(both user-level and project-level), so different projects can automatically get their own color.
Use case: I work across multiple Obsidian vaults and project directories. I already use different terminal themes per project, but having
the Claude prompt bar color persist per project would make session identification even easier.
Suggested implementation:
- Add
promptColorto settings.json schema - Project-level settings.json overrides user-level
- /color command updates the setting when used (optional)
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.1.75
- Feedback ID: 1b07a720-ed7c-4617-ae8a-ae84f9602c9d
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1 — Another use case: if
promptColoris available in settings.json, custom statusline scripts can dynamically read it and apply matching colors to elements like the project name or other indicators. Right now there's no way for a statusline script to access the session color, so any color-coding has to be hardcoded and manually updated every time the color changes. Having it in settings.json (especially per-project) would let statusline scripts automatically pick up color changes, making it easy to unify the overall look and reflect personal color preferences across the entire UI without any manual intervention.+1 — this would pair nicely with
--setting-sources project,localfor per-project visual identity. Each project directory gets its ownsettings.json, so apromptBarColorthere would mean different projects automatically get distinct colors without manual/coloreach session.Would love this to support per-project configuration (in
.claude/settings.json, not just global). Being able to visually differentiate repos at a glance — e.g. a distinct color when working in a workspace vs. a specific project — would be a nice quality-of-life improvement.Bonus idea: support a per-repo ASCII art thumbnail that displays alongside the Claude logo during a session. A small visual identity for each project — you'd know exactly where you are at a glance without reading the path.
+1 We update our app icon with a colour based on the worktree path to help differentiate when running multiple versions of the app at the same time, it would be very nice to sync that with the Claude settings to match app icon colour to Claude session colour, and persisting the colour would be a pre-requisite for doing that.
+1 on this