3 ms·

100k tokens it's basically nothing these days. Claude Opus 4.6M with 1M context windows is just a different ball game

operatingthetan 7mo ago
The context windows of these Chinese open-source subscriptions (GLM, Minimax, Kimi) is too small and I'm guessing it's because they are trying to keep them cheap to run. Fine for openclaw, not so much for coding.
bredren 7mo ago
I had thought this, but my experience initially was that performance degradation began getting noticeable not long after crossing the old 250k barrier. So, it has been convenient to not have hard stops / allow for extra but I still try to /clear at an actual 25% of the 1M anyhow. This is in contrast to my use of the 1M opus model this past fall over the API, which seemed to perform more steadily.
thawab 7mo ago
Don’t want to disappoint you, but above 200k opus memory is like a gold fish. You need to be below 150k to get good research and implementation.
- arcanemachiner 7mo ago
  Oh nice, I just wrote pretty much the same comment above yours.
syntaxing 7mo ago
I’m genuinely surprised. I use copilot at work which is capped at 128K regardless of model and it’s a monorepo. Admittedly I know our code base really well so I can point towards different things quickly directly but I don’t think I ever needed compacting more than a handful in the past year. Let alone 1M tokens.
braebo 7mo ago
The cost per message increases with context while quality decreases so it’s still generally good to practice strategic context engineering. Even with cross-repo changes on enterprise systems, it’s uncommon to need more than 100k (unless I’m using playwright mcp for testing).
arcanemachiner 7mo ago
Personal opinions follow: Claude Opus at 150K context starts getting dumber and dumber. Claude Opus at 200K+ is mentally retarded. Abandon hope and start wrapping up the session.
plandis 7mo ago
Claude Opus can use a 1M context window but I’ve found it to degrade significantly past 250k in practice.
- marcus_holmes 7mo ago
  Seconded. I'm getting used to the changes that happen in the conversation now, and can work out when it's time for my little coding buddy to have a nap. And Opus is absolutely terrible at guessing how many tokens it's used. Having that as a number that the model can access itself would be a real boon.
- airstrike 7mo ago
  250k is still massively more than 100k and 1M prevents it from having to compact
wild_egg 7mo ago
The Dumb Zone for Opus has always started at 80-100k tokens. The 1M token window just made the dumb zone bigger. Probably fine if the work isn't complicated but really I never want an Opus session to go much beyond 100k.
epolanski 7mo ago
Quality degrades fast with context length for all models. If you want quality you still have to compact or start new contextes often.

The context windows of these Chinese open-source subscriptions (GLM, Minimax, Kimi) is too small and I'm guessing it's because they are trying to keep them cheap to run. Fine for openclaw, not so much for coding.

bredren 7mo ago

I had thought this, but my experience initially was that performance degradation began getting noticeable not long after crossing the old 250k barrier. So, it has been convenient to not have hard stops / allow for extra but I still try to /clear at an actual 25% of the 1M anyhow. This is in contrast to my use of the 1M opus model this past fall over the API, which seemed to perform more steadily.

thawab 7mo ago

Don’t want to disappoint you, but above 200k opus memory is like a gold fish. You need to be below 150k to get good research and implementation.

arcanemachiner 7mo ago
Oh nice, I just wrote pretty much the same comment above yours.

syntaxing 7mo ago

I’m genuinely surprised. I use copilot at work which is capped at 128K regardless of model and it’s a monorepo. Admittedly I know our code base really well so I can point towards different things quickly directly but I don’t think I ever needed compacting more than a handful in the past year. Let alone 1M tokens.

braebo 7mo ago

The cost per message increases with context while quality decreases so it’s still generally good to practice strategic context engineering. Even with cross-repo changes on enterprise systems, it’s uncommon to need more than 100k (unless I’m using playwright mcp for testing).

arcanemachiner 7mo ago

Personal opinions follow: Claude Opus at 150K context starts getting dumber and dumber. Claude Opus at 200K+ is mentally retarded. Abandon hope and start wrapping up the session.

plandis 7mo ago

Claude Opus can use a 1M context window but I’ve found it to degrade significantly past 250k in practice.

marcus_holmes 7mo ago
Seconded. I'm getting used to the changes that happen in the conversation now, and can work out when it's time for my little coding buddy to have a nap. And Opus is absolutely terrible at guessing how many tokens it's used. Having that as a number that the model can access itself would be a real boon.
airstrike 7mo ago
250k is still massively more than 100k and 1M prevents it from having to compact

wild_egg 7mo ago

The Dumb Zone for Opus has always started at 80-100k tokens. The 1M token window just made the dumb zone bigger. Probably fine if the work isn't complicated but really I never want an Opus session to go much beyond 100k.

epolanski 7mo ago

Quality degrades fast with context length for all models. If you want quality you still have to compact or start new contextes often.