claude-code - 💡(How to fix) Fix [BUG] Agent view ignores 'theme' setting; uses defaults instead of user's configured theme

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The new agent view (claude agents, shipped 2026-05-11 in 2.1.139) does not honor the theme key from ~/.claude/settings.json. Regular interactive claude sessions use the configured theme correctly; agent view falls back to default colors regardless.

Error Message

Agent view uses default colors. No theme inheritance, no agentView.theme setting documented, no warning/error.

Root Cause

The new agent view (claude agents, shipped 2026-05-11 in 2.1.139) does not honor the theme key from ~/.claude/settings.json. Regular interactive claude sessions use the configured theme correctly; agent view falls back to default colors regardless.

Code Example

{ "theme": "custom:eink-kaleido" }
RAW_BUFFERClick to expand / collapse

Summary

The new agent view (claude agents, shipped 2026-05-11 in 2.1.139) does not honor the theme key from ~/.claude/settings.json. Regular interactive claude sessions use the configured theme correctly; agent view falls back to default colors regardless.

Steps to reproduce

  1. Configure a non-default theme in ~/.claude/settings.json, e.g.:
    { "theme": "custom:eink-kaleido" }
    (Any custom theme registered in ~/.claude/themes/ reproduces; built-in non-default themes should as well.)
  2. Run claude interactively — the configured theme is applied as expected.
  3. Run claude agents — the dashboard appears with default styling, not the configured theme.

Expected

Agent view inherits the same theme setting as the main interactive session, including custom themes registered under ~/.claude/themes/.

Actual

Agent view uses default colors. No theme inheritance, no agentView.theme setting documented, no warning/error.

Why this matters (not just cosmetic)

I run Claude Code on a Kaleido 3 e-ink display where the contrast/saturation of UI colors is functional, not decorative — default themes are unreadable on this hardware. My custom theme (custom:eink-kaleido) is tuned for Kaleido 3's color filter array, and not having it in agent view makes the dashboard practically unusable for me. There are presumably also accessibility cases (low-vision users with tuned high-contrast themes) where this matters similarly.

Suggested fix

Have agent view read the same theme resolution path as the main session, including custom themes under ~/.claude/themes/. Alternatively (or additionally), accept an agentView.theme override for users who want the dashboard styled differently from their session.

Environment

  • Claude Code: 2.1.139
  • OS: Windows 11 Pro (10.0.26200)
  • Shell: Git Bash / MINGW64 (launched as winpty claude agents due to TTY-detection — orthogonal issue)
  • Display: Dasung Paperlike Color (Kaleido 3 panel)
  • Settings file location: E:/Projects/.claude/settings.json (via CLAUDE_CONFIG_DIR)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING