Opus 1M context on Max plan requires extra usage despite docs saying 'included with subscription'

[andersonaggie05]

Opus 1M context on Max plan requires extra usage despite docs saying "included with subscription"

Summary

On a Max 5x plan, opus[1m] is blocked unless extra usage is enabled, and when enabled it says "Billed as extra usage." The official docs explicitly state Opus 1M on Max plans is "Included with subscription."

Environment

• Claude Code version: 2.1.85
• Plan: Max 5x ($100/mo)
• OS: Windows 11 Pro
• Model: opus (default), attempting opus[1m]

Steps to Reproduce

1. Have a Max 5x subscription with extra usage disabled (a valid configuration to prevent surprise charges)
2. Run /model opus[1m]
3. Observe: "Opus 4.6 with 1M context is not available for your account"

Expected Behavior

Per the model config docs:

On Max, Team, and Enterprise plans, Opus is automatically upgraded to 1M context with no additional configuration.

Plan	Opus 4.6 with 1M context
Max, Team, and Enterprise	Included with subscription

Opus 1M should work on Max plans regardless of extra usage settings, since it's "included with subscription."

Actual Behavior

1. With extra usage disabled: /model opus[1m] returns "not available for your account"
2. With extra usage enabled ($0 cap): Still blocked — cachedExtraUsageDisabledReason changes from org_level_disabled to org_level_disabled_until, access still denied
3. With extra usage enabled ($1 cap): Model selection works, but displays "Billed as extra usage" — contradicting the "included with subscription" documentation
4. Context window feature flag unchanged: Even after selecting opus[1m], the cached GrowthBook feature tengu_hawthorn_window remains 200000 instead of updating to 1000000, suggesting the actual context window may not change even when the model is accepted

Additional Details from .claude.json

• cachedGrowthBookFeatures.tengu_hawthorn_window: 200000 — context window locked at 200K regardless of model selection
• cachedExtraUsageDisabledReason cycles through: org_level_disabled -> org_level_disabled_until -> out_of_credits depending on extra usage configuration
• oauthAccount.hasExtraUsageEnabled: true contradicts cachedExtraUsageDisabledReason values
• lastModelUsage shows claude-opus-4-6[1m] has been used before, suggesting this may be a regression

Impact

Max plan users who responsibly disable extra usage to prevent surprise charges are denied a feature that is documented as included with their subscription. This effectively forces users to enable extra usage billing to access something they've already paid for.

Suggested Fix

The 1M context access check should distinguish between:

• Opus 1M on Max/Team/Enterprise — included with subscription, should NOT require extra usage
• Sonnet 1M on Max — correctly requires extra usage per docs

Additionally, when opus[1m] is selected, tengu_hawthorn_window should update to 1000000 to ensure compaction uses the correct context window size.

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Opus 4.6 with 1M context is not available on Max 5x plan #34333
2. Opus 4.6 with 1M context unavailable for Max 5x subscriber #34585
3. [BUG] 1M context unavailable on Max plan — Windows 10 #39482

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[canucklehead2001]

I changed my usage limit to $1 to test this and had zero change, not even the false positive of the 1M above

[marlvinvu]

My Claude says your issue appears to be similar to issues #39482, #39000, #39107. Please keep updating. I also want to know whether this has been fixed yet.

[gavin604]

I have been charged as well. Could you please let me know how I can apply for a refund from you?

[jpwinans]

I was also charged, even with only having less than 50% weekly usage, and never exceeding my 5-hour session usage limits. I sent proof with screenshots to a human support agent, but it sat all day with no response.

[Portll]

My issue is the same as this.