claude-code - 💡(How to fix) Fix [DOCS] Auto mode docs still require obsolete `--enable-auto-mode` flag [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#49292Fetched 2026-04-17 08:45:23
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
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

"Switch permission modes" (CLI tab) and "Eliminate prompts with auto mode"

Current Documentation

The docs currently say:

During a session: press Shift+Tab to cycle defaultacceptEditsplan. The current mode appears in the status bar. Not every mode is in the default cycle:

  • auto: appears after you opt in with --enable-auto-mode or the persisted equivalent in settings

And later on the same page:

Once enabled, start with the flag and auto joins the Shift+Tab cycle:

claude --enable-auto-mode

The CLI reference also says:

--enable-auto-mode | Unlock auto mode in the Shift+Tab cycle.

At the same time, other current docs already describe direct auto-mode entry points:

--permission-mode ... Accepts default, acceptEdits, plan, auto, dontAsk, or bypassPermissions.

defaultMode ... Valid values: default, acceptEdits, plan, auto, dontAsk, bypassPermissions.

What's Wrong or Missing?

Changelog v2.1.111 says: Auto mode no longer requires --enable-auto-mode.

The current docs still describe --enable-auto-mode as required to make auto mode available in the CLI and mode cycle. That is now outdated and creates contradictory guidance: some pages say users must opt in with --enable-auto-mode, while other pages already document auto as a normal --permission-mode and defaultMode value.

Users reading the outdated instructions may assume auto mode is unavailable unless they pass an extra flag, even though the current behavior no longer requires that opt-in step.

Suggested Improvement

Update the auto mode activation docs to reflect the post-v2.1.111 behavior.

Specifically:

  1. Remove or rewrite statements that say --enable-auto-mode is required to make auto mode appear in the CLI cycle.
  2. Update the auto mode startup example so it documents the current flow, such as entering auto mode directly with --permission-mode auto or permissions.defaultMode: "auto" when the eligibility requirements are met.
  3. Update the CLI reference entry for --enable-auto-mode to either remove it if obsolete, or mark it as optional/legacy if it still exists for backward compatibility.
  4. Make the permission-modes page, settings page, and CLI reference use the same terminology for how auto mode is activated.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/permission-modesCLI instructions still say auto appears only after opting in with --enable-auto-mode, and the auto mode section tells users to start with that flag
https://code.claude.com/docs/en/cli-reference--enable-auto-mode is still documented as the way to unlock auto mode in the Shift+Tab cycle

Related cross-references:

PageContext
https://code.claude.com/docs/en/settingspermissions.defaultMode already lists auto as a valid value
https://code.claude.com/docs/en/best-practicesUses claude --permission-mode auto -p "fix all lint errors"

Total scope: 2 pages affected

Source: Changelog v2.1.111

Exact changelog entry:

Auto mode no longer requires --enable-auto-mode

extent analysis

TL;DR

Update the documentation to reflect that --enable-auto-mode is no longer required to use auto mode, and provide consistent instructions on how to activate auto mode.

Guidance

  • Review and update the documentation on the "Switch permission modes" and "Eliminate prompts with auto mode" sections to remove references to --enable-auto-mode as a requirement for auto mode.
  • Update the CLI reference entry for --enable-auto-mode to either remove it or mark it as optional/legacy.
  • Ensure that the permission-modes page, settings page, and CLI reference use consistent terminology for activating auto mode, such as using --permission-mode auto or permissions.defaultMode: "auto".
  • Verify that the updated documentation is consistent across all affected pages, including the CLI reference and settings page.

Example

The updated documentation could include examples such as:

claude --permission-mode auto

or

{
  "permissions": {
    "defaultMode": "auto"
  }
}

to illustrate how to activate auto mode.

Notes

The updates should be made to the following pages: https://code.claude.com/docs/en/permission-modes and https://code.claude.com/docs/en/cli-reference. The changes should be verified to ensure that the documentation is consistent and accurate.

Recommendation

Apply workaround: Update the documentation to reflect the current behavior of auto mode, as the changelog entry v2.1.111 indicates that --enable-auto-mode is no longer required. This will help to avoid confusion and ensure that users can understand how to use auto mode correctly.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING