[DOCS] `agent-view` docs omit `claude agents --allow-dangerously-skip-permissions` behavior

Resolved 💬 2 comments Opened May 16, 2026 by coygeek Closed Jun 1, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/agent-view

Section/Topic

Permission mode, model, and effort in the agent view guide

Current Documentation

The docs currently say:

Dispatching from the agent view input or running claude --bg from your shell uses the defaultMode from that directory's settings, or the permissionMode from the dispatched subagent's frontmatter. To set defaults for every session you dispatch from agent view, pass any of --permission-mode, --model, or --effort when opening it: ``bash claude agents --permission-mode plan --model opus --effort high ``

The CLI reference separately says:

--allow-dangerously-skip-permissions | Add bypassPermissions to the Shift+Tab mode cycle without starting in it. Lets you begin in a different mode like plan and switch to bypassPermissions later.

And the permission modes page says:

bypassPermissions: appears after you start with --permission-mode bypassPermissions, --dangerously-skip-permissions, or --allow-dangerously-skip-permissions; the --allow- variant adds the mode to the cycle without activating it

What's Wrong or Missing?

The docs explain what --allow-dangerously-skip-permissions does in general, and they separately explain how claude agents sets defaults for dispatched sessions, but they do not document the combined claude agents behavior.

That leaves the v2.1.143 agent-view change undocumented in the place users would look for it:

A. agent-view does not say that claude agents accepts --allow-dangerously-skip-permissions

The dispatch-default section lists --permission-mode, --model, and --effort, but not the flag that enables bypass permissions in the session's mode cycle.

B. The docs do not explain the agent-view-specific effect of the flag

For sessions dispatched from claude agents, --allow-dangerously-skip-permissions should make bypassPermissions available in the Shift+Tab cycle without starting the dispatched session in bypassPermissions immediately. That distinction matters because v2.1.143 specifically fixed claude agents --allow-dangerously-skip-permissions defaulting dispatched sessions to bypass mode instead of only making it available in the cycle.

Suggested Improvement

Update the agent-view page to document --allow-dangerously-skip-permissions alongside the existing dispatch-default flags.

For example, extend the section to say that:

Before:

To set defaults for every session you dispatch from agent view, pass any of --permission-mode, --model, or --effort when opening it.

After:

To set defaults for every session you dispatch from agent view, pass --permission-mode, --model, --effort, or --allow-dangerously-skip-permissions when opening it.

Add a concrete example such as:

claude agents --permission-mode plan --allow-dangerously-skip-permissions

And clarify that dispatched sessions start in plan but can cycle to bypassPermissions later with Shift+Tab, rather than starting in bypass mode immediately.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 308-324 | Explains agent-view dispatch defaults and starting permission mode, but omits --allow-dangerously-skip-permissions |
| https://code.claude.com/docs/en/cli-reference | 52 | Defines the flag semantics generally, but not how claude agents uses it for dispatched sessions |
| https://code.claude.com/docs/en/permission-modes | 34-40 | Explains that the --allow- variant adds bypassPermissions to the cycle without activating it |

Total scope: 3 pages affected

Version context: The v2.1.143 changelog says claude agents --allow-dangerously-skip-permissions was fixed so dispatched sessions no longer default to bypass mode and instead only make bypass mode available in the permission cycle.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗