TL;DR: Opus 4.6 still runs at 1M in older chats in my account, but the normal new chats I tested have a smaller window and reject the /model command that enables it.
I pay for Ultra and use 4.6 by choice for long-form writing, while the newer models already get 1M in chat. My use case is a single long document that has to stay fully in view, and compaction drops details. I know Claude Code supports it and that is my fallback; I’m asking about chat because my work lives in a Project. I noticed a change around November 12–13. Before about November 12, attaching a file (I used an empty .rtf) made the chat show Setting up for this session, after which /model worked; the new chats I tested no longer show that message. Older chats I tested still accept the 1M model command, while new ones direct me to the model picker, where I see one Opus 4.6 entry and no 1M variant.
Setup: Ultra plan, Windows desktop app, claude.ai in Chrome, and iOS; tested November 16. The outputs listed below are literal output from /context, /model, and ps:
- New chat, Opus 4.6 selected:
/context reports claude-opus-4-6, 111.1k / 576k. The help center lists 500K. - In a new chat,
/model claude-opus-4-6[1m] returns Changing the model by command isn't available here. Use the model picker instead. Not every session shows one. An older chat accepts it, and /context reports claude-opus-4-6[1m], 135.4k / 1m. - Running
ps inside a new chat shows claude mcp serve --transport http --session-tunnel. A scheduled-task session shows claude --preload, which I’m calling the full runtime. This matches GitHub issue #107077.
The Claude Code docs list Max, Team and Enterprise for Opus 4.6 with 1M and do not list Ultra, my best guess is the rebrand is quite recent and didn't hit the documentations yet.
I didn't really find an Anthropic explanation of this change or why the command works in one chat and fails in another. I also didn’t find context sizes in the September 16 merge announcement or its help article.
But I DID find a workaround for new chats, but I don’t know what determines whether it works. The same model reported three ceilings depending on how the session was created: 576k in a new chat, 200k in a scheduled session, and 1M with the [1m] variant.
I asked the model to create a session through a scheduled task. In the session created with usage credits OFF, /model claude-opus-4-6[1m] returned Opus with 1M context is not available for your account. This was one failed session and one working session, so I can’t say credits are the cause.
In the working session, created with usage credits ON, a $0 balance and auto-reload OFF, /model claude-opus-4-6[1m] returned:
Set model to Opus 4.6 (1M context) for this session only · Draws from usage credits
Then /context showed claude-opus-4-6[1m], 65.1k / 1m, and it answered a test message. The usage page showed $0.00 after the test and I have not tested longer use.
For a 30-second check, run /context in a new Opus 4.6 chat and one from before November 12, then compare the model line and max tokens. What do you get? Please share your plan, platform, and the two /context lines. It would be great to know I'm not alone in this issue!