claude-code - 💡(How to fix) Fix Feature Request: Add defaultSessionColor setting to auto-apply color on startup [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50806Fetched 2026-04-20 12:12:33
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When starting Claude Code sessions, I need to manually run /color green each time to apply my preferred session color. This is a repetitive friction point in my workflow. There's no way to set a persistent default session color across all sessions, so I have to remember to run the command at the start of every session or accept the default color. This is especially frustrating in projects where I use session color as a visual indicator (e.g., green for production work, red for experimental work).

Proposed Solution

Add a defaultSessionColor setting to Claude Code's configuration files (.claude/settings.json, .claude/settings.local.json, or ~/.claude/settings.json) that automatically applies a color when a session starts.

Example: { "defaultSessionColor": "green" }

The session color would apply automatically without requiring a manual /color command. The user should still be able to override it with /color during the session if needed.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I'm working on the calendar-simple library project. I want all my sessions in this project to start with a green color to visually distinguish them from other projects (which might use different colors).

Current workflow:

  1. Start Claude Code session
  2. Type /color green manually
  3. Begin work

Desired workflow:

  1. Start Claude Code session (automatically green)
  2. Begin work

This saves a small repetitive step and reduces mental overhead, especially useful when switching between multiple projects with different color schemes.

Additional Context

  • The /color command already exists and works perfectly; this would simply automate it on session start
  • Similar to how other settings like model, theme, and language have defaults that apply automatically
  • This aligns with Claude Code's philosophy of reducing friction through configuration
  • Could support: "defaultSessionColor": "green" or potentially null/undefined to disable auto-coloring

extent analysis

TL;DR

Implementing a defaultSessionColor setting in Claude Code's configuration files could automate the application of a preferred session color.

Guidance

  • Consider adding a defaultSessionColor property to the .claude/settings.json, .claude/settings.local.json, or ~/.claude/settings.json configuration files to store the user's preferred session color.
  • Consider how the existing /color command could be integrated with the proposed defaultSessionColor setting to allow for both automated and manual color changes.
  • Evaluate how to handle cases where a user wants to override the default session color with a different color during a session.
  • Review Claude Code's configuration handling to ensure seamless integration of the new defaultSessionColor setting.

Example

{
    "defaultSessionColor": "green"
}

This example shows how a user might configure their default session color in a Claude Code configuration file.

Notes

The proposed solution aligns with Claude Code's existing configuration philosophy and could reduce user friction. However, the implementation details, such as how to handle overrides and potential conflicts, need careful consideration.

Recommendation

Apply workaround by manually running the /color command until the defaultSessionColor setting is implemented, as this allows users to still achieve their desired workflow, albeit manually.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING