[Feature Request] Add customizable color styling for user input messages
Bug Description
Problem:
In the Claude Code CLI, user input messages and Claude's responses have similar visual styling, making it difficult to quickly distinguish between them when
scrolling through a conversation.
Requested Feature:
Allow users to customize the color of their own chat messages in the Claude Code CLI. Specifically:
- Background color of user input messages (e.g., yellow)
- Text color of user input messages (e.g., black)
Use Case:
When reviewing a long conversation, users need to quickly locate their own questions/prompts. Currently, the similar color scheme between user messages and assistant
responses makes this difficult. Custom colors would provide clear visual separation.
Suggested Implementation:
A new configuration option in settings.json or via a /theme command extension, such as:
{
"theme": {
"userMessage": {
"backgroundColor": "yellow",
"textColor": "black"
}
}
}
Current Workaround:
None. The /theme command only affects syntax highlighting in Claude's responses, not user input message styling.
Environment Info
- Platform: darwin
- Terminal: WarpTerminal
- Version: 2.1.37
- Feedback ID: f3940c5f-0021-4e6b-8f09-c33ad7d7f39a
Errors
[{"error":"Error: ENOENT: no such file or directory, open '/Users/jaegu/.claude/remote-settings.json'\n at openSync (unknown)\n at <anonymous> (/$bunfs/root/claude:12:947)\n at oC (/$bunfs/root/claude:11:49132)\n at readSync (/$bunfs/root/claude:12:875)\n at tC (/$bunfs/root/claude:6113:113)\n at TC (/$bunfs/root/claude:6115:226)\n at BAA (/$bunfs/root/claude:178:8143)\n at xBR (/$bunfs/root/claude:178:8306)\n at gKD (/$bunfs/root/claude:179:1202)\n at zAT (/$bunfs/root/claude:179:2080)","timestamp":"2026-02-09T18:18:18.537Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/jaegu/.local/share/claude/versions/2.1.37 (expected in multi-process scenarios)\n at GFR (/$bunfs/root/claude:3584:2098)\n at ebA (/$bunfs/root/claude:3584:1209)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-09T18:18:18.674Z"},{"error":"Error: Tool ToolSearch not found\n at Qa_ (/$bunfs/root/claude:1856:5796)\n at g1 (/$bunfs/root/claude:656:20780)\n at F6 (/$bunfs/root/claude:656:39182)\n at yb (/$bunfs/root/claude:656:49801)\n at dx (/$bunfs/root/claude:656:86058)\n at iT (/$bunfs/root/claude:656:86030)\n at rdT (/$bunfs/root/claude:656:85872)\n at td (/$bunfs/root/claude:656:81269)\n at nR (/$bunfs/root/claude:656:6275)\n at z0A (/$bunfs/root/claude:649:13953)","timestamp":"2026-02-09T18:18:29.697Z"},{"error":"Error: Tool ToolSearch not found\n at Qa_ (/$bunfs/root/claude:1856:5796)\n at g1 (/$bunfs/root/claude:656:20780)\n at F6 (/$bunfs/root/claude:656:39182)\n at yb (/$bunfs/root/claude:656:49801)\n at dx (/$bunfs/root/claude:656:86058)\n at Se (/$bunfs/root/claude:656:85032)\n at Ap (/$bunfs/root/claude:656:84857)\n at td (/$bunfs/root/claude:656:81277)\n at nR (/$bunfs/root/claude:656:6275)\n at z0A (/$bunfs/root/claude:649:13953)","timestamp":"2026-02-09T18:18:29.753Z"},{"error":"Error: Tool ToolSearch not found\n at Qa_ (/$bunfs/root/claude:1856:5796)\n at g1 (/$bunfs/root/claude:656:20780)\n at F6 (/$bunfs/root/claude:656:39182)\n at yb (/$bunfs/root/claude:656:49801)\n at dx (/$bunfs/root/claude…
Note: Content was truncated.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗