[FEATURE]

Preflight Checklist

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

Problem Statement

Claude Code supports setting a session color via /color interactively, but there is no way to set it at launch time via a CLI flag. This makes it impossible to automate — shell scripts and
launchers that start Claude for a specific project cannot pre-set the color without human interaction inside the running session.

Proposed Solution

Add a --color CLI flag accepting a hex color string:

claude --color ddbb33

This would apply the same effect as /color but at startup, making it scriptable. A project launcher could then do:

# launch Claude for the SASE project with yellow
claude --color ddbb33 --name “project1"

# launch Claude for the main project with green
claude --color 55cc77 --name “project2"

Alternative Solutions

Currently the only workaround is to launch Claude and manually type /color inside the session. This cannot be automated. There is no way to pass the color as a startup argument.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Use Case Example

1. User has a shell script or launcher per project that starts Claude Code
2. Each launcher passes --color <hex> corresponding to the project
3. Claude Code starts with that color already applied — no need to type /color manually
4. Multiple Claude sessions across different projects are immediately visually distinct from launch

Additional Context

The /color command already exists and works well. This request is purely about exposing that same capability as a CLI flag so it can be set before the interactive session begins, enabling automation.