Morgan Linton

Codex, it's different.

It depends on what your methodology is.

And I think what we're seeing now, not just with vibe coding, but also with like,

overall like ai powered engineering is how how do you want to work with agentic coding do you want to have a totally autonomous experience where you're sending agents out to do work or do you want to work with an llm um like another teammate and pair program with the llm and that's where you're now seeing a divergence where i think you're going to see a lot of teams using both

because Codex really is your collaborator.

And what they've added with 5.3 is like really good, like mid-execution steering.

Whereas with Opus 4.6, it's probably the best of the best now being able to say, I want to spin up three or four agents.

I want them to go do stuff.

Hey, don't bug me.

I want to trust they're going to do good stuff.

And it's able to deliver.

Yeah, well, and you might be both.

Right?

That's true.

It might turn out that you're both.

That's why, like, not to disappoint people here, but we're not going to end this with me saying, and so the winner is... It's like, well, depends on what you want to do.

Everyone has a different methodology for it.

So I'll dive in and try to make this part fast because I know the fun part is probably us going in and playing around with both of these and having them do a head-to-head and...

try to build a competitor to poly market and however much time we have um but uh i'll just i'll just start kind of going into these uh at a high level just so for anyone wants to know like what are the core differences why is this so interesting um let's go into what that is so with with opus 4-6 uh much bigger context window so you have a million token context window here um

very strong coherence over entire documents and repos, designed for, you know, like load the whole universe and reason over it.