[Bug] Warp Terminal Light Mode: Unreadable Question Text Due to Color Contrast

Status Closed — not planned
Maintainer reply None cached
Activity 13 comments · opened Nov 10, 2025 · closed May 2, 2026

Bug Description
I primarily use the Warp terminal shell application. I have noticed recently that when Claude Code asks for me to answer questions the text of the question is the same color as the background, preventing me from being able to see the text at all.

Environment Info

  • Platform: win32
  • Terminal: WarpTerminal
  • Version: 2.0.36

View original on GitHub ↗

13 Comments

github-actions[bot] · 9 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/4948
  2. https://github.com/anthropics/claude-code/issues/8681
  3. https://github.com/anthropics/claude-code/issues/6214

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

jperna7254 · 9 months ago

This is not a duplicate because the specific text that cannot be seen is the question text when in the "user feedback" feature (while Claude Code is asking for user input about questions after an initial prompt).

ghnmqdtg · 9 months ago

I'm not sure if you have the same issue as mine. I think it is probably because your Claude Code theme is set to the light mode, and your Warp is set to a dark theme.

The text color in Claude Code's light mode is black, making it hard to read in dark backgrounds. Perhaps you can try setting your Claude Code to dark mode so the question text in plan mode is white.

github-actions[bot] · 8 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

sukhdeepjohar · 7 months ago

Same issue with file listings and data output

Experiencing the same issue, but not just with question text - all light gray text in Claude Code output is unreadable on light backgrounds.

Specific Examples:

  • File listings in diff outputs: "bigquery_schema_2.json" appears in very light gray
  • Field names in data comparisons: "acquired_at_s", "advertising_id", etc. are barely visible
  • Table column headers and dimmed text

Environment:

  • macOS Terminal.app (not Warp, but same issue)
  • Terminal background: Light blue (#B8D4E8) and white (#FFFFFF) tested

Critical Use Case:
When copying Claude Code output to documentation (Word docs, PDFs, reports), the light gray text becomes completely invisible on white backgrounds. This makes it impossible to document work or share findings with colleagues.

Attempted Workarounds:

  • Changed all 16 ANSI colors in Terminal preferences → no effect
  • Changed background to pure white → text still too light
  • Claude Code appears to use hardcoded colors that bypass terminal settings

Impact:
This is a blocker for workflows that require documenting Claude Code's output. Currently need to:

  1. Copy text
  2. Paste to text editor
  3. Select all & copy again (strips formatting)
  4. Paste to final document

Would appreciate either:

  • Auto-detection of terminal background brightness (adjust text colors accordingly)
  • Configuration option to set minimum text darkness/contrast
  • Flag to disable colored output entirely
sukhdeepjohar · 7 months ago

+1 for this feature request. I'm experiencing significant usability issues with Claude Code's hardcoded light gray text colors on light terminal backgrounds.

Specific Problem:
When Claude Code outputs file listings, data comparisons, or field names (e.g., "bigquery_schema_2.json", "acquired_at_s", "advertising_id"), it uses very light gray colors that are:

  • Nearly invisible on white/light backgrounds
  • Impossible to read when copying to documents (the text disappears on white paper/PDFs)

What I've Tried:

  • Adjusted all 16 ANSI colors in Terminal.app preferences
  • Changed background to pure white (#FFFFFF)
  • Tested multiple terminal color schemes
  • None of these affect Claude Code's light gray output (it appears to use hardcoded RGB/256-color values)

Impact on Workflow:
I frequently need to document Claude Code's output in reports. The current workaround (copy → paste to text editor → strip formatting → copy again → paste to document) adds significant friction.

Proposed Solution:
Allow users to customize output colors via settings.json:
{
"colors": {
"fileNames": "#333333",
"fieldNames": "#444444",
"dimText": "#666666"
}
}

Or at minimum, provide a "light mode" / "dark mode" toggle that auto-adjusts text colors for proper contrast.

Environment:

  • macOS Terminal.app
  • Terminal background: Light blue (#B8D4E8) and white (#FFFFFF) tested
  • Issue persists regardless of terminal ANSI color configuration

This would greatly improve accessibility and usability for users with light-themed terminals.

hauntedhost · 6 months ago

This issue is still happening

kae-builds · 6 months ago

This issue is still happening

kylecrouse · 5 months ago

Same issue on macOS with Apple Terminal.app.

Environment:

  • OS: macOS 15.5 (Darwin 25.1.0)
  • Terminal: Apple Terminal.app Version 2.15 (465)
  • Theme: Light terminal profile
  • Claude Code model: claude-opus-4-6

The AskUserQuestion prompt options (labels, descriptions) render as white/near-white text on a white background, making them completely unreadable. Have to guess at option numbers or switch to a dark theme to interact.

Not just a Warp issue — affects native macOS Terminal as well.

jwuttke · 5 months ago

+1, barely readable, tiring my eyes

David-261108 · 5 months ago

问题依旧存在,快点修复吧
Environment:

macOS Terminal.app
Terminal background: Light blue (#B8D4E8) and white (#FFFFFF) tested
Issue persists regardless of terminal ANSI color configuration

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.