Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Permission modes page shows auto mode instead of bypass permissions after `--dangerously-skip-permissions` [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52204•Fetched 2026-04-23 07:33:48
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"Analyze before you edit with plan mode" — the plan acceptance options shown after exiting plan mode

Current Documentation

The permission modes page currently says:

When the plan is ready, Claude presents it and asks how to proceed. From that prompt you can:

  • Approve and start in auto mode
  • Approve and accept edits
  • Approve and review each edit manually

The same page also says:

The --dangerously-skip-permissions flag is equivalent.

That line appears in the bypassPermissions section, where the page explains that --dangerously-skip-permissions is equivalent to --permission-mode bypassPermissions.

What's Wrong or Missing?

Changelog v2.1.118 says Claude Code fixed the plan acceptance dialog to offer bypass permissions instead of auto mode when the session is running with --dangerously-skip-permissions.

The current permission modes page still presents "Approve and start in auto mode" as the approval option without explaining that the plan acceptance choice depends on the permission mode that was active before entering plan mode. For users who start in bypassPermissions via --dangerously-skip-permissions, this is outdated and describes the pre-fix behavior.

As written, the page can mislead users into expecting the wrong post-plan mode and makes the --dangerously-skip-permissions flow harder to understand.

Suggested Improvement

Update the plan mode section to explain that approving a plan resumes the relevant execution mode for the current session, rather than always offering auto mode.

For example, the docs could clarify that:

  • sessions started with --dangerously-skip-permissions / bypassPermissions resume bypass permissions after plan approval
  • auto appears only when auto mode is actually available for that session
  • the label shown in the approval dialog depends on the mode Claude should return to after planning

If helpful, add a short note cross-referencing the bypassPermissions section so readers can understand why the dialog changes when they entered plan mode from a bypass-permissions session.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/permission-modesPlan mode approval options currently say "Approve and start in auto mode" even though v2.1.118 fixed the --dangerously-skip-permissions case to offer bypass permissions instead

Total scope: 1 page affected

Source: Changelog v2.1.118

Exact changelog entry:

Fixed plan acceptance dialog offering "auto mode" instead of "bypass permissions" when running with --dangerously-skip-permissions

extent analysis

TL;DR

Update the documentation to reflect that the plan acceptance dialog's approval options depend on the permission mode active before entering plan mode.

Guidance

  • Review the current documentation on the "Analyze before you edit with plan mode" section and update it to explain that approving a plan resumes the relevant execution mode for the current session.
  • Clarify that sessions started with --dangerously-skip-permissions / bypassPermissions resume bypass permissions after plan approval, and auto appears only when auto mode is available for that session.
  • Consider adding a note cross-referencing the bypassPermissions section to help readers understand the dialog changes when entering plan mode from a bypass-permissions session.
  • Verify the changes by checking the documentation against the behavior described in Changelog v2.1.118.

Example

No code snippet is necessary for this documentation update, but an example of the revised text could be: "The plan acceptance dialog will offer approval options based on the permission mode active before entering plan mode. For example, if you entered plan mode from a session started with --dangerously-skip-permissions, the dialog will offer 'Approve and bypass permissions' instead of 'Approve and start in auto mode'."

Notes

The update should only affect the "Plan mode approval options" section on the permission modes page, as indicated in the affected pages table.

Recommendation

Apply workaround: Update the documentation to accurately reflect the current behavior, as the changelog entry v2.1.118 has already fixed the underlying issue, but the documentation needs to be corrected to match the new behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#ssr#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Permission modes page shows auto mode instead of bypass permissions after `--dangerously-skip-permissions` [1 participants]