Desktop app always starts sessions in "Accept Edits" mode instead of "Bypass Permissions", even though defaultMode: "bypassPermissions" is set in ~/.claude/settings.json
Resolved 💬 4 comments Opened May 22, 2026 by Lebedb233 Closed Jun 26, 2026
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?
Desktop app always starts sessions in "Accept Edits" mode instead of "Bypass Permissions", even though defaultMode: "bypassPermissions" is configured in ~/.claude/settings.json
What Should Happen?
Sessions should start in Bypass Permissions mode as configured in settings.json
Error Messages/Logs
Warning: "Bypass Permissions mode isn't enabled. The session started in Accept Edits"
"Permission mode couldn't be changed. You can try again."
Steps to Reproduce
- Set ~/.claude/settings.json with "permissions": { "defaultMode": "bypassPermissions" }
- Enable "Allow bypass permissions mode" in Desktop Settings
- Run CLI with --dangerously-skip-permissions and accept
- Open desktop app → start new session
- Send any message
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.146
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
CLI works correctly — shows "bypass permissions on".
Desktop GUI ignores the same settings.json.
Mode reverts to "Accept Edits" after sending first message even if manually switched.
skipDangerousModePermissionPrompt: true is also set.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗