[DOCS] `/bg` and `←` detach docs omit `--allow-dangerously-skip-permissions` preservation for backgrounded sessions

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:

The permission mode depends on how you started the session. Backgrounding an existing session with /bg or ← keeps the current permission mode, so a session you switched to acceptEdits or auto stays in that mode after detaching. 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.

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 agent-view page explains that /bg and ← keep the current permission mode after detaching, but it does not document the narrower v2.1.143 behavior where detaching also preserves --allow-dangerously-skip-permissions.

That omission matters because --allow-dangerously-skip-permissions does not start the session in bypassPermissions; it only makes bypassPermissions available later in the Shift+Tab cycle. A reader who backgrounds a session with /bg or ← cannot tell from the current docs whether the forked background worker still has bypassPermissions available to cycle into, or whether that optional mode is lost during detach.

Suggested Improvement

Add a short note to agent-view near the detach/background permission-mode description clarifying that /bg and ← preserve --allow-dangerously-skip-permissions when they fork a background worker.

For example:

Before:

Backgrounding an existing session with /bg or ← keeps the current permission mode...

After:

Backgrounding an existing session with /bg or ← keeps the current permission mode. If the attached session was started with --allow-dangerously-skip-permissions, the forked background worker also keeps bypassPermissions available in its Shift+Tab cycle.

This could also cross-reference the permission-modes page so readers understand the difference between --dangerously-skip-permissions and --allow-dangerously-skip-permissions.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 308-314 | Detach/background behavior explains preserved permission mode but not preservation of --allow-dangerously-skip-permissions for the forked worker |
| https://code.claude.com/docs/en/permission-modes | 34-40 | Explains that --allow-dangerously-skip-permissions adds bypassPermissions to the Shift+Tab cycle, which is the behavior readers need when interpreting detached background workers |

Total scope: 2 pages affected

Version context: Changelog v2.1.143 says /bg and ← detach now preserve --allow-dangerously-skip-permissions, so the forked worker keeps bypass-permissions available in its Shift+Tab cycle.