MatIntellect

👀 For a few weeks I worked closely with both - and the answer to "which is better" turned out to be unexpected. Spoiler: I choose to use them together. Now to the details

My personal take on Codex and Claude:
Codex writes code well - and checks code written by others even better. It's especially sharp at tearing apart what Claude wrote: finds weak spots, points out architectural mistakes, suggests alternatives. Claude is different: strong at planning, great at building architecture, sees the whole system on the first try. In code quality they're roughly equal - but there's one fundamental difference that changes the whole pipeline

The main gap - the context window:
📌 Claude Opus 4.7 - 1 million tokens, holds the entire codebase in memory at once
📌 Codex ChatGPT 5.5 - a context window 4 times smaller‼️, but it focuses well on a specific chunk
📌 The upshot - Claude handles systems thinking, Codex - pinpoint analysis

That's exactly why they're not competitors - they're complementary tools with different strengths

How I split the roles between them:
⚡️ Claude - planning, writing the architecture, first-pass code
⚡️ Codex - fact-checking what's been written, critiquing decisions, final approval
⚡️ The combo - always together, never solo

This isn't about convenience - it's a qualitatively different result. Claude with its 1M tokens keeps the whole project in its head and writes code in the context of the entire system. Then Codex looks at a specific module with fresh eyes and finds what Claude might have missed precisely because it saw too much. I got this after the very first joint session - two tools gave a better result than each one on its own

And this is only the beginning. Ahead are big multi-level architectural systems where every stage has its own model plugged in. One is in charge of architecture - like Claude now. Another checks and critiques the code - like Codex. A third generates images. A fourth conducts the agents. Not one universal model - a whole orchestra of specialized ones. And the sooner you start thinking this way - the faster you'll get to systems that really work above the level of an average developer

💻 In practice a multi-model pipeline is cheaper and better than one model for every task

⭐️ Andrej Karpathy, former Director of AI at Tesla, OpenAI co-founder:

"The hottest new programming language is English"

How it's laid out for me now

The multi-level system I wrote about is already running. The brains of my 8 agents are Sonnet 5 and Opus 5.5 for different roles: the marketer, copywriter and designer each live in their own Telegram topic. The marketer's morning brief is built by a plain Python program: 20 live questions people ask AI and 10 topics. The model then adds the meaning: what worked yesterday and what to post today. Over three months that has produced 80 daily briefs and 94 images, with me deciding at every step

Some tasks don't need a language model at all. I transcribe long calls on my own computer with a separate speech model: a 57-minute conversation becomes text in about 10 minutes, and clients' voices never leave the machine. The summary and tasks from that text are then written by a language model

For reliability, my personal agent Jes has a primary model and an automatic backup. If the first one fails, the second carries on by itself, and I find out afterwards rather than from a missed job. Those are the SIM cards: the right one switches on by itself and the work doesn't stop

If you want to start with two models, split them by role: one writes, the other checks. After a week you'll see which tasks the second one finds mistakes in most often, and that's where to keep it for good

🎯 "Claude or Codex?" is the wrong question. The right one: when Claude, when Codex, and how they complement each other. It's like a phone with several SIM cards: whatever country you travel to - the right one switches on by itself

Share:

No comments yet

Leave a Comment

Fields marked with an asterisk (*) are required