[DOCS] Auto mode docs still require obsolete `--enable-auto-mode` flag

Resolved 💬 2 comments Opened Apr 16, 2026 by coygeek Closed Apr 29, 2026

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:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/permission-modes | CLI 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:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/settings | permissions.defaultMode already lists auto as a valid value |
| https://code.claude.com/docs/en/best-practices | Uses 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

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗