Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] `auto mode` and `ask before edits` indicators are both orange — visually indistinguishable in VS Code extension [1 participants]

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…
GitHub stats
anthropics/claude-code#52732•Fetched 2026-04-24 10:41:07
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
tomahawk810tomahawk810
Participants
tomahawk810tomahawk810
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

Code Example

None — this is a visual defect, no errors are logged.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

In the Claude Code VS Code extension, the permission mode indicator uses the same orange color for both auto mode and ask before edits:

  • auto mode → orange
  • ask before edits → orange

These two modes have opposite safety semantics — ask before edits gates every write behind an explicit confirmation, while auto mode lets Claude edit without asking — but they look identical in the UI. Cycling modes with Shift+Tab gives no reliable visual cue, so you have to read the text to know which mode you're in. This is a real foot-gun: believing you're in ask before edits when you're actually in auto mode means Claude will modify files without prompting.

What Should Happen?

The two modes should use distinct colors keyed to risk level:

  • ask before edits — a "safe" color (blue, cyan, or green), reflecting that no write happens without approval
  • auto mode — a "caution" color (amber or red), reflecting that Claude writes to disk freely

Colors should be driven by VS Code theme tokens (e.g. charts.blue, charts.orange) so contrast holds in both light and dark themes.

Error Messages/Logs

None — this is a visual defect, no errors are logged.

Steps to Reproduce

  1. Open the Claude Code extension in VS Code.
  2. Start a session — it begins in the default mode.
  3. Press Shift+Tab to switch to ask before edits. Note the indicator color.
  4. Press Shift+Tab again to switch to auto mode. Note the indicator color.
  5. Observe that both modes display in the same orange.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.119 (Claude Code for VS Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

Update the VS Code extension to use distinct colors for auto mode and ask before edits to reflect their different safety semantics.

Guidance

  • Identify the current CSS or theme configuration that sets the orange color for both modes and update it to use different colors, such as blue or green for ask before edits and amber or red for auto mode.
  • Use VS Code theme tokens (e.g. charts.blue, charts.orange) to ensure contrast in both light and dark themes.
  • Verify the color change by reproducing the steps to reproduce and checking the indicator color for each mode.
  • Consider adding a tooltip or other visual cue to reinforce the mode indicator, in case the color change is not sufficient.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The fix may require updating the extension's CSS or theme configuration, and may involve using VS Code's theme token system to ensure compatibility with different themes.

Recommendation

Apply a workaround by manually updating the extension's CSS or theme configuration to use distinct colors for each mode, as the issue is not a regression and there is no previous working version to upgrade to.

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…
#api#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING