[BUG] AskUserQuestion question text invisible when Claude Code theme doesn't match terminal background

Resolved 💬 2 comments Opened May 10, 2026 by vipinjose8683 Closed Jun 8, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

On Claude Code with a dark theme running in a light-background terminal, the question field of AskUserQuestion renders in a light foreground color against the light background and is unreadable.
Highlighting the region reveals the text is present, just color-matched to the background.

The header chip and options list render with readable contrast in the same view — they appear to have their own background/contrast handling. Only the bare question text inherits the raw theme foreground, so
it's the only element that fails when theme and terminal background are mismatched.

Switching Claude Code to a light theme via /config resolves it.

Related: #26170 (same class, opposite direction — black text on dark terminal).

What Should Happen?

The question text should render with readable contrast regardless of theme/terminal-background mismatch — either by using its own contrast-safe styling like the header chip and options, or by the theme picker
warning when the selected theme is likely mismatched with the terminal background.

Error Messages/Logs

Steps to Reproduce

  1. Set terminal to a light background (e.g., Terminal.app default light profile).
  2. Set Claude Code to dark theme via /config.
  3. Have the assistant invoke any AskUserQuestion call.
  4. Observe: question text is invisible without highlighting; header chip and options render normally.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.138

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗