Claude Opus 5 spots code issues earlier versions and Codex kept missing
PawelHuryn · x · 2026-07-25
The thread says the issues found are not random bugs, but ones previous Claude Opus/Codex sessions had also missed, plus synthetic analogs.
The commenter says this is a strange model: it was the first in the Claude family that did not understand the instruction “analyze this solution” and instead started inspecting uncommitted changes. At the same time, it did actions that initially seemed odd, like analyzing git history, but those steps led to unexpected insights.
The author also claims that in dozens of sessions with Fable 5 and Opus 4.8, essential issues were missed that Opus 5 identified.
Related event: GPT-5.6 Beats Claude Opus 5 in Bug Hunt Benchmark(3 posts)→
More from coding & agent
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11