Light mode ANSI theme uses color7 for both code text and UI backgrounds, making it unusable with standard palettes

[vcekron]

Problem

In "Light mode (ANSI colors only)", color7 (ANSI white) is used for:

• Code default tokens in diffs (needs to be dark to read on a light background)
• Command bar / message bar backgrounds (needs to be light)
• Input box borders and status bar separators

No single value works for all three. A standard light palette sets color7 to near-white, making code text invisible against the background. Setting it dark makes code readable but produces dark message bars.

Dark mode doesn't have this problem

"Dark mode (ANSI colors only)" correctly separates these concerns: color7 = code text / UI foreground, color8 = message background. They are independently tunable.

Suggested fix

Light mode should match the dark mode approach and ANSI conventions:

• color0 (ANSI black) for code default tokens — dark on light background is natural
• color7 (ANSI white) for backgrounds only — light on light is natural

Workaround

Use "Dark mode (ANSI colors only)" on a light terminal. Since dark mode doesn't use color1–6, they remain at standard values for other terminal apps.

Environment

• Claude Code v2.1.87
• kitty terminal, macOS
• Tomorrow Light color scheme

[github-actions]

Found 2 possible duplicate issues:

1. Light (ANSI only) theme uses ANSI white for syntax, invisible on light terminals #40071
2. [Bug] Text illegibility in Ghostty light theme #22574

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[yurukusa]

Good analysis of the color7 collision. Until Anthropic separates the color roles in light mode, here are terminal-side workarounds:
Workaround 1 — Override color7 with a mid-tone gray:
Pick a gray that's dark enough to read on white but light enough for UI backgrounds. Something around #666666 to #808080 is a reasonable compromise:

• Alacritty (alacritty.toml):

  [colors.normal]
  white = "#707070"

• iTerm2: Profiles → Colors → ANSI Colors → set "Bright" white to #707070
• Kitty (kitty.conf):

  color7 #707070
  

• Windows Terminal (settings.json):

  "white": "#707070"

It won't be perfect for both code text and UI backgrounds, but #707070 is a workable middle ground.
Workaround 2 — Use a custom theme that already handles this:
Some terminal themes (e.g., Solarized Light, Catppuccin Latte) are designed with this exact problem in mind and set color7 to a value that works in both contexts.
Workaround 3 — Switch to non-ANSI mode:
If your terminal supports truecolor (most modern terminals do), using Claude Code's default theme instead of "ANSI colors only" avoids this entirely, since it uses direct RGB values rather than the ANSI palette.

[anthknee]

Just hit this on the dark-ansi side, and I want to flag that the OP's claim isn't quite right. Dark-ansi has the same structural overloading, just with different symptoms.

What I see on dark-ansi

UI element	Effective background slot
User message block	slot 8 (ansi:blackBright)
Bash command header, memory block, message actions	slot 8
Bash stdout panel	slot 7 (ansi:white)

Pixel-sampling a Bash tool-call output on my terminal (Ghostty + Kanso Mist):

• User prompt / Bash header row: #5d6065 = Kanso Mist palette[8] = ansi:blackBright ✓ (matches the OP's assertion)
• Bash stdout body: #a5a7a4 = Kanso Mist palette[7] = ansi:white ← slot 7 used as panel bg

Screenshot (Kanso Mist, dark-ansi): the stdout body is visibly palette-7 gray with Claude's dimmed (dimColor) foreground on top. Contrast drops below comfortable readability.

Source-side

From the compiled bundle, theme ll4 (dark-ansi):

bashMessageBackgroundColor: "ansi:black"        // slot 0
messageActionsBackground:   "ansi:blackBright"  // slot 8
memoryBackgroundColor:      "ansi:blackBright"  // slot 8
userMessageBackground:      "ansi:blackBright"  // slot 8
subtle / inactive:          "ansi:white"        // slot 7

No explicit Background token binds to ansi:white, but the stdout panel is rendered with slot 7 as bg anyway, most likely via a parent wrapper applying backgroundColor: "subtle" / "inactive", or via inverse rendering on a subtle-colored Text. Either way, the observable is the same: slot 7 drives stdout panel background.

Terminal themes this breaks on

Theme	slot 7	slot 8	main bg
Kanso Mist	#a4a7a4	#5C6066	#23262D
Kanagawa Paper Ink	#c5c9c7	#393836	#1F1F28
Gruvbox Dark	#a89984	#928374	#282828
One Dark	#abb2bf	#5c6370	#282c34

These are all popular dark palettes. In every case, slots 7 and 8 are bright enough to produce low-contrast panels under Claude's dimmed foreground text.

Why the workaround (remap palette 7) in this comment doesn't fully work on dark-ansi

Slot 7 is owned by the terminal for dim-foreground roles across every other tool: statusline (oh-my-posh / starship), ls directories, git diff metadata, editor comments. Darkening it to #707070 makes Claude readable but breaks statusline readability for everything else.

Environment

• Claude Code v2.1.114
• Ghostty, macOS 15.4, Kanso Mist palette