[DOCS] `claude --bg --dangerously-skip-permissions` persistence across retire/wake is undocumented

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

Permission mode, model, and effort and the wake/respawn behavior for background sessions

Current Documentation

The docs currently say:

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.

They also say:

Attach to a running session and run /model there. The change persists if the session is respawned.

And the wake section says:

Background sessions don't survive sleep or shutdown, so sessions that were running show as failed after you wake. Attach, peek, or reply to any of them and the session restarts from where it left off. To restart all of them at once, run claude respawn --all.

The CLI reference documents the startup flag but not its persistence behavior:

--dangerously-skip-permissions | Skip permission prompts. Equivalent to --permission-mode bypassPermissions.

What's Wrong or Missing?

Changelog v2.1.143 says:

claude --bg --dangerously-skip-permissions now persists across retire→wake

The current docs explain how background sessions start, how permission mode is chosen initially, and that some state such as /model persists across respawn. They do not document the corresponding behavior for sessions started with claude --bg --dangerously-skip-permissions.

That leaves an important unattended-use case undocumented: after a background session is retired and later resumed, or after a wake-triggered restart, users cannot tell from the docs whether bypass-permissions mode is preserved or whether the session falls back to the directory default permission mode.

Suggested Improvement

Add a short note to agent-view near the permission-mode and wake/respawn sections stating that sessions started with claude --bg --dangerously-skip-permissions keep bypassPermissions across retire/wake respawns.

Suggested wording:

Sessions started with claude --bg --dangerously-skip-permissions keep bypassPermissions when the background process is retired and later restarted, including after waking the machine or when you resume the session with claude respawn, attach, or reply.

Also add a brief cross-reference from cli-reference so readers who start from the flag documentation know this background-session persistence behavior exists.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/agent-view | Documents background-session permission mode, respawn behavior, and wake recovery, but not that claude --bg --dangerously-skip-permissions persists across retire/wake |
| https://code.claude.com/docs/en/cli-reference | Documents the --dangerously-skip-permissions flag, but not its background-session persistence behavior when combined with --bg |

Total scope: 2 pages affected

Source: Changelog v2.1.143

Changelog entry: claude --bg --dangerously-skip-permissions now persists across retire→wake