...and if the benchmarks praise them so much while the community's experience is so different, then to me it is a sign that it's the benchmarks that are failing to measure practical parameters, rather than being the so called "skill issue" of the community.
Disclaimer #1: I am sorry that the post got somehow long as I was writing it; you should understand the post even just reading the second half if you don't want to read it whole. The TL;DR is that to me the 6.2 models feel the issue of being "Sheldon Coopers"; they are not stupid--but they are not picking up your intentions. What you often mean with your requests is not how they interpret them. Therefore they will either provide things you didn't actually ask for, or even if they will, they might not be able to explain you the way you wished.
Disclaimer #2: If 6.2 Astra/Sol is working well for you, I'm no one to tell you that your experience isn't true or worth mentioning; therefore I'd ask you not to just tell me that I'm wrong, but that you can hopefully share meaningful and detailed enough recommendations that may improve the experience of the other users. I'm here to describe from what I've read and what I've experienced, what the GPT-6.2 shortcomings are and why they are affecting so many users, including myself.
IMHO the main issue with the newer models is not that they're not "smart" or intelligent. It's that they are not aligned with the users' language/way to express things; plus other "practical" shortcomings in how they operate (of course, although being a programmer myself and knowing my stuff in ML and DL, I am not an AI engineer comparable to OAI ones therefore I cannot explain in detail why this is happening nor how it can be completely managed).
This has been described by other users as the "Opus 5" issue, that is, a model that while being smart, it doesn't pick up users' intentions, it seems to speak a different language, and rather than just prompting it tasks and getting work done, you have to constantly workaround with the model.
This is how yesterday this issue became far too evident with me: I asked GPT-6.2 to provide me the command to push to origin its work. You may wonder, if I claim to be a programmer, why would I ever ask a so simple question to Codex. And the reason is that my project has several worktrees, with several branches, and when subagents are delegated through my own agentic/container manager MCP, each subagent spawned gets its own worktree copy; maybe that is inefficient but that would be going out of topic. Also that agent whom I asked to, was spawned as a subagent of Claude Opus 5.5 through my MCP, therefore it was not manually managed by me and that's also why just for simplicity and to save time I asked the proper git push command to do to save its work.
So far, GPT-6.1 never failed me to answer this prompt. It straight-up always gave me the exact git push command of the branch it was working on, and telling me whether there other work to save besides that.
GPT-6.2-Sol however answered very differently, in this specific instance, and its instructions were something like:
"[...] from the [branch X] directory in the host checkout, run:"
git cherry-pick [...commit hash]
git push origin <branch X>
(of course I am editing out the hashes and branch name)
And its instructions got me suspicious, I immediately asked, "Can you explain the cherrypick?", as I just asked the instructions for a push and I was not doing merges and even less doing cherrypick merges.
And it proceeds to explain me what a cherrypick does (which I know); kind of it interpreted I was asking to explain how git works while I meant to ask why it was proposing a cherrypick.
Then I ask from which worktree in the host I should ran those commands (as the container in which the agents work has the filesystem mapped differently than how the files are on the host). It proceeds suggesting a cd to <relative path>, and then again the git cherry-pick and then push.
Since I had troubles understanding on which worktree it was working on I keep asking for instructions and I keep getting recommendations unclear to follow. I ask the agent why cannot it just do the merge itself and just provide me the push command, and the agents keep recommending the cherry-pick and blah blah blah.
Basically what with 6.1-sol had always been a clear and ready command to launch, with 6.2-sol I was having a back and forth discussion.
Since it was also quite late and I had to go to sleep and I had seriously enough of it, and I also wondered "was it me? Did I prompt it unclearly?" Thus I want the help of 6.1-sol instead, but I don't start a new fresh chat. I just fork the chat as it is, so that 6.1-sol can work with the exact same context, and I beg it to provide me just the exact git push command I need and that it was never so complicated to get the instructions to push to origin my GPT.
And then 6.1-sol just does it. It just picks up what I want, and gives me the proper command that I asked for.
And therefore, amazed as I was, seeing with my own eyes that it was gpt-6.2-sol that it was making it so unnecessarily utter complicated, asked gpt-6.1-sol explanations (since again, it had the very same context of gpt-6.2). And here it is its response:
Your request was straightforward. The earlier replies made it complicated by assuming “push tonight’s work to origin” meant “integrate tonight’s work into [branch X], then push that branch.”
That assumption introduced cherry-picking, finding another worktree, and explaining divergent history. Each follow-up defended that workflow instead of reconsidering whether you needed it. When you showed the host directories, you received another lookup command.
The work was already committed on [...]/annot-sol61. Pushing that branch satisfied your request immediately.
I had the same conversation history. The difference was the interpretation I chose. You shouldn’t have needed to rephrase the request or switch models to get that result.
This exchange supports a concrete criticism of the earlier responses. It doesn’t establish why 6.2 behaves that way generally, and I don’t have access to its internal reasoning. Benchmark performance also doesn’t tell you whether a model will handle ordinary collaboration with sensible assumptions and proportionate effort.
If you keep using it, one standing instruction might help—
> For routine Git requests, give the shortest command that satisfies my stated goal. Use the current branch unless I explicitly name a destination branch. Treat integration and publishing as separate requests.
But that is a workaround for the model’s behavior. Your original request was sufficient.
See? Not only it picked up my intentions immediately, from the very same context thus it was not bad prompting, but it also inferred why GPT-6.2-Sol got it wrong. The way I see it is that the GPT-6.2 just speak a different language from most humans. You probably will be able to get wonderful work from them with "proper communication", yet I believe that not being able to pick up "simple" prompts is an issue that should be fixed. If the model fails to understand user's intentions and even more fails to make the users' to understand its own intentions, there is an issue to fix.
Even more so I don't think that Claude Opus 5.5 receives the praise it receives because it writes better code; I think both GPT-6.1 and 6.2 are both better coders than Opus 5.5. However, Opus 5.5 is just even better than GPT-6.1 Sol in picking up users' intentions. And not only that but it is more "practical" as well.
I suggest that models should not just be evaluated in correctness and being able to get good results, but also in "practicality". To summarize it: a model that is fully correct yet completely impractical is close to useless (at least when you have better alternatives); on the other hand, a model that is practical (it gets stuff done, doesn't go into tangents etc.) yet very incorrect is an unreliable model. Therefore you need a tradeoff between correctness and practicality. Why do people love Opus 5.5? Because it's likely the "best" model (as of today) in trading off correctness and practicality.
I don't ask you to take my word for it. If you are getting similar issues with GPT-6.2 Astra/Sol, just attempt the same yourself, fork the chat, switch to a model like 6.1-Sol, and just ask it to give you what you have been asking for. If it picks up your intentions with the exact same context, then you were not "bad prompting" and do not let yourself gaslit by other users about it.