Opus 4.6 with 1M context unavailable for Max 5x subscriber
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Mar 15, 2026 · closed May 28, 2026
I'm a Claude Max 5x subscriber. According to the March 13, 2026 announcement, Opus 4.6 now supports 1M context and should be enabled by default for Max users.
However, in Claude Code v2.1.76 (Opus 4.6 · Claude Max), running /model opus[1m] returns:
Opus 4.6 with 1M context is not available for your account.
Environment:
- macOS (Darwin 24.6.0)
- Claude Code v2.1.76
- Plan: Claude Max 5x
Is this still rolling out, or is there a configuration step I'm missing?
<img width="1232" height="167" alt="Image" src="https://github.com/user-attachments/assets/9ac7f1b6-ea5f-4ae8-9f62-baafa0ff50e8" />
11 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is happening on my 20x plan on linux only. Mac install works ok. Tried full removal and reinstall + reauth on linux server and still can't get opus 1m.
me too
Found a workaround via #34435:
Set the environment variable:
Or add it to
~/.claude/settings.json:<img width="677" height="366" alt="Image" src="https://github.com/user-attachments/assets/202178e9-3949-4421-85fc-4e3892ddf0e1" />
Both approaches work. The original question remains — shouldn't this be the default for Max subscribers?
also facing this issue. dont know if it makes a difference but recently undid my NPM installation in favor of native installation and I am on Linux (WSL). happened in the last few hour randomly lol.
"Opus 4.6 with 1M context is not available for your account."
I have the same issue
Opus 1M doesn't appear in the
/modellist and trying to set it by name anyway results in error:Can confirm the env var workaround worked for me
But it seems totally incoherent that it will first respond that that model is unavailable (not just non-default) and then setting it as 'default' makes it available
Current version: 2.1.85Actually just setting
"model": "opus[1m]"in~/.claude/settings.jsonwithout any env var stuff works for meThis sets it as currently active and then it also appears in the
/modellistNone of these workarounds worked for me on Win10. Still stuck unable to even use Claude Code currently.
followup on this w/ a real root cause, since i cracked it today. was on opus 4.7 this time but same rejection pattern as the original 4.6 report.
the problem wasn't
/model opus[1m]being unavailable for max, it was that the oauth token minted byclaude loginhadsubscriptionType: nulland norateLimitTierfield. server-side entitlement reads that field, sees no tier, denies 1m regardless of actual plan.fix:
fresh token came back w/
subscriptionType: "max",rateLimitTier: "default_claude_max_20x", 1m worked immediately. no travel, same network, wsl2 install where the initial token was just malformed.quick check before re-auth:
if
rateLimitTieris missing, that's it.related: #43639 has a side-by-side credential comparison proving this exact pattern, #39482 @harrisonaedwards hit the same fix via a different trigger.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.