Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Auto mode eligibility docs still exclude Max subscribers and Opus 4.7 [1 comments, 2 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#49280•Fetched 2026-04-17 08:45:44
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeekgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"Eliminate prompts with auto mode" requirements and related auto mode availability summaries

Current Documentation

The docs currently say:

Auto mode is available only when your account meets all of these requirements:

  • Plan: Team, Enterprise, or API. Not available on Pro or Max.
  • Admin: on Team and Enterprise, an admin must enable it in Claude Code admin settings before users can turn it on.
  • Model: Claude Sonnet 4.6 or Opus 4.6. Not available on Haiku or claude-3 models.
  • Provider: Anthropic API only. Not available on Bedrock, Vertex, or Foundry.

Related pages repeat the same limitation:

--enable-auto-mode ... Requires a Team, Enterprise, or API plan and Claude Sonnet 4.6 or Opus 4.6

Auto ... Available on Team, Enterprise, and API plans. Requires Claude Sonnet 4.6 or Opus 4.6.

What's Wrong or Missing?

Changelog v2.1.111 says: "Auto mode is now available for Max subscribers when using Opus 4.7".

The current docs still say auto mode is unavailable on Max and still list only Sonnet 4.6 / Opus 4.6 as supported models. That directly contradicts the release change.

As written, a Max subscriber using Opus 4.7 would reasonably conclude that auto mode is unsupported, and the CLI and Desktop summaries reinforce the same outdated eligibility rules.

Suggested Improvement

Update the auto mode eligibility matrix anywhere it is summarized so it reflects the v2.1.111 change.

Suggested changes:

  • In permission-modes, update the plan/model requirements to mention Max support when using Opus 4.7.
  • In cli-reference, update the --enable-auto-mode requirement text to include the new Max + Opus 4.7 path.
  • In desktop, update the Auto mode row so its plan/model availability matches the current product behavior.

If Max support is limited specifically to Opus 4.7, the docs should say that explicitly so users understand that the new eligibility is model-specific rather than a blanket Max-plan change.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/permission-modesPrimary auto mode requirements section still says "Not available on Pro or Max" and lists only Sonnet 4.6 / Opus 4.6
https://code.claude.com/docs/en/cli-reference--enable-auto-mode flag description repeats the old Team/Enterprise/API + 4.6 requirement
https://code.claude.com/docs/en/desktopPermission mode table repeats the old plan and model eligibility summary

Total scope: 3 pages affected

Source: Changelog v2.1.111

Exact changelog entry: "Auto mode is now available for Max subscribers when using Opus 4.7"

extent analysis

TL;DR

Update the documentation to reflect the new auto mode eligibility rules, including support for Max subscribers using Opus 4.7.

Guidance

  • Review the affected pages (permission-modes, cli-reference, and desktop) and update the auto mode requirements to include Max support with Opus 4.7.
  • Ensure the documentation explicitly states that Max support is limited to Opus 4.7, if that is the case.
  • Verify that the updated documentation is consistent across all affected pages.
  • Consider adding a note or clarification to the documentation to highlight the change and avoid confusion for users who may have previously checked the eligibility rules.

Example

No code snippet is necessary for this issue, as it is a documentation update.

Notes

The issue is specific to the documentation and does not require any code changes. The updates should be made to the affected pages to reflect the new auto mode eligibility rules.

Recommendation

Apply workaround: Update the documentation to reflect the new auto mode eligibility rules, as the current documentation is outdated and may cause confusion for users. This will ensure that users have accurate information about the feature's availability.

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…
#api#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING