[BUG] `auto mode` and `ask before edits` indicators are both orange — visually indistinguishable in VS Code extension
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?
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→ orangeask 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 approvalauto 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
- Open the Claude Code extension in VS Code.
- Start a session — it begins in the default mode.
- Press
Shift+Tabto switch toask before edits. Note the indicator color. - Press
Shift+Tabagain to switch toauto mode. Note the indicator color. - 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_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗