Cursor ran a fleet of agents for close to a week in January 2026, and found GPT-5.2 best for extended autonomous work. When the experiment finished, the system had generated over a million lines of Rust code across a thousand files and built a browser rendering engine—HTML and CSS parsing, cascade, layout, text pipeline, paint, and JavaScript integration. The FastRender repo describes itself as “under heavy development,” and Simon Willison actually ran it and posted screenshots: it kind of works.
This experiment forced a question that every organization will have to answer in 2026: Is your AI shaped like a colleague, or is it shaped like a tool?
The conventional approach—comparing benchmarks, reading feature lists, picking whatever’s newest—misses what actually matters. Claude Code and Codex aren’t competing products in the same category. They’re built on fundamentally different philosophies about what AI should be and how humans should work with it. Senior engineers are reporting major productivity gains with Codex. Junior developers are struggling with the same tool and producing subtle bugs that compound into major problems. The difference isn’t skill. It’s fit.
Here’s what’s inside:
The CNC Machine Metaphor — Why this distinction determines whether AI multiplies your output or multiplies your mistakes
Why Senior Engineers Are Flocking to Codex — The specific capability that matters more than coding-specific training
Why Junior Developers Prefer Claude Code — What looks like friction is actually the mechanism that catches errors early
The Self-Awareness Challenge — Most people overestimate their ability to specify precise intent, and the consequences stay invisible until they’re expensive
The Non-Technical Frontier — What “high-grade intent” looks like outside software, and why figuring this out will define competitive advantage in 2026
The question for 2026 isn’t which AI is better—that question doesn’t make sense. The real question is whether you’re honest with yourself about which situation you’re actually in.
Listen to this episode with a 7-day free trial
Subscribe to Nate’s Substack to listen to this post and get 7 days of free access to the full post archives.













