claude-code - 💡(How to fix) Fix [BUG] `claude agents --allow-dangerously-skip-permissions` defaults to bypass instead of allowing it

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?

Following the fix in #58380, claude agents --allow-dangerously-skip-permissions has two problems:

1. It defaults new sessions to bypass permissions mode. The expected behavior for --allow-dangerously-skip-permissions is to make bypass available as a mode you can cycle to, not to force it as the default. That's what --dangerously-skip-permissions is for.

2. 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?

1. --allow-dangerously-skip-permissions should 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.
2. 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

1. Run claude agents --allow-dangerously-skip-permissions
2. Dispatch a new session
3. Observe it starts in bypass permissions mode (should start in default mode with bypass available)
4. Attach to a pre-existing session that was dispatched without the flag
5. 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