[BUG] 1M context window removed from Desktop Code tab model picker after v1.1.7714 update on Max plan
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
After updating Claude Desktop to v1.1.7714 (build 3bd6f6), the Opus 4.6 [1M] option no longer appears in the Code tab model dropdown on Max plan. Only "Opus 4.6" (200K), "Sonnet 4.6", and "Haiku 4.5" are shown.
The 1M option briefly flashes in the dropdown on launch, then reverts to plain "Opus 4.6". The /context command confirms a 200K ceiling.
Confirmed version regression: one machine had working 1M on the prior version with zero custom configuration. After updating to v1.1.7714, it disappeared immediately.
What Should Happen?
The model dropdown in the Code tab should show "Opus 4.6 [1M context]" for Max plan subscribers, as documented at code.claude.com/docs/en/model-config.
Error Messages/Logs
No error message. The 1M option silently disappears from the dropdown.
Also found stale s1mAccessCache in .claude.json with hasAccess:false from Dec 2025 that survived Reset App Data — this should be cleared by reset.
Steps to Reproduce
- Have a Max plan account
- Update Claude Desktop to v1.1.7714
- Open Code tab
- Click model dropdown — no 1M context option appears
- On launch, "Opus 4.6 [1M]" briefly flashes then reverts to "Opus 4.6"
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.1.7714 (3bd6f6)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Tested on two Windows 11 machines, same Max plan account. Both affected on v1.1.7714.
Extensive local troubleshooting performed — none resolved it:
- Removed stale ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL env vars
- Cleared s1mAccessCache from .claude.json (had hasAccess:false cached from Dec 2025)
- Removed oauthAccount field from .claude.json
- Replaced entire .claude.json with fresh auto-generated version
- Full Reset App Data + re-authentication
- Multiple Clear Cache and Restart
- Removed all ANTHROPIC env vars (verified at registry level)
- Cleaned settings.json of any model overrides
Note: s1mAccessCache persists through "Reset App Data" — this seems like a separate bug.
Likely related to #24208, #34143, #34333, #34435, #34593
17 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I think this issue is specific to Code tab within Claude Desktop. It was working until I updated this morning (March 19th)
I'm furious with Anthropic. The exact same thing happened to me. I'm a MAX subscriber, I use Claude Desktop with code on Windows, and to top it all off, when I got the subscription I was in the middle of a major refactoring of the software I was working on. The update broke my session and ruined a lot of work I'd already done. I had to back up my code because when the tokens were reduced, Claude Opus 4.6 went haywire and corrupted the code. A big slap on the wrist for Anthropic.
I've spent a hell of a lot of time debugging this and can add some specificity from my
main.logthat narrows the regression window:The
[1m]suffix disappeared between 18:36 and 19:59 UTC on March 19 — which lines up exactly with the ["Elevated errors on Claude Opus 4.6" incident] that was marked resolved at 16:16 UTC that day.Theory behind it: the incident resolution disabled or reset the 1M entitlement flag server-side for some subset of Max accounts.
What I've tried and hasn't worked (Claude desktop app + cowork on Mac)
oauth:tokenCachefrom~/Library/Application Support/Claude/config.json→ no effectANTHROPIC_DEFAULT_OPUS_MODEL: "claude-opus-4-6[1m]"in~/.claude/settings.json→ only affects CLI, Cowork ignores it entirely (of course it does, but I'm trying everything at this point).s1mAccessCachefinding)The
supported-features-info.jsonin my logs still showsyukonSilver: supportedandyukonSilverGems: supported, so the feature flags for Cowork itself are fine.. it's specifically the 1M model variant entitlement that's broken.This needs a server-side fix. Either the
s1mAccessCacheneeds to be reset for affected accounts, or the entitlement check that runs duringLocalAgentModeSessionManagermodel resolution needs to be patched.---
Hope this helps - ya'll are not crazy, this is very frustrating that we are paying $200/month for degraded service/features while Anthropic Support gaslights us like there's no issue.
Same issue here. Max plan, Claude for Windows v1.1.7714, Windows 11.
Timeline:
tengu_hawthorn_windowin.claude.jsonis set to200000by the servercachedExtraUsageDisabledReason: "org_level_disabled"keeps reappearing after deletionWhat I've tried (none worked for Desktop Code tab):
.claude.json(regenerated with 200K by server)tengu_hawthorn_windowto1000000(overwritten on next session)cachedExtraUsageDisabledReason(comes back)ANTHROPIC_DEFAULT_OPUS_MODEL=claude-opus-4-6[1m]in~/.claude/settings.json— works for CLI but Desktop Code tab ignores itDISABLE_TELEMETRYorCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICset anywhereConfirming @evanjcosgrove's analysis — this is a server-side entitlement issue that needs to be fixed by Anthropic. Local workarounds cannot override the Desktop's
LocalAgentModeSessionManagermodel resolution.Same issue here
Even worse for me.
I can not continue all the different COWORK sessions (projects) I used when the 1M context was available.
Whatever I type in there brings the "Prompt to long" error and I have no options.
Now I wait and hope the 1M context window for Cowork (with Max 20x Plan) comes back quick !!!
And boy did the 1M context made a difference for me. Now with the much smaller window claude feels like he forgets what he did 20 minutes ago frequently. This basically never happend with the 1M window.
I WANT IT BACK... PLEASE :-)
Same issue on Mac!
just updated to 2.1.89 and this happened to me in claude code. I think this was fixed for a bit and now it is back. When I manually try to set the model to 1m it tells me its not available on my account and links me to documentation that says it is infact available on max plan.
I use Claude Code in my terminal on the Max Plan, and I lost the 1M context window yesterday. It now automatically compacts and stops working with original 200K windows. Very frustrating. It had worked since they initially provided the upgrade, but regressed just yesterday for the first time. I really hope Anthropic address this issue soon, it's not just a display issue, the actual context window is limited to 200K.
I actually found a work around. If I run the command /model Opus[1M] it will in fact return to using the 1M context window. However, if your run the command /model Opus (without actually specifying the 1M) it will revert back to the 200K window.
Same issue here.... anthropic is full of bugs......
In my case just running the command to switch manually (
/model claude-opus-4-6[1m]) got it backI am having the same issue on windows
Note for VSCode extension users:
/model opus[1m]from the comments here does NOT work in the Code tab ("not available in this environment"). It's CLI-only.If you're in the VSCode extension and the 1M option disappeared from the picker, the env var workaround from #50083 works:
Add to
~/.claude/settings.json:Restart ->
/contextshows 1M. Confirmed working May 19, 2026.Also be aware that Anthropic's
unpinOpus47LaunchEffortmigration can silently remove yourmodelfield (#60240). Back up your settings.json after configuring.worked for me
same thing for Sonnet, just the manual fix in
~/.claude/settings.jsondoesn't workSame on the Desktop App:
<img width="1525" height="721" alt="Image" src="https://github.com/user-attachments/assets/52c6198d-76de-4054-9b61-576aa528d6dc" />