Codex Does Too Much Busywork in Large Projects
Chipware · reddit · 2026-07-14
Comparing Claude Opus/Fable and Codex/GPT5.6 on large coding projects, the author's biggest takeaway is that Codex often looks busy but lacks actual output efficiency.
Typical behaviors described include:
- Spending a lot of time on prep work
- Writing a little bit of code occasionally
- Devoting most of the time to testing and verification
- Spending 20% of the time coding and 80% on looping, unproductive actions
Even when using /goal, Codex forgets the objective after context compression and requires manual intervention and reminders to actually start working. In contrast, the author finds Claude's status updates more purposeful and better at explaining the "why" behind its actions.
More from coding & agent
- 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
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11