[FEATURE] add a setting to make the Claude panel ignore Windows High Contrast

Resolved 💬 1 comment Opened Jun 2, 2026 by YrralH Closed Jun 18, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Windows High Contrast (HC) significantly improves readability on an e-ink display, but it also overwrites the Claude panel in VS Code: the panel can no longer be controlled by the VS Code theme to render well, so the Start / Stop buttons become invisible, the yes/no highlight is almost invisible, and the background shows moiré.

  • Why I need HC: I have severe dry-eye disease, so I use an e-ink display (DASUNG 25.3). E-ink is low-contrast, and HC markedly improves its readability.
  • Fact 1: No Windows HC + VS Code high contrast is perfect for reading inside VS Code.
  • Fact 2: Windows HC does help outside VS Code.

But I can't enjoy both at once — my only workaround is toggling Windows HC on and off, and the shortcut takes a few seconds each time.

Proposed Solution

Add a setting: when enabled, the Claude panel ignores Windows High Contrast and keeps its original (VS Code theme-following) colors.

Alternative Solutions

Turn Windows HC off entirely: Claude becomes readable, but I lose HC's benefit for all other apps — not acceptable.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  1. VS Code uses an HC theme; the Claude panel is readable.
  2. I enable Windows HC for the rest of the OS.
  3. The Claude panel is now overwritten and becomes unreadable.

Additional Context

MechanismAI-assisted (Opus) reasoning about the likely cause; please verify.

  • Windows HC / Win11 "Contrast themes" is the only OS signal that puts Chromium into forced-colors mode (@media (forced-colors: active)), which remaps web content's colors to the system palette unless the page sets forced-color-adjust: none.
  • The Claude panel is Chromium webview content, so it is force-colored directly; VS Code's own UI goes through its theme layer (window.autoDetectHighContrast), decoupled from the renderer — which is why HC hits the Claude panel but not VS Code itself.
  • Because the panel is not authored for forced-colors, the remap collapses its distinct button / highlight colors into a few system colors, so they become invisible — matching the breakage above (HC mangles the webview rather than improving it).
  • There is no per-app HC exclusion in Windows, and no Chromium/Electron flag to disable forced-colors while OS HC is on (electron/electron#28000). The only opt-out is page-side forced-color-adjust: none, which only the extension can apply.
  • So technically the toggle would apply forced-color-adjust: none to the webview root, behind a setting; the default should keep respecting OS HC (accessibility), with users opting in to ignore.

Refs: MDN forced-colors / forced-color-adjust; electron/electron#28000.

Related contrast / webview-styling reports (none requests an opt-out from OS forced-colors): #8724, #45841, #42878, #37591, #30205.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗