I just set the context window to 100k and manage it actively (e.g. I compact it regularly or make it write out documentation of its current state and start a new session).
replyFor me, Opus 4.6 isn't working quite right currently, and I often use GLM 5.1 instead. I'd prefer to use peak Opus over GLM 5.1, but GLM 5.1 is an adequate fallback. It's incredible how good open-weight models have gotten.
When it works and its not slow it can impress. Like yesterday it solved something that kimi k2.5 could not. and kimi was best open source model for me. But it still slow sometimes. I have z.ai and kimi subscription when i run out of tokens for claude (max) and codex(plus).
replyi have a feeling its nearing opus 4.5 level if they could fix it getting crazy after like 100k tokens.
Why don't you start a new session or use the /compact command when context gets to 100k tokens?
replyFrom my testing it was ok until 145k tokens, the largest context I had before switching to a new session. I think Z.ai officially said it should be good until 200k tokens.
Using it in Open Code is compacting the context automatically when it gets too large.
Why is that sad? A free and open source model outperforming their closed source counterparts is always a win for the users
replyThe non-awesome context window is the sad part, but I think a better harness can deal with this.
replyI honestly still hold onto habits from earlier days of Claude & Codex usage and tend to wipe / compact my context frequently. I don't trust the era of big giant contexts, frankly, even on the frontier models.
replyI also feel like its helping me on the big models these days with claude giving so many issues.
replyAfter the context gets to 100k tokens you should open a new session or run /compact.
replyI've set max context to 180k and usually compact around 120k. It's much better to re-read stuff than to have it under-perform when it's over 120k.
replyIsn't the same with opus nowadays?
reply