[BUG] `claude agents --allow-dangerously-skip-permissions` defaults to bypass instead of allowing it
Resolved 💬 3 comments Opened May 15, 2026 by jonathanlaniado Closed May 27, 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?
Following the fix in #58380, claude agents --allow-dangerously-skip-permissions has two problems:
- It defaults new sessions to
bypass permissionsmode. The expected behavior for--allow-dangerously-skip-permissionsis to make bypass available as a mode you can cycle to, not to force it as the default. That's what--dangerously-skip-permissionsis for.
- It doesn't let you switch existing sessions to bypass permissions. If I attach to a session that was dispatched without the flag, there's no way to enable bypass on it after the fact.
What Should Happen?
--allow-dangerously-skip-permissionsshould start sessions in the normal default permission mode, but include bypass permissions in the Shift+Tab cycle so the user can opt into it per-session.- Attaching to an existing session from agent view should respect the agent view's permission flags, or at minimum let the user cycle into bypass if the flag was set.
Steps to Reproduce
- Run
claude agents --allow-dangerously-skip-permissions - Dispatch a new session
- Observe it starts in bypass permissions mode (should start in default mode with bypass available)
- Attach to a pre-existing session that was dispatched without the flag
- Try to cycle to bypass permissions via Shift+Tab — it's not available
Claude Model
Opus
Is this a regression?
No, new feature (shipped in v2.1.142 via #58380)
Claude Code Version
2.1.142
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Ghostty / zsh
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗