Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Plan-approval auto mode rejected with inconsistent gating, disables shift+tab auto [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#49653•Fetched 2026-04-17 08:35:05
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
1
Author
mianst9524mianst9524
Participants
mianst9524mianst9524
Timeline (top)
labeled ×4

Error Message

Auto mode gating is inconsistent across entry paths for the same session on the same plan. The plan-approval path rejects auto with a misleading plan-tier error, and the rejection leaves the session in a state where shift+tab can no longer select Auto either. A CLI restart is required to recover.

  • If gating applies, the error should be consistent across entry paths (startup / shift+tab / plan-approval). OR at minimum

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Title: Plan-approval "Start in auto mode" is rejected with "unavailable for your plan" on Max plan, and poisons session so shift+tab auto also breaks

Environment

  • Claude Code: 2.1.112 (Windows 11)
  • Account: Claude Max (verified via /status → "Login method: Claude Max account")
  • Model: Opus 4.7 (1M context)

Summary Auto mode gating is inconsistent across entry paths for the same session on the same plan. The plan-approval path rejects auto with a misleading plan-tier error, and the rejection leaves the session in a state where shift+tab can no longer select Auto either. A CLI restart is required to recover.

Steps to reproduce

  1. In a session where Auto mode works normally (e.g. startup with permissions.defaultMode: "auto" succeeds, and shift+tab cycle includes Auto).
  2. Invoke /plan and have the assistant produce a plan.
  3. On the approval prompt, choose "Approve and start in auto mode".
  4. Status line briefly displays: plan exit → default · auto mode is unavailable for your plan. Session falls back to default mode.
  5. Press shift+tab and cycle through modes — Auto is no longer a candidate.
  6. Restart Claude Code; Auto becomes selectable again both on startup and via shift+tab.

Expected

  • Max plan users should be able to enter Auto via plan-approval. OR
  • If gating applies, the error should be consistent across entry paths (startup / shift+tab / plan-approval). OR at minimum
  • A rejected plan-approval auto transition should not disable Auto for subsequent shift+tab cycles in the same session.

Actual

  • Plan-approval auto is rejected with a plan-tier message even though Max plan allows auto elsewhere.
  • The rejection causes Auto to disappear from shift+tab cycle until CLI restart.

Notes

  • Message text "unavailable for your plan" is misleading — Max does support Auto via other paths.
  • No log file documents the rejection reason beyond the brief status-line text.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.112
  • Feedback ID: a6b77074-2ea8-48ed-938e-cffe3e8aedac

Errors

[]

extent analysis

TL;DR

The plan-approval path for Auto mode should be revised to correctly handle Max plan users and prevent session poisoning.

Guidance

  • Investigate the plan-approval logic to ensure it correctly checks the user's plan and permissions before rejecting Auto mode.
  • Verify that the error message "unavailable for your plan" is accurate and not misleading, considering Max plan users can access Auto mode through other paths.
  • Review the session state management to prevent the rejection of Auto mode from affecting subsequent shift+tab cycles.
  • Check for any inconsistencies in Auto mode gating across different entry paths (startup, shift+tab, plan-approval) to ensure a unified experience.

Example

No code snippet is provided as the issue lacks specific implementation details.

Notes

The issue seems to be related to the plan-approval logic and session state management, but without more information about the implementation, it's challenging to provide a definitive solution.

Recommendation

Apply a workaround to temporarily resolve the issue, such as modifying the plan-approval logic to correctly handle Max plan users or implementing a session reset mechanism to recover from the poisoning effect, until a permanent fix can be developed and deployed.

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…
#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING