Re:Has Opus 5.5 gotten dumber for anyone else in the last fe...
by bbor on Sunday October 25, 2026 @11:57PM
(#50238922)
Well the biggest disconnect is that I rarely run the orchestrator model at medium -- I just checked the ArtificialAnalysis index, and Opus-5.5-xhigh is about as much better than Opus-5.5-medium than Opus-5.5-medium was than Opus-5-medium (~5 PP, or ~10%). If I'm letting a model plan changes and then orchestrate their implementation without talking through the details first, it's almost always worth it to me to pay for that extra intelligence.
The second biggest difference, though, is that I haven't used Opus 5.5 in a few days cause I ran out of credits on Thursday! So... you might be doing something right, there ;)
One thing you could check is the files that tend to get read into context, especially their built-in "memory" feature, which can get insanely cluttered if not actively maintained. This is why I prefer keeping everything I can to three other abstractions, none of them harness-specific: reports (roughly per-(long-)turn), policies (human readable, very concise, identified with unique slugs, system-wide), and tasks (Plane/Trello/Linear/etc., mentioned in git commits).
For something like "high level performance choices", a policy to always think about performance explicitly before reporting back could honestly do wonders. As you say yourself, they're typically smart enough to know what to do when reminded of your priorities or asked explicitly. The trick is to not prioritize everything, everywhere, all at once!
...so weird talking about how to best use these agents, BTW. Truly shuffling the deck chairs on our Titanic of a career/civilization.
The second biggest difference, though, is that I haven't used Opus 5.5 in a few days cause I ran out of credits on Thursday! So... you might be doing something right, there ;)
One thing you could check is the files that tend to get read into context, especially their built-in "memory" feature, which can get insanely cluttered if not actively maintained. This is why I prefer keeping everything I can to three other abstractions, none of them harness-specific: reports (roughly per-(long-)turn), policies (human readable, very concise, identified with unique slugs, system-wide), and tasks (Plane/Trello/Linear/etc., mentioned in git commits).
For something like "high level performance choices", a policy to always think about performance explicitly before reporting back could honestly do wonders. As you say yourself, they're typically smart enough to know what to do when reminded of your priorities or asked explicitly. The trick is to not prioritize everything, everywhere, all at once!
...so weird talking about how to best use these agents, BTW. Truly shuffling the deck chairs on our Titanic of a career/civilization.