Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Opus 4.6 stuck at 200k context on Max plan — s1mAccessCache hasAccess:false persists after re-auth (v2.1.107) [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#47785•Fetched 2026-04-15 06:42:25
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Hahyun-LeeHahyun-Lee
Participants
github-actions[bot]github-actions[bot]Hahyun-LeeHahyun-Lee
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1

Error Message

Error Messages/Logs

Code Example

❯ /context
   claude-opus-4-6
   54.3k/200k tokens (27%)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude Code v2.1.107 on Claude Max plan shows 200k context window instead of 1M for Opus 4.6. /context consistently reports xxx/200k tokens despite Max subscription.

Diagnostics from .claude.json:

  • s1mAccessCache: hasAccess: false (even after clearing cache and re-login)
  • cachedExtraUsageDisabledReason: was org_level_disabled (personal Max account, no org)
  • tengu_hawthorn_window: 200000 (server re-pushes after every restart)
  • hasAvailableSubscription: false

Steps taken (none resolved):

  1. claude auth logout → claude auth login (re-authenticated)
  2. Cleared s1mAccessCache to {} → server re-populates with hasAccess: false
  3. Manually set tengu_hawthorn_window: 1000000 → server reverts to 200000 on next sync
  4. Set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 → blocks sync but /context still shows 200k
  5. Fresh terminal, new session — same result

Impact:

  • Autocompact triggers at ~160k tokens (80% of 200k) instead of ~800k
  • Conversations are unnecessarily truncated, losing context mid-session
  • Paying for Max plan but receiving Pro-level context window

What Should Happen?

/context should show xxx/1000k tokens and autocompact should respect the 1M limit for Opus 4.6 on Max plan.

Error Messages/Logs

❯ /context
   claude-opus-4-6
   54.3k/200k tokens (27%)

Steps to Reproduce

  1. claude auth logout && claude auth login
  2. Launch claude (v2.1.107)
  3. Run /context
  4. Observe 200k limit instead of 1M

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Not confirmed (may have never worked on this account)

Claude Code Version

2.1.107

Platform

Anthropic API (claude.ai OAuth)

Operating System

macOS (Darwin 25.3.0, Apple M4 Pro)

Related Issues

  • #34158 — s1mAccessCache fix (didn't work)
  • #36649 — Context window defaulting to 200k (same symptoms, OPEN)
  • #47019 — hasExtraUsageEnabled stuck after plan change

extent analysis

TL;DR

The issue can likely be resolved by investigating and addressing the hasAccess: false value in the s1mAccessCache and the hasAvailableSubscription: false flag, which may indicate a subscription or authentication issue.

Guidance

  • Verify the subscription status and ensure that the Max plan is correctly applied to the account, as the hasAvailableSubscription: false flag suggests a potential issue.
  • Investigate the s1mAccessCache and its hasAccess: false value, which may be related to the authentication or authorization process, and try clearing the cache again or re-authenticating.
  • Check the related issues (#34158, #36649, #47019) for any potential workarounds or fixes that may apply to this case.
  • Consider reaching out to support or the development team to help resolve the subscription or authentication issue, as the problem persists despite attempts to clear the cache and re-authenticate.

Notes

The issue seems to be related to a subscription or authentication problem, and resolving this may require assistance from the development team or support. The provided information suggests that the issue is not solely related to the code or configuration, but rather to the account or subscription settings.

Recommendation

Apply a workaround by investigating and addressing the subscription or authentication issue, as the root cause of the problem seems to be related to the hasAccess: false and hasAvailableSubscription: false flags.

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#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Opus 4.6 stuck at 200k context on Max plan — s1mAccessCache hasAccess:false persists after re-auth (v2.1.107) [1 comments, 2 participants]