Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature request: allow disabling bypass permission mode entirely

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…

Code Example

{
  "permissions": {
    "defaultMode": "auto",
    "allowedModes": ["auto", "approve"]
  }
}
RAW_BUFFERClick to expand / collapse

Problem

settings.json supports "defaultMode": "auto" but there is no way to disable bypass mode entirely as a permitted mode. Even with defaultMode set to auto, new sessions in VS Code consistently start in bypass mode. The setting appears to have no effect.

Expected behavior

  • defaultMode: "auto" should reliably start every new session in auto mode
  • There should be an allowedModes (or disabledModes) setting that lets users remove bypass from the mode picker entirely

Current behavior

  • "defaultMode": "auto" is set in ~/.claude/settings.json
  • New VS Code sessions still default to bypass mode
  • No way to prevent bypass from appearing as an option
  • skipDangerousModePermissionPrompt is already false

Use case

Users who want guardrails on by default — especially in shared environments or when working across multiple projects — should be able to lock out bypass mode at the settings level.

Suggested implementation

Add an allowedModes array to the permissions config:

{
  "permissions": {
    "defaultMode": "auto",
    "allowedModes": ["auto", "approve"]
  }
}

If allowedModes is set, modes not in the list would be hidden from the picker and rejected if somehow triggered.

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…

FAQ

Expected behavior

  • defaultMode: "auto" should reliably start every new session in auto mode
  • There should be an allowedModes (or disabledModes) setting that lets users remove bypass from the mode picker entirely
#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

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

Back to top recommendations

TRENDING