[DOCS] `--dangerously-skip-permissions` docs still say protected-path writes prompt

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/permission-modes

Section/Topic

"Skip all checks with bypassPermissions mode" and "Protected paths"

Current Documentation

The docs currently say:

bypassPermissions mode disables permission prompts and safety checks so tool calls execute immediately. Writes to protected paths are the only actions that still prompt.

The "Protected paths" section also says:

Writes to a small set of paths are never auto-approved, in every mode. This prevents accidental corruption of repository state and Claude's own configuration. In default, acceptEdits, plan, and bypassPermissions these writes prompt; in auto they route to the classifier; in dontAsk they are denied.

What's Wrong or Missing?

This appears outdated for Claude Code v2.1.126. The v2.1.126 changelog says:

--dangerously-skip-permissions now bypasses prompts for writes to .claude/, .git/, .vscode/, shell config files, and other previously-protected paths (catastrophic removal commands still prompt as a safety net)

That directly contradicts the current permission-mode documentation, which tells users that protected-path writes still prompt in bypassPermissions mode and that protected paths are "never auto-approved, in every mode."

The current wording understates what --dangerously-skip-permissions now bypasses. Users relying on the docs may believe writes to repository metadata, Claude configuration, editor configuration, and shell config files still require a confirmation prompt when they no longer do in v2.1.126.

Suggested Improvement

Update the bypassPermissions and protected-path wording to match v2.1.126 behavior. For example:

Before:

Writes to protected paths are the only actions that still prompt.

After:

In v2.1.126 and later, --dangerously-skip-permissions / bypassPermissions also bypasses prompts for writes to previously protected paths such as .claude/, .git/, .vscode/, shell config files, and similar configuration paths. Catastrophic removal commands still prompt as a safety net.

Also update the "Protected paths" section so it no longer says protected-path writes are "never auto-approved, in every mode" or that they prompt in bypassPermissions.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/permission-modes | "Skip all checks with bypassPermissions mode"; "Protected paths" | Says protected-path writes still prompt in bypassPermissions and are never auto-approved |
| https://code.claude.com/docs/en/permissions | "Permission modes" table and warning | Says bypassPermissions skips prompts except protected directories, and protected directories still prompt |

Total scope: 2 pages affected

Version context: The behavior change is from Claude Code v2.1.126.