1M context is now generally available for Opus 4.6 and Sonnet 4.6
1–10 of 565 posts
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#2[deleted]
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#3The big change here is:
> Standard pricing now applies across the full 1M window for both models, with no long-context premium. Media limits expand to 600 images or PDF pages.
For Claude Code users this is huge - assuming coherence remains strong past 200k tok.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#4Claude Code 2.1.75 now no longer delineates between base Opus and 1M Opus: it's the same model. Oddly, I have Pro where the change supposedly only for Max+ but am still seeing this to be case.
EDIT: Don't think Pro has access to it, a typical prompt just hit the context limit.
The removal of extra pricing beyond 200k tokens may be Anthropic's salvo in the agent wars against GPT 5.4's 1M window and extra pricing for that.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#5Is there a writeup anywhere on what this means for effective context? I think that many of us have found that even when the context window was 100k tokens the actual usable window was smaller than that. As you got closer to 100k performance degraded substantially. I'm assuming that is still true but what does the curve look like?
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#6Is there a writeup anywhere on what this means for effective context? I think that many of us have found that even when the context window was 100k tokens the actual usable window was smaller than that. As you got closer to 100k performance degraded substantially. I'm assuming that is still true but what does the curve look like?
The benchmark charts provided are the writeup. Everything else is just anecdata.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#7This is super exciting. I've been poking at it today, and it definitely changes my workflow -- I feel like a full three or four hour parallel coding session with subagents is now generally fitting into a single master session.
The stats claim Opus at 1M is about like 5.4 at 256k -- these needle long context tests don't always go with quality reasoning ability sadly -- but this is still a significant improvement, and I haven't seen dramatic falloff in my tests, unlike q4 '25 models.
p.s. what's up with sonnet 4.5 getting comparatively better as context got longer?
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#8Noticed this just now - all of a sudden i have 1M context window (!!!) without changing anything. It's actually slightly disturbing because this IS a behavior change. Don't get me wrong, I like having longer context but we really need to pin down behaviour for how things are deployed.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#9Is there a writeup anywhere on what this means for effective context? I think that many of us have found that even when the context window was 100k tokens the actual usable window was smaller than that. As you got closer to 100k performance degraded substantially. I'm assuming that is still true but what does the curve look like?
I mentioned this at work but context still rots at the same rate. 90k tokens consumed has just as bad results in 100k context window or 1M.
Personally, I’m on a 6M+ line codebase and had no problems with the old window. I’m not sending it blindly into the codebase though like I do for small projects. Good prompts are necessary at scale.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#10Oh nice, does it mean less game of /compact, /clear, and updating CLAUDE.md with Claude Code?