Preflight Checklist
Problem Statement
When working in Claude Code for extended sessions, I can't visually distinguish my input from Claude's output. Both use the same text color in the terminal. During long conversations with many back-and-forth
exchanges, I lose track of where my messages are versus Claude's responses. This slows me down -- I have to mentally parse every line to figure out who said what. A simple color distinction between user input and AI
output would make the conversation immediately scannable.
Proposed Solution
▎ Add a configurable color for user input text in the Claude Code terminal. Either a distinct default color (e.g. a subtle blue or green tint for user messages) or a setting in ~/.claude/settings.json like
"userInputColor": "#5E6AD2". The AI response text stays the current default. This is how chat interfaces (Slack, iMessage, every LLM chat UI) solve this -- your messages are visually distinct from the other party's.
The terminal already renders markdown formatting in Claude's output, so text styling infrastructure exists.
Alternative Solutions
▎ 1. A subtle prefix or gutter indicator (e.g. a colored bar or > character) next to user input lines, similar to how git diff shows additions/deletions
▎ 2. A background highlight on user input lines (subtle, like rgba(255,255,255,0.03)) rather than changing text color
▎ 3. Leverage the terminal's existing ANSI dim/bold -- render user input as bold and AI output as normal weight (or vice versa)
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response
Preflight Checklist
Problem Statement
When working in Claude Code for extended sessions, I can't visually distinguish my input from Claude's output. Both use the same text color in the terminal. During long conversations with many back-and-forth
exchanges, I lose track of where my messages are versus Claude's responses. This slows me down -- I have to mentally parse every line to figure out who said what. A simple color distinction between user input and AI
output would make the conversation immediately scannable.
Proposed Solution
▎ Add a configurable color for user input text in the Claude Code terminal. Either a distinct default color (e.g. a subtle blue or green tint for user messages) or a setting in ~/.claude/settings.json like
"userInputColor": "#5E6AD2". The AI response text stays the current default. This is how chat interfaces (Slack, iMessage, every LLM chat UI) solve this -- your messages are visually distinct from the other party's.
The terminal already renders markdown formatting in Claude's output, so text styling infrastructure exists.
Alternative Solutions
▎ 1. A subtle prefix or gutter indicator (e.g. a colored bar or > character) next to user input lines, similar to how git diff shows additions/deletions
▎ 2. A background highlight on user input lines (subtle, like rgba(255,255,255,0.03)) rather than changing text color
▎ 3. Leverage the terminal's existing ANSI dim/bold -- render user input as bold and AI output as normal weight (or vice versa)
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response