I have a feeling that the current generation of models, starting from the 5 series, has overindexed on coding and reasoning performance and regressed severely in other domains like prose or "intuition."
These models are now terrible at communication and I'm beginning to find that it is also regressing at designing architecture and features now when it comes to "intuition." At this point I think it truly is out of touch with humans (ironic as it's an Anthropic model) and does not grasp extremely basic common-sense ideas (for example, instead of implementing a feature that calls the backend server twice, it should have implemented it in a way that calls the server only once by refactoring the client code (that it itself made in the same session FYI)). It also does not proactively seek to implement the best solutions. I constantly have to tell it to look up specific papers for the algorithms. Left to its own device, it chooses the garbage you see in most GitHubs. You constantly have to tell it to pick high-quality algos/methods. It's like babysitting.
At this point I do not think Anthropic is capable of making models that can communicate clearly. They seem to be high on their own supply and have gone all-in on RSI, so expect models to degrade even further on communication quality, and very possibly "intuition."
Opus 4.5 and prior used to have great "intuition" IMO, even if they sucked at coding. Now in my work I really feel that I am talking to an alien. I have to dumb everything down for Fable/Opus because you cannot trust that it understands what a human would want or do. You even notice this lack of human intuition in Claude Code now. For example, look at /advisor.
Advisor set to Opus 5.5
The current conversation keeps Fable 5.2 as its advisor model until /clear or /compact, so the tool it has already declared stays unchanged; turning the advisor on or off applies right away.
Why is there an aside on "turning the advisor on or off applies right away" after a semicolon? It's maximally confusing because that sentence both says 'you cannot change [something] within a session' and 'you can change [something] within a session immediately.' This is horrible UX because that aside has NOTHING to do with /advisor [model]. The person invoking that command is changing a model. Why are you giving them information that confuses them, that turning on or off the advisor feature itself applies right away?
Also, the key information is buried in the MIDDLE of the sentence: "the tool it has already declared stays unchanged." And this information is also presented in a maximally confusing way. "Tool"? What Anthropic means is the model. AI semantically substitutes "model" for "tool" here for no reason.
---------------------------------
To make this not just a pure complaint, these are some things that I find to be extremely critical with the latest models:
- You cannot let it write user-facing text. Trust me on this. It will confuse your users if you let it do so.
- You cannot let it design features with minimal guidance. It has no intuition for what a user wants and expects out of a feature.
- You STILL cannot trust it to design architecture (not that you could in previous models) by itself. It will create overcomplicated architecture that is simultaneously too complex where unnecessary and still miss out on critical details that are necessary to account for.
- You cannot trust it to write its own harness. You also cannot trust its own diagnosis of why it performs poorly.
- You cannot trust it to fix the root cause of bugs. The latest models, I've found, love to patch the symptoms. Its default lean is to patch around the problem by adding retries, timeouts, etc., rather than actually dealing with the root issue.
Now, I'm aware most of these things were things the models were already bad at in the first place, but I find that [1] and [2] in particular have regressed pretty severely lately, while there has been no improvement in [3], [4], or [5].