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

Status Fixed / completed

Maintainer reply None cached

Activity 3 comments · opened May 16, 2026 · 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 ↗

3 Comments

github-actions[bot] · 5 months ago

Found 2 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

coygeek · 4 months ago

Issue #59596 Verification

Title: [DOCS] agent-view docs omit claude agents --allow-dangerously-skip-permissions behavior
Issue Date: 2026-05-16
Verification Date: 2026-05-31
Status: RESOLVED

---

Issue Summary

This issue reports that the agent-view documentation page omitted documentation for claude agents --allow-dangerously-skip-permissions: the page did not mention that the flag was accepted by claude agents, nor did it explain the agent-view-specific effect (making bypassPermissions available in the dispatched session's Shift+Tab cycle without starting in bypass mode immediately).

---

Verification Results

Claim A: `agent-view` does not say that `claude agents` accepts `--allow-dangerously-skip-permissions`

Status: RESOLVED

At https://code.claude.com/docs/en/agent-view, lines 390-391:

claude agents also accepts --dangerously-skip-permissions as shorthand for --permission-mode bypassPermissions, and --allow-dangerously-skip-permissions to make bypassPermissions available in each dispatched session's Shift+Tab cycle without starting in that mode. Both match the top-level CLI flags.

The flag is also listed in the version-compatibility table at line 397:

| --allow-dangerously-skip-permissions | v2.1.143 |

Verdict: The agent-view page now explicitly documents that claude agents accepts --allow-dangerously-skip-permissions. The missing documentation has been added.

---

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

Status: RESOLVED

At https://code.claude.com/docs/en/agent-view, line 390:

--allow-dangerously-skip-permissions to make bypassPermissions available in each dispatched session's Shift+Tab cycle without starting in that mode.

This directly addresses the issue's concern that the v2.1.143 fix (dispatched sessions no longer defaulting to bypass mode when the flag is used) was undocumented. The current text explains that dispatched sessions do not start in bypass mode — they merely gain the ability to cycle to it later.

Verdict: The agent-view-specific effect is now documented, including the distinction that sessions start in their normal mode rather than in bypassPermissions immediately.

---

Current State

| Claim | Status |
|-------|--------|
| Claim A: agent-view does not say claude agents accepts --allow-dangerously-skip-permissions | RESOLVED |
| Claim B: No explanation of agent-view-specific effect | RESOLVED |

---

Suggested Fix

N/A - issue has been resolved.

---

References

https://code.claude.com/docs/en/agent-view, lines 390-397: Documents claude agents --allow-dangerously-skip-permissions and explains the dispatched-session behavior (flag makes bypassPermissions available in the cycle without starting in that mode)
https://code.claude.com/docs/en/cli-reference, line 53: General CLI definition of --allow-dangerously-skip-permissions
https://code.claude.com/docs/en/permission-modes, line 37: Explains the --allow- variant adds bypassPermissions to the cycle without activating it

---

Conclusion & Recommendation

Primary Concern: The agent-view documentation omitted documentation of claude agents --allow-dangerously-skip-permissions and its dispatched-session behavior.

Resolution Status: RESOLVED

Recommendation: CLOSE

The agent-view page now includes a dedicated paragraph (line 390) documenting that claude agents accepts --allow-dangerously-skip-permissions and explaining that it makes bypassPermissions available in each dispatched session's Shift+Tab cycle without starting in that mode, directly addressing both claims in the issue.

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.