Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Anthropic API Error: Opus 1M context window not recognized after Max plan upgrade [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#56238•Fetched 2026-05-06 06:33:29
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
MihirjataniyaMihirjataniya
Participants
github-actions[bot]github-actions[bot]MihirjataniyaMihirjataniya
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description Title: Opus 1M context window unavailable after upgrading from Pro to Max

Environment:

  • Claude Code version: 2.1.126
  • Model: claude-opus-4-6
  • OS: macOS
  • Account email: [email protected]
  • Current plan: Shows as "Claude Pro account" (should be Max)

Description: After upgrading from Pro to Max, the 1M context window for Opus is not available. Running /model opus[1m] returns:

"Opus with 1M context is not available for your account."

/context shows a 200K context window (152.6k/200k tokens) instead of the expected 1M. /status still shows the login method as "Claude Pro account" despite having upgraded to Max.

It appears that Claude Code is not recognizing the plan upgrade and is still treating the account as Pro

Environment Info

  • Platform: darwin
  • Terminal: vscode
  • Version: 2.1.126
  • Feedback ID: 60e61aa5-cdb7-4944-ba84-c499a0951550

extent analysis

TL;DR

The issue is likely due to the account not being recognized as upgraded to Max, and a potential fix involves ensuring the account plan is correctly updated and reflected in the Claude Code application.

Guidance

  • Verify the account plan upgrade by checking the Claude website or contacting support to confirm the upgrade was successful.
  • Check the /status command output to ensure it reflects the correct account plan ("Claude Max account") after upgrading.
  • Try restarting the Claude Code application or logging out and back in to see if it updates the account plan recognition.
  • If the issue persists, provide the Feedback ID (60e61aa5-cdb7-4944-ba84-c499a0951550) to support for further investigation.

Notes

The issue seems to be related to the account plan not being correctly updated or recognized by the Claude Code application, rather than a technical issue with the Opus model itself.

Recommendation

Apply workaround: Contact Claude support to verify the account plan upgrade and ensure it is correctly reflected in the application, as the current workaround is to confirm the upgrade and potentially restart the application.

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…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING