I know there are a lot of other comments on this, but just adding for further analysis on this. Claude is nearly useless for me now and without Codex I would be back to human coding only at this point. I am using Claude 4.6 with high effort and also Codex, both on their max plan equivalents. Up until recently they both gave useful insight and feedback and I would use both to refine and review until a solid solution was agree on. This process worked great for a while. In the last week or so I started noticing Claude missing one or two issues which Codex was catching. This morning this difference is now stark, and Claude is now possibly more destructive and slowing me down to the point I think its no longer fit for purpose. I gave both Codex and Claude the exact same prompt today. Claude responded in 30 seconds with a 4 line assessment which missed many critical issues. Codex took about 5 minutes and did a deep dive on all the touch points. It came back with a lengthy topic for discussion and nailed it. I responded to Claude with the significantly more thorough review from Codex. Here is Claudes response (domain specific mentions filtered out by Codex): Claude: The other agent’s review is stronger than mine on three important points. Let me be direct about where they caught things I missed.
- Unified mutation pipeline prerequisite They’re right, and I missed this. I assumed there was a single authoritative mutation path and that using it would naturally propagate all derived-state updates. But there are multiple independent paths that mutate the same underlying state, and they do not currently share a rebuild pipeline. Adding another path on top of that fragmentation is likely to create inconsistencies. The prerequisite task to unify mutation handling is the right call.
- Non-destructive expiry / deactivation Their approach is better than the one I suggested. I proposed removing the state entirely. They proposed retaining the original record and marking it inactive with a timestamp. That is the better design because it preserves:
- auditability
- analytics
- support/debug context It also keeps runtime behaviour simple, because the effective state can be computed from “active” records only.
- Derived-state refresh gap This was a critical catch that I got wrong. I said the downstream recalculation would happen naturally if the mutation went through the existing update path. The other agent verified the implementation and found that the current invalidation/checksum logic does not include the relevant state inputs. In other words, a metadata hint exists, but it is not actually wired into backend recomputation. So the recalculation will not happen automatically. The unified mutation pipeline needs to trigger that refresh explicitly. One additional point they raised that I missed: do not let this expiry/deactivation happen while an active downstream workflow is in progress. Changing the underlying state mid-flight could create mismatches between what is being processed and what is now considered current. Their recommended sequencing is right. If Anthropic were honest and said they are upping their price for Opus to X, I would respect that. We are getting one hell of a deal for $200 a month. But this cloak and dagger bullshit is not acceptable. I need consistency. I will pay for it if needed. Just tell me upfront. Is the pay as you go API the answer? Who knows, they are not saying anything. submitted by /u/Appropriate-Fox-2347
Originally posted by u/Appropriate-Fox-2347 on r/ClaudeCode