Claude Opus 4.6 vs GPT-5.3 Codex: Live Build, Clear Winner

0:00 Today is a massive day because Anthropic just dropped Opus 4.6 and OpenAI answered with GPT 5.3 Codex. But what is the better model and how do you get started and what are some tips and tricks to get the most out of them? Well, this episode is all about that. This is for the technical person who's trying to get the most out of these models, who don't just want hot takes, who want tactical sauce for getting the most out of these models.

0:29 This episode of The Pod is with my dear friend, Morgan Linton. Morgan is one of the best engineers I know. He was an executive at Sonos. He's invested in a lot of AI companies, and he's building an AI company of his own. He's one of my first calls when I'm like, hey, which model's better? So we put the models head-to-head, and there's a winner at the end.

0:49 We rebuild Polymarket, a multi-billion dollar app, but we use these models. So which is the better one? You'll find out by watching this episode, but you'll also learn to become a better AI developer because you'll have these tips and tricks in your back pocket. I'm with one of my favorite people, Morgan Linton.

1:15 You might not know him, but he is just, you know, just an incredible developer, founder, entrepreneur, investor. He does it all. But today, what I needed him to help me understand is Opus 4.6 just came out. GPT 5.3 Codex just came out. Morgan, help me understand. By the end of this episode, what are people going to get out of this?

1:38 Yeah, well, Greg, thanks for having me. Super exciting day. It's moving fast today. Opus 4.6 came out, and then Sam Altman put together a quick tweet, I want to say maybe 18 minutes later, announcing GPT 5.3 Codex. and me and I think everybody else has been jumping on it, playing around, figuring out the differences, you know, all the little neat new settings that there are in each of these.

2:02 By the end of this, you're going to know first how to make sure that you are running Opus 4.6 and all of the little details you can change in the settings.json file to use some of the cool features in Opus 4.6, especially agent teams, which is probably the feature I'm the most excited about. it'll also understand why you might use one versus the other because they both kind of tackle different engineering methodologies and then hopefully you'll see some cool stuff as we build some demos together that i've put together that i haven't tried myself so i'll be trying just live with you so we'll see how that goes cool i think one of them is we're going to try to recreate polymarket yes and see which model performs best yeah we're gonna have both

2:47 they're going to do a head-to-head to try to each build their own version of Polymarket. So by the end of this episode, you will have a pretty good understanding of how to use the models, when to use the models, how to get started. Morgan, let's get into it. Cool. Right on. All right. So I took some notes and essentially, you know, with 5.3 Codex, I'll be showing that in the desktop app on Mac because they're super excited about that.

3:13 I'm excited about it. I think if OpenAI was wanting a demo to be done the right way, they would want me to do it in their app. Whereas with Opus 4.6, I would say the Anthropic team would want me to do it in the CLI. And so there's a few different configuration settings that you do want to make sure that you get right when you're using Opus 4.6 or trying to use Opus 4.6 today, tomorrow, whenever it is that you're jumping in to use it.

3:39 I've seen a lot of people online today on Twitter saying, it's weird, I'm having a problem. Like it's supposed to be agent teams, but I don't see them or how do I know what version I'm running? So I thought, let's start by just giving everybody a level playing field to know, okay, I wanna be able to use quad code with Opus 4.6.

3:57 How do I make sure I'm doing that and doing that correctly? So here's kind of the initial to-dos that everyone should have on their list. Just do an NPM update, see if that does the trick. If that doesn't and you're running an older version, then run clod update. But you should see, as of right now, it's 2.1.32.

4:20 If you see 1.something, you're running an old version. And then what you want to do is go into your settings.json, and I'll just show this here. So if you just do cd tilde slash .clod. So I bet that there's people who are running the old model, they don't even realize it. I have no idea. It's probably a bad result.

4:44 I have no idea. Yeah, yeah. So, I mean, make sure you go in here, cd://.cloud. Here's your settings.json. If you view this, here's essentially what you should see. Now, it's okay. It can be model. If you want to, like, really be specific about it, you can put in cloud-opish-4-6. That'll lock it in. But because 4.6 is the newest model, you can also just put in model and just opus, and that'll work.

5:14 The key thing that you want to do is, in my opinion, the coolest feature that they added with 4.6 is agent teams. I'm super excited to demo that with you. You have to make sure to turn that on because it is an experimental feature. And that's probably the biggest confusion I'm seeing people have today with Opus 4.6 is that they are running Opus 4.6.

5:35 They keep hearing about agent teams and they're giving it prompts like, build a team of agents, do this and this. And it's not quite doing it. and that's because you do have to enable this. So you do have to add in end this Cloud Code Experimental Agent Teams and then set it equal to one, okay? Nothing too crazy.

5:53 Once you do that, that will make all that possible. So with that in mind, you're pretty ready to go there. Then you can just run Cloud in the terminal and you're good. For people that are using the API, the one thing I did want to point out is there's a pretty cool new addition, which is called adaptive thinking.

6:14 Also, just to be clear, because I'm seeing confusion on this too, this is in the API. This is not in Cloud Code itself. But adaptive thinking, just to show it here, you're able to essentially pick the level of effort that you would like the model to use. This is only going to work in 4.6. By the way, if you want to use like an effort level of max.

6:37 And so here's kind of a different level. So with Max, Cloud always thinks with no constraints on thinking depth. It's Opus 4.6 only. So requests using Max on other models are going to return an error. So if you're calling the API and you set the effort level to Max and you get an error, then you're probably not using Opus 4.6.

6:56 But here's the example where you can see if I'm calling the API, I set the model to Cloud Opus 4.6, and then here's where I can set the effort. And this is another thing. If you're using existing API code, you may have the model of Opus 4.5, and now you adjust the effort to max. It gives you an error.

7:13 All you need to do is just bump the version, and you're good. But this is kind of a neat thing they've added to the API with 4.6 that's worth mentioning. And then kind of the last thing I would say is just if you want to use split panes for agents. so if you want agents to show up in different panes and you're using something like warp just make sure to install tmux you can do this with brew install tmux and then if you do that it's going to default to auto which usually means in process which means in that same terminal window you have the agents are going to be working all together if you want it to split pane then you just need to update that setting in the settings.json to split panes I'm not going to go into super details on that, but those are just like, I think, good housekeeping to start with for anyone using Opus.

8:06 But don't worry about it. Really, all that anybody needs to do, especially if you don't even want to use Teams, agent Teams, is just make sure you're updated using the newest version and that the model is Opus and you'll be using Opus 4.6. Cool. So that's that. Before I get into kind of the differences between Opus 4.6 and Codex, I thought I would actually read this because this was posted on Hacker News four hours ago and I was reading it.

8:36 I was thinking that's like the best way to explain it. So I'm just gonna read this little section here because I think they do such a good job with it. This person's saying, what's interesting to me is that GPT-5 through Opus 4.6 are diverging philosophically and really in the same way that actual engineers and orgs have diverged philosophically.

8:55 I think this really nails it. With Codex 5.3, the framing is an interactive collaborator. You steer it mid-execution, stay in the loop, course correct as it works. With Opus 4.6, the emphasis is the opposite, a more autonomous, agentic, thoughtful system that plans deeply, runs longer, and asks less of the human.

9:16 That feels like a reflection of a real split in how people think LLM-based coding should work. Some want tight human-in-loop control, Others want to delegate whole chunks of work and review the results. And I honestly, I think that says it beautifully. And I think that nails the differences. And also hopefully, you know, everybody wants to pick a winner where it's like, oh no, no, Opus 4.6 is better.

9:40 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 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?

10:01 Or do you want to work with an LLM 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.

10:23 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, and don't bug me. I want to trust they're going to do good stuff and it's able to deliver. So are you saying that there, in some ways, it's just a preference, like depending on how, you know, there's no right or wrong, basically, you know not wrong to be an opus person or you know it just like might feel yeah it's just a preference 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

11:10 um for it so i'll dive in and try to try to make this part fast because i know the fun part is probably us going in and uh playing around with both of these and having them do a head-to-head and try to build a competitor to polymarket 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 just going to what that is so with with opus 4.6, much bigger context window.

11:43 So you have a million token context window here. Very strong coherence over entire documents and repos designed for, you know, like load the whole universe and reason over it. 5.3, they talk about large context, but it's not a headline feature. And I actually went back and forth with it to get it to actually give me a number.

12:05 And the number is around 200,000 tokens, which is not that impressive. That's smaller than I was thinking it would be. But that's okay. It's optimized, you know, for progressive execution rather than total recall. So that's why that's not as important. And, you know, optimized for deciding like what to keep in working memory.

12:25 So high level, what that means is Claude is better when the task is understand everything first and then decide. GPT-5-3 codecs are probably better when the task is decide, fast, act, iterate more of that, you know, pair of programming, you know, mid-task change behavior. For coding benchmarks, you know, Opus 4.6 is really good at code-based comprehension refactors with like architectural sensitivity explaining why a system behaves a certain way and then, you know, a little less tendency of this like YOLO write code, right?

13:03 That's good. Which is, I think, something everybody wants. Yeah, exactly. So, you know, that's good for everybody, but especially for vibe coders that are getting started and they may not be able to identify hallucinations. Opus 4.6 is definitely going to perform better there. But then for teams, you know, building in large code bases like me and my team are doing, that's also really important.

13:26 And so kind of a win for everyone there. 5.3 Codex did win on SWD Bench Pro, Terminal Bench. Overall, it's like scored better on coding benchmarks. So probably better end-to-end app generation. And, you know, Claude's kind of like senior reviewer, staff engineer. GPT 5.3, probably like your founding engineer, right?

13:49 Agentic Behavior, Opus 4.6. This is the key one, right? It's like the multi-agent orchestration. that's that's probably like the bleeding edge feature in four six and then with with with five three codecs really like task driven autonomy build test modify without being asked but then this task steering you can watch it you can go in it's like your buddy's coding and you can say wait wait man wait why are you doing this and you can stop it and it'll go okay and then you can restart you can really fix things in line much harder to do that with with opus with opus you'll kind of be stopping it and then starting somewhat fresh but it has a pretty big context window so so it knows what it did um but you know claude's really asking like should we do this gpt gpt 5.3

14:38 is like how fast can i ship this right it's really i mean it's so cool because it almost feels like they're different people you know i mean like they have different styles yes totally yeah it's a good way to look at it it's like a different it's like a different personality type right and then yeah uh failure failure modes uh you know clod 4-6 it might overanalyze it's got a much bigger context window i can hesitate when when requirements are ambiguous and then it can stop short on a full execution uh five three codecs uh could be overconfident can lock in a flawed assumption early but you can steer it back in the right direction if that if that happens so that's kind of a high level overview on the on the two cool that's helpful yeah so should we should we just

15:30 dive in i haven't tested any of this so this is not i have like zero can demos because i thought it'd be more fun just to try something together and see what happens. So should we, should we try it? Yeah. Okay. So let's see. I'm going to, I'm going to start with Opus and I've got these prompts preloaded.

15:49 So I'm giving different prompts, just like, I think you said it really well. It's like, you're talking to different people. And so, you know, when I'm talking to Opus, I can tell Opus, build me a team, and here's what I want each member of the team to do. When I'm talking to Codex, I can't really tell it to build me a team, but I can tell it to think about stuff.

16:10 So the prompt that I'm gonna give to Opus is build a competitive polymarket, create an agent team to explore this from different angles, one team made on technical architecture, one on understanding polymarket and the ins and outs of prediction markets, one on UX, and one that just works on building really good tests to make sure everything works.

16:29 For Codex, I'm going to give it a little different prompt, but very similar. So still build a competitive polymarket, but now think deeply about technical architecture, understanding polymarket and the ins and outs of prediction markets, good clean UX, make sure it builds really good tests, make sure everything works.

16:47 And to be fair, I'm going to try to paste these in around the same time. You're a fair guy, Morgan. I'm trying to keep it fair here, right? It's the only way to do it. Like I said, no winners or losers. It's just about letting everybody have a fair shot to play the game. Yeah. All right. So let's see.

17:07 I'm going to make different directory streams. So I'll do, let's just call this Opus45 Folly Market Competitor. All right. So let's fire up Cloud in here. By the way, if you want to check when you're running, just to like really make sure that you're in a good place, But the model, if you type slash model, I can see here, right?

17:31 Cloud Opus 4.6, right? So I'm good there. I'm going to take this prompt, copy it. Make sure this is all copied incorrectly. Okay, got that. I'm not going to hit enter yet. I'm making this totally fair. I don't want anyone at Anthropic or OpenAI to get upset with me. So I want to be in good terms with both of them.

17:55 Totally. Smart guy. Let's see. Oh, wait, actually, you know what? I do want to create a new folder for this. But we are keeping it real. We're being objective. Yes. Neither myself or Morgan are affiliated with either. Well, actually, I don't know about you. I'm not affiliated. No, I'm not. I'm not. Nope.

18:13 Nope. I love them both equally. How about that? Yeah. Okay. And I'm going to try to start as close to the same time as I can. Enter. Go. All right. They're going off to the races. So what do you think is going to happen? That's a great question. Well, I know right now because I told Opus 4.5 to build using different teammates, it's going to do that.

18:45 So you can see here it says, I'll build a Polymark competitor by launching parallel research agents first, then synthesizing their finding to a comprehensive implementation planning code base. this is brand brand new right like if i did this with opus yesterday wouldn't be possible um that's kind of the difference here is that um the way that um that codex is working is the way things have kind of always worked right so if you see this is like the individual person right it's not saying okay i'm going to launch all these different agents and compare what they say it's Say, okay, I'm going to inspect the workspace.

19:21 This is your, you know, really detail-oriented, really senior, like, founding engineer, like that example gave, right? Whereas over here, you can see it's already launched these agents, and now it wants to do web searches, and I'm going to let it do that. So multiple agents were asking to do web searches.

19:41 So now launching all four research agents in parallel. So this is off, and I've got, you know, So my technical architecture agent, I've got this other agent that these are both doing web searches right now. So one is looking at like prediction market order book matching engine architecture. So this one's learning about engine architecture for prediction markets.

20:02 This one's looking at polymarket, how it works, barnier prediction market mechanics. And then I've got the UX design is doing some design research. And then we've got some test research. Okay, now it's going to go to Polymarket, and let's really hope that Polymarket doesn't block it, because that'll make things harder for it.

20:20 Meanwhile, over here, this has discovered Codex, it's figured out the repo's empty, so it's going to scaffold it from scratch. And it is starting to, I'm now wiring the core market math and trading engine. so it's interesting right so you've got uh codex is out here building and it is like building the engine uh with opus 4 6 it still has agents out there like doing research work yeah you really start to see just like how different they really are yes as they make progress yeah like i said i haven't tested it before so we don't know how long it'll take each of these totally yeah and i think one question I have is is one model better for being more of a beginner non-technical coder or it doesn't really matter.

21:16 Yeah, it's a good question. I think the fair answer would be probably Codex because Codex edged out Opus 4.6 a little bit on some of those coding benchmarks and is kind of known for writing better production code, probably Codex in that way. At the same time, one of the downsides, and like I said, I could only do this in a totally balanced way because they're so different.

21:46 You know, at the same time for a vibe coder, knowing when to interject and stop Codex and say, oh, wait, you're doing this this way. Can you instead look at doing it this way? they're probably not going to know how to do that. And so that's where maybe Opus 4.6 is better where you could say, okay, spin up four or five agents and let them work with each other.

22:11 Yeah. Okay, Codex is done. So Codex built a competitor to Polymarket in three minutes and 47 seconds. And to be clear, Polymarket's a multi-billion dollar company. Yeah, I don't think this will work quite as well. Um, but, uh, but we'll see, let's see. So, um, let's just check out if it worked first.

22:36 I'll let this keep running here. Um, so, you know, it'll tell you at the end here, it actually did the testing. So you can see it built a test suite. So it has an LMSR math unit test suite, an engine behavior unit test suite, and an API integration, uh, test suite. And it passed with 10 out of 10 tests.

22:55 As far as what it built, it has this core LMSR market maker engine. So coherent pricing, slippage, bound loss behavior, domain trending engine. It built a REST API router, which is kind of interesting because I didn't tell it that it would have to build obviously any of this in any way. It figured out the architecture on its own.

23:16 Clean, responsive front end. All right, well, let's see. Let's see if it is actually. So let's go here. I'll let this keep running. This has got these four agents just running away here. And I'm in here. I'm going to do 1 p.m. test. All right, test 10 past 10. That looks good to me. Oh, yeah. 1 p.m. start.

23:44 All right, it's running. Let's see. Okay, here we go. So this looks like it has the ability. So Greg, we'll make you the first trader. All right. Say add. Okay. You got a thousand bucks. Okay. There we go. Not bad. All right. What market do you want to create? Well, Bitcoin, I think as we speak, has crashed to what, 63,000 or something?

24:17 Something like that, yeah. So I do like the, I mean, will BDC be above, you know, be above 110K by. Yeah. Okay. By DES 31, 2026. That's pretty good. Yeah. Okay. So let's. I mean, that's almost double. Yeah. That'd be pretty good. It depends. Depends when you bought it, you know, if you bought it at 125K, then you're not so happy.

24:47 Let's see. So then I don't know, I don't even know what resolution criteria and source would be. I mean, I think I know what it's getting at, but I guess you could say like, why don't we say use CoinMarket cap as the source and resolve by looking at the price on the last day of December, just before midnight, I guess.

25:17 I guess like the price of BTC yeah alright okay it looks like it's okay so we've got it now so we'll use CoinMarketCap okay so then you can do a yes 50% so what do you think yes yes or no I mean this isn't financial advice this is just purely purposes but I think I think so I think that. All right. That's a yes for Greg.

25:49 Buy. Let's see. How many shares you want to buy? You've got a thousand bucks. I want to put it all. I'll put it all on this. I don't know how much it is per share. Let's see if it's a thousand, if that's right. Okay. Yeah. Okay. Trade executed. Okay. So, I mean, it seems like it built something, you know, as a prototype relatively functional here.

26:15 I guess that it actually has decremented. So, okay, 1,000 shares was not, that ended up being, you know, about $24 that you spent. So you've got more money if you wanted to create another market. But it worked. It's not returning an error. It shows the volume here. Interesting. All right, so let's go back.

26:33 Let's see. So far so good with that, I'd say. Let's see what's going on here. So we've got, okay. So first off, look at how many tokens. People have been talking about how token hungry Opus is, and it's very token hungry. Each one of these agents has used over 25,000 tokens. So let's see, though. So they finished, right?

26:58 The technical research around architecture is done. Prediction market research is done. The UX design research is done. The testing strategy is done. Now it's going to go and build. so it's writing the package JSON did you see the ad that Anthropic launched about ads? yes I watched them all they're hilarious although actually I guess Sam was not very happy about them today I saw a tweet from Sam that was less than happy so I found them hilarious but I also understand his side as well so basically it seems like anthropic is sort of anti-ads for now and and yes the chat gpt is going to be introducing ads yes and you know when i'm when i'm watching this and i'm seeing you're going through 25 000 tokens 25 000 tokens 25 000 tokens yeah i'm like yeah of course anthropic

27:58 doesn't really yeah you know yeah yeah i mean this is literally i mean if you add that all up you're talking about over 100,000 tokens used in doing this. So I think that's one of the very good things for investors in Anthropic, right? Is with agents and agents now being, I think probably the new killer feature in Opus, you're going to take whatever token usage and multiply it by the number of agents.

28:28 Exactly. It's actually really smart. And I wonder if that was the thinking. like they're like how can we get people to use more tokens oh we'll just like spin up agents and we'll design it like that or did they think like okay how can we design a system that is best for the use case and then they're like okay then we'll monetize it like this I don't know probably a combination of the two I can tell you I've never used so many tokens in one day as today so it's working 100,000 tokens is like roughly how much in US dollars I don't know because I have a Claude Max plan so I'm not paying we're not seeing it hit any limits right now so I'm not paying more than $200 I can tell you that my guess is it's

29:20 we're talking in the $200 Max plan do you remember how many tokens you get approximately that's a good question let me fire up Claude and ask it let's see here how many tokens do I get estimate let's see okay so here you go estimate estimate so 45 million tokens per month of Sonnet but let's see what is your estimate for Opus or 6 let's see It's like they don't really want you to know.

30:02 No, they're trying to make it a little harder. They're not even going to tell me actually. They're just going to say there's no public data. It's very new. Opus is roughly 5x more expensive. So then if it's 45 million, that's 5x. So 10 million is probably the answer about it. So then if we're doing quick math, let's just say we spent 100,000 tokens.

30:28 you know 100,000 divided by 5 million is you know we're going to spend more than that because look at this we're now over 17,000 tokens on top of that in this next build so but still let's say you know even if we use a million tokens building a competitive Polymer here right now we're still only using a tenth of what anybody can do that's not terrible no I mean it's $20 which is like the price of a cocktail in Miami yeah yeah exactly yeah so let's see but now as I say I'm watching the tokens alright so it's building the API routes now I have a feeling this is going to be a better end result I was actually just going to say that this feels and maybe it's just because there were four agents that were doing all the work beforehand

31:26 and now it's doing the work. It feels like we're going to see something very different when we load what it builds. Yeah. I don't think we gave it any design, like visual design. Do you recommend for folks to just sort of get the MVP out, play around with it on local host, click some buttons, and then sort of update with the visual design from there?

31:55 It's a good question. I do like 50-50. Sometimes if I have something in mind, especially if I want something like on brand with something like suppose I'm building something that is going to be in the like open claw multibook ecosystem, I would probably say, hey, I want to design a site that looks somewhat similar to or is inspired by OpenClaw.ai and MoldBook.com.

32:27 Take a look at those sites and get inspiration. These models are great at doing stuff like that. I'm really excited to see what this is doing though. I think we're now well over 200,000 tokens. They show what I can tell. But we're not at 10 million. We're not hitting any limits. We don't have to take out a second mortgages on our...

32:49 Yeah, there you go. Yet. It's still going, though. I guess, you know, we can tell, like, here's an interesting thing in a comparison. Like, this is still going. Why don't we say, like, the design, because the design looked kind of bland to me, right? Yes, it did. Can you spruce it up and make it look nicer?

33:16 Because, like, we may as well have codecs working away, too, right? Yeah. so you didn't really give it any like specific it should look like square.com we'll basically see if if codex if you know if 5.3 has a little bit of taste yeah yeah so that's what it's saying now it's saying okay I'll upgrade the visual system without changing functionality stronger typography richer color direction better card hierarchy and purposeful motion I don't know what that means but we'll find out um all right okay so now it's now it's editing um index.html it looks like it's going to add motion hover polish okay totally that this current task for over 30 000 tokens building the front end ui okay it's done yeah codex is fast by the way right i mean that's pretty darn fast yeah um so

34:12 So we should be able to just go here. It should have already automatically reloaded. Okay. All right. I mean, it's not that different. It's not that different. It's, I think, can I try something? Yeah, go for it. I'm going to say, I would say, okay, thank you. But this was a minor design refresh. I'm looking for a major one.

34:42 There you go, yeah. And then I'm going to say, pretend you are Jack Dorsey. Here you go. And how would he design this website to be clean, elegant, and full of interesting interactions? Yeah, great. Yeah. Jack Dorsey, for people who don't know, co-founder of formerly known as Twitter, square block now he's just got he's got he's a design guy i don't know he's first one guy came to mind or first person came to mind yeah that's a good one that's a good prompt let's see so i'll do a full visual re-architect not an incremental tweak new layout language stronger typography monochrome first palette interesting interaction driven cards that's a duh okay you No, what's interesting is it didn't, I would have kind of hoped, and maybe, you know, we're not quite at AGI yet.

35:48 I would kind of hope that it would say, let me go find some art. Like, if you told me that, Greg, like, hey, Morgan, can you read it? I would be like, yeah, let me go look at some articles about Jack Dorsey's design aesthetic. Exactly. I'm surprised it's not doing that. Instead, it's going like, I am assuming it knows who Jack Dorsey is, although I don't know if it actually does.

36:09 It just seems like it's really just taking like this part of your question and going, oh, okay, major refresh. I'll do that. Well, can't you ask it? Can't you say, do you know who Jack Dorsey is? Let's see. I can actually – I'm supposed to be able to in the middle cut it off. So let me see. Yeah. Do you know who Jack Dorsey is?

36:32 Let's see. Okay. So here we go. This is the midstream test. Okay. I was thinking about it. 43,000 tokens over here. Okay. There we go. Yes. Okay, here we go. Yes. Jack Dorsey is the co-founder of Twitter, founder of Docking Square. Okay. With a design style that's typically minimal, restrained, and interaction focused.

36:56 Beautiful. Okay. All right. So, touche. It showed us. Yeah. Now, here's the weird thing. It looks like it's... Is it complete? Or do we have to say... Is it complete? Like, right when I was saying that? Are you done or did you stop because I asked a question? Yeah, this is really interesting. I will say, oh, I pause when you ask the question.

37:22 The major redesign, mostly. If you want to resume, so that's weird. So you ask a question, it just stops. So yes, of course, continue. So that's actually some weird UX. like it obviously should just continue after right yeah i would assume that it's such a weird thing as it said yeah if you want i'll resume now i will say i i do like that you can in midstream like kind of edit things yeah like that's how my brain works totally yeah yeah this is using a ton of tokens yeah it is amazing to see the detail i mean this this should be a a work of art, whatever site this comes off.

38:10 All right, this is done. So now let's see, we can go back to this. And, okay. I mean, I'm not blown away, but it's okay. Opinions become price in milliseconds. Trade conviction, not noise. Signal market is done for fast thesis iteration with transparent pricing. Okay. I would push it more, I think. Yeah, I guess.

38:41 Go for it. I would say that's not the Jack Dorsey I know. I don't know Jack Dorsey. I was looking for a Caps Lock major upgrade. that might mean way more copy way more images way more storytelling yeah exactly etc etc yeah I'll just say seriously take your time go nuts yeah what are credits famous last words Morgan I know right it's like oh perfect okay that's like a signal within the opening of headquarters like we finally got someone totally it's a whale alright so Opus has finished yeah I have no idea how many credits I used but probably actually let me ask it how many how many tokens in total did you use to put all of this together including the four agents and then we can hope it's using token stance

39:52 that's so funny okay doesn't know let's see okay here we go okay it's estimating it actually doesn't know which is weird because it should know although I wonder if I can actually do slash cost oh here we go yeah okay oh it doesn't okay no no need to monitor cost okay so they really don't want you to know okay it's guessing 150 to 250,000 tokens total yeah that's probably right okay sure yeah okay so here's what it's done so first off one really interesting thing here is um you know codex created 10 tests right opus created 96 tests so definitely a lot uh a lot more detail on the testing side and it's called it forecast uh whereas uh codex called it uh signal market so different names a polymark competitor is built and verified here's what each team member delivered

40:56 so the architecture technical lead decided modular monolith next to s14 app router central limit order book database schema wrestle api okay the prediction market domain expert binary yes no market where yes no is always a dollar okay seeded markets across crypto politics Okay, the UX design lead. Dark mode trading platform.

41:23 Pages. It is a green for yes, red for no. Okay. Testing QA lead did. Order book test. Okay, so here's what the tests are breaking down. Order book test. Matching engine. Okay. All right. NPN run dev to start the app. So let's go in here. Oh, interesting. Okay. I don't want to say anything, actually. I've already given it to him.

41:48 What's your initial take? I mean, my, hello, Jack Dorsey. You know what I'm saying? This is what I expected it to look like when we pushed Codex. Yeah, me too. This looks really clean. What happens when you hover over? Oh yeah, look at that. Yeah. It's got hover states. Hover states. It's actually got it organized.

42:15 Like when it goes sports, you know, Will the next tube will have over 120 million viewers? Will AI pass the Turing test by 2027? Will a movie deserve a three? It's got stuff in there, yeah. Yeah, this doesn't even, it doesn't feel like an MVP. Yeah, this is pretty wild actually. And it created some stuff, you know, that we never talked to it about, right?

42:37 Like a leaderboard, which it's already populated with some initial stuff, portfolio section. yeah interesting so let's see now so i mean i'm i'm more impressed with though it was maybe worth the 150 000 for 50 000 tokens feeling better about it will spacex land humans on marge before 2030 only eight percent it thinks huh oh yeah look at this actually whoa this is insane bro that's clean that's yeah i wasn't expecting to click in and actually get a well-designed page like this.

43:15 Huh. So if I were to do that, I have to sign in a trade. I don't know if I'm going to be able to sign in because I haven't set anything up. Let me just check. Well, you can sign up. It says don't have an account. Oh yeah, sign up. I don't know if it gets it all connected though. Let's see though. All right, I'm snagging.

43:30 You know what, actually, I'm going to take the username Greg. I'll steal your username. All right. Let's see. Okay. So yeah, it's probably because I was going to say the database isn't wired up yet. So I'm not surprised that I would actually have to do it. I wasn't expecting to do that. But I get it.

43:49 I mean, it's clean. This is pretty neat. Yep. Yeah. All right, let's see. So then, can this, all right, we've given, I don't know about you, but this is the last chance I'm going to give Codex on the design side. It's out of opportunities here. So, oh, here, it's funny though. In the end, it kind of, it's acting a little bit like data from Star Trek.

44:11 And the question, what are credits? In this context, credits usually means... Wasn't quite it. That's good, though. Okay, so let's see. Let's take a look and see. All right, here we go. The new version of Signal Market. Boom. Oh. Oh, okay. This is getting a little bit interesting. Let's see here. Read the manifesto.

44:36 Yeah, I mean, I don't hate it. it's definitely better yeah I mean it's it's got a lot going on yeah but it's different terminal it's different than yeah different than any sort of prediction market app I've seen from a UX perspective I just feel like this is just so clean though this is so good it's so fast yeah I mean I would say you know like I said I'm not going to say which one is it's not that Opus is better than Codex or vice versa but I would say in this test Opus won yeah in this test Opus won yeah that's just the truth yeah yeah but we could give it another I mean you know you never know like I think that what's interesting about this is I mean Codex built it like I don't know how much faster we can look at the timing on this

45:32 video but like 20 times faster or something right yeah yeah Yeah. Well, anything else you want to cover? I don't think we'll have time to do another example, but anything else you want to cover between, you know, that you want to leave people with? Yeah. Let me see if there is anything else in here. I covered the adaptive thinking.

45:55 Oh, I guess just on the orchestration, I would say, you know, this is a feature I'm probably the most excited about with Opus. And clearly we saw in this example, it working really well. Just make sure to look at the documentation. It's all in the docs now. And it gives some examples as well because it has this idea of like, compare with subagents of like context and communication and coordination and kind of breaks this down.

46:23 And then it has like a sample prompt, more of the details on the display mode. There's a lot of other stuff that I didn't go into there. That's probably what I would leave people with because I think a lot of people are going to want to dive in and use agents with Opus 4.6 and they've got pretty good details on all the little tweaks that you can make with it.

46:45 Amazing. Well, Morgan, I can't thank you enough for coming on. I hope people love this episode. I love talking to you. Thank you for having me, Greg. It's a total honor. I love how clearly you communicate to technical people, but also non-technical people. You're criminally under-followed, so I'm going to include links where you can find Morgan and follow him on X.

47:15 He talks a lot about vibe coding over there. and Morgan anything else you want to you know places that you want to leave people to go and check you out yeah I mean I'm the co-founder and CTO of Bold Metrics I'll just give a little plug for us we have AI technology that's used by apparel brands and retailers so if you're shopping online and want to find the right size you see a find my size button we a lot of times power that and have really powerful machine learning models that update and adapt over time to help people find the right size and give lots of really interesting data to lots of amazing brands and retailers that you probably all know and love.

47:55 And me and my team, we're using all of this tooling. Like I had a meeting with my team this morning about Opus 4.6 and Codex, and I've given everybody access to both of these. And I actually have multiple teams of mine that are trying current things we're working on and are actually testing with each to see which performs better.

48:19 So the one thing I encourage all engineering teams to do and engineering leaders to do is let your teams loose with this stuff. Let them try it. Some of this stuff is really cutting edge and really performing and gives us the opportunity to do better, more creative work. Yeah, stop listening to us right now.

48:37 Yeah, exactly. Stop listening to us. X out of this YouTube or Spotify link, but actually give us a like, a comment, and subscribe. Let us know if you like this episode. Morgan, thanks again for coming on the show. This was a lot of fun. See you next time. Greg, thank you so much. Total honor.