I use Opus for planning, through API on medium thinking, it doesn't cost anything significant and the rest can be happily done with deepseek or glm flash. Using sol 6.1 for review loops at the end. All running on pi.
replyA very complex task tends to cost like 10$ max. It's comparable to a subscription with enormous flexibility.
It's a steal.
Honestly, I don't know what people see in Sol 6.1. Opus 5.5 is so much more inteligent, as in proactive, avoiding stupid mistakes, where it contradicts itself, ignores the context. Sol 6.1 has a gold-fish memory, it's as annoying for me to work with as Opus 5 was.
replyI'd rank Sol 6.1 only slightly behind Opus 5.5 in intelligence and both significantly ahead of anything else I've used (though cheaper/faster models are totally fine for a lot of tasks). My only real annoyance is 6.1 Sol is one of the slowest models I've used, which does make Opus 5.5 more pleasant to use.
replyYou can override the context length of Sol to 1M
replyWithout this change I hated Sol and was burning tokens way faster due to all the forced compacting.
replySince making this (obscure/hidden) change I enjoy Codex much more.
The work I do cannot fit in 256k so it was just relearning the same things over and over again while making zero progress. AFAIK the 1M burns tokens at twice the rate but I use Sol on medium as the work I'm doing now needs more memory than it needs intelligence and it's working great. I use Opus 5.5 for the stuff that needs stronger intelligence.
replyThat's not actually the problem. It forgets the instructions from 15 minutes ago, without context compression involved in-between.
replyThat has not been my experience after bumping it up to 1M. I do run a lot of agents in parallel ~10-16 and I actively babysit them so perhaps I'm just used to reminding the agents with things I've already told them. But I don't notice much of a difference between Sol 6.1 1M and Opus 5.5 1M
reply