Things have been degrading super fast in Claude Code. I still use Claude Code, but my default is now Codex. I still prefer Opus models for c…

Things have been degrading super fast in Claude Code. I still use Claude Code, but my default is now Codex. I still prefer Opus models for coding, and so I will try again with the fixes. I appreciate the post-mortem, but I don't trust that all issues have been resolved. Claude Code, in general, has been barely usable for me in the past couple of days. I got excited about Opus 4.7 (1M), but there is something really off about the thinking/reasoning. The model tends to either put in too much or too little effort, no matter the setting. I prefer it's smarter about how much effort to put. Responses are too verbose, and it really degrades the experience. In a lot of cases, I find myself doing things manually that Opus 4.6 had no issues solving for me at all. As they report, it might not be the model. But that means that the harness required a bit more testing. Not my favorite type of thing to tweet about, but as an avid Claude Code user, I would prefer that the Claude Code team properly test things before shipping them. Look, it's nice to show that you can move fast, and it's necessary in some instances, but the user experience cannot be the tradeoff. There are a lot of people (including myself) who depend on the quality of the product for very important work. The Claude Code experience has been so bad for a lot of devs I know (and me), so I've recently been more open to exploring other coding agents/harnesses. Also worth checking out Hermes Agent, pi, and OpenCode. I have nothing but love for the Claude Code team, but I hope they consider reassessing their strategy for how they move forward with improvement releases. Over the past month, some of you reported Claude Code's quality had slipped. We investigated, and published a post-mortem on the three issues we found. All are fixed in v2.1.116+ and we’ve reset usage limits for all subscribers.

Source: DAIR.AI (X) | 2026-04-23