Today's a massive day because Anthropic just dropped Opus 46 and OpenAI answered with GPT 53 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.
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.
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 today, because you'll have these tips and tricks in your back pocket.
I'm with one of my favorite people, Morgan Linton.
You might not know him, but he is just an incredible developer, founder, entrepreneur, investor.
He does it all, but today what I needed him to help me understand is Opus 46 just came out.
GPT 53 Codex just came out.
Morgan, help me understand by the end of this episode, what are people going to get out of this?
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 like maybe 18 minutes later announcing GPT-5.3 Codex.
And me, 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.
By the end of this you're going to know first how to make sure that you are running Opus 46 and all of the little details you can change in the settingsjson file to use some of the cool features in Opus 46, especially agent teams, which is probably the feature I'm the most excited about.
You'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 and see which model performs best.
They're going to do a head-to-head to try to each build their own version of Polymarket.
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.
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 46 or trying to use Opus 46 today tomorrow, whenever it is that you're jumping in to use it.
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 want to be able to use quad code with Opus 46.
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, like as of right now, it's 2.1.32.
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 like cd tilde slash clod, So I bet that there's people who are running the old model.
They don't even realize it.
They're probably getting bad results.
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.
The key thing that you want to do is in my opinion, the coolest feature that they added with 46 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 46 is that they are running Opus 46.
They keep hearing about Agent Teams 4.6.
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 and end this cloud code experimental agent teams and then set it equal to one.
Okay.
Nothing too crazy.
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.
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.
And so here's kind of the different levels.
So with Max, Claude 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 46.
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.
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 settingsjson 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.
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 46.
Cool.
So that's that.
Before I get into kind of the differences between Opus 46 and Codex.
I thought I would actually read this, because this was posted on Hacker News four hours ago.
And I was reading and I was thinking that's like the best way to explain it.
So I'm just going to 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-3 and Opus 4-6 are diverging philosophically and really in the same way that actual engineers and orgs have diverged philosophically.
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 46 the emphasis is the opposite a more autonomous agentic, thoughtful system that plans deeply, runs longer and asks less of the human.
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 result.
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 46 is better.
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 46, 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, 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 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, just going to 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.
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.
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 for progressive execution rather than total recall.
So that's why that's not as important.
And optimized for deciding what to keep in working memory.
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.
Opus 46 is really good at code-based comprehension refactors with architectural sensitivity, explaining why a system behaves a certain way, and then a little less tendency of this YOLO write code.
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.
So kind of a win for everyone there.
5.3 Codecs 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, you're probably like your founding engineer, right?
Yeah.
Uh, agentic behavior, uh, Opus 4.6, this is the key one, right?
It's like the multi-agent orchestration.
Um, that's, that's probably like the bleeding edge feature in 4.6.
Um, and then with uh, with with uh 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, oh 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 But it has a pretty big context window, so it knows what it did.
But, you know, Claude's really asking, like, should we do this?
GPT-53 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 what I mean?
Like, they have different styles.
Yes, totally.
Yeah, it's a good way to look at it.
It's like a different personality type, right?
Yeah.
And then, yeah, failure modes, you know, Claude 4.6, it might overanalyze.
It's got a much bigger context window.
It can hesitate when requirements are ambiguous.
And then it can stop short of full execution.
53.
Codex could be overconfident, can lock in a flawed assumption early, but you can steer it back in the right direction if that happens.
Yeah.
So that's kind of a high level overview on the two.
Cool.
That's helpful.
Yeah.
So should we just dive in?
I haven't tested any of this.
So this is not.
I have like zero canned demos because I thought it'd be more fun just to try something together and see what happens.
So should we try it?
Yeah.
Okay.
So let's see.
I'm going to start with Opus.
And I've got these prompts preloaded.
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.
So the prompt that I'm going to 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.
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 to make sure everything works.
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?
That'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.
I'm going to make different directory streets.
I'll do, let's just call this Opus45 Folly Market Competitor.
All right, so let's fire up Claude 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 with the model, if you type slash model, I can see here right.
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.
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.
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.
Neither myself or Morgan are affiliated with either.
Well, actually, I don't know about you.
I'm not affiliated with Anthropic or OpenAI.
No, I'm not.
Nope.
I love them both equally.
How about that?
Yeah.
Okay.
And I'm going to try to start them 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?
Yeah.
That's a great question.
Well, I know right now, because I told Opus 45 to build using different teammates.
It's going to do that.
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.
That's kind of.
The difference here is that the way 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 and say okay, I'm going to inspect the workspace today.
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.
So now launching all four research agents in parallel.
So this is off and I've got, you know, 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.
This one's looking at polymarket, how it works barnard, particular market mechanics, and then i've got the ux design um 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 the polymarket doesn't block it, because that'll make things harder for it.
Meanwhile, over here uh, this has discovered coex has figured out the repo is empty, so it's going to scaffold it from scratch um, 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 Codex is out here building and is like building the engine with Opus 4.6.
It still has agents out there like doing research work.
You really start to see just like how different they really are 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 like, I guess one question I have is like, is one...
Is one model better for being more of a beginner, non-technical live coder or, you know, does it really matter?
Yeah, it's a good question.
I mean, I think the fair answer would be probably Codex, because Codex edged out Opus 46 a little bit on some of those coding benchmarks and is kind of known for writing better production code.
Probably codex in that way.
Um, at the same time, one of the downsides and, like i said, this is i could only do this in a totally balanced way because they're so different um, 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 and can you instead look at doing it this way?
They're probably not going to know how to do that, right?
And so that's where maybe Opus 46 is better, where you could say okay, spin up four or five agents and let them work with each other, right?
Yeah.
Okay, Codex is done, all right?
So Codex built a competitor to Polymarket in three minutes and 47 seconds, right?
And to be clear, Polymarket's a multi-billion dollar company.
Yeah, I don't think this will work quite as well. but we'll see.
Let's see.
So let's just check out if it worked first.
I'll let this keep running here.
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 test suite.
And it passed with 10 out of 10 tests.
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.
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.
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?
Okay. say add.
Okay.
You got a thousand bucks.
Okay.
There we go.
Not bad.
All right.
What, what market do you want to create?
Well, Bitcoin, I think as we speak is crashed to what?
63,000 or something.
Something like that.
Yeah.
So I do like the, I mean, we'll BDC be about, you know, be above 110 K by.
Yeah.
Okay.
Yeah.
By DES 31, 2026.
That's pretty good, yeah, okay.
That's pretty good.
So let's see.
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 about it.
Let's see.
So then I don't even know what resolution criterion source would be be.
I mean, i think i know what it's getting at, but i guess you could say like uh uh, why don't we say use coin market, uh cap as the source and resolve by looking at the price?
Uh, on the last day of december?
Uh, just before midnight, i guess?
Yeah, i guess like The price of BTC.
Yeah.
All right.
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 educational purposes.
Okay.
But I think so.
I think that.
All right.
That's a yes for Greg.
Buy.
Let's see.
How many shares do 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.
I guess that it actually has decremented.
So, okay.
A thousand 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.
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?
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 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.
Yeah.
It seems like Anthropic is sort of anti-ads for now and ChatGPT is going to be introducing ads.
And when I'm watching this and I'm seeing you're going through 25000 tokens, 25000 tokens, 25000 tokens, I'm like yeah, of course, Anthropic doesn't really work.
Yeah, exactly.
Yeah.
I mean, this is literally.
I mean, if you add that all up, you're talking about over 100000 tokens used in doing this.
So I think that's one of the very good things for like investors in Anthropic, right?
Is with agents and agents now being, I think probably the new killer feature in Opus.
Yeah.
You're going to take whatever token usage and multiply it by the number of agents.
Exactly.
Yeah.
It's actually really smart.
And I wonder if that was the thinking.
They're like, how can we get people to use more tokens?
Oh, we'll just spin up agents and we'll design it like that.
Or did they think, 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.
Yeah, 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.
Yeah, 200 bucks.
Yeah, so I'm not paying, we're not seeing it hit any limits right now, right?
So I'm not paying more than $200, I can tell you that.
Yeah.
My guess is it's, you know, 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.
So 45 million tokens per month of Sonnet.
But let's see.
What is your estimate for Opus or six?
It's like they don't really want you to know.
No, they're trying to make a little harder, okay.
Well yeah, 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 uh, if it's 45 million, that's 5x, so 10 million is probably the answer.
About right yeah yeah um, So then, if we're doing quick math, let's just say we spent 100000 tokens.
100,000 divided by 5 million is... 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.
Okay.
Yeah.
But still, let's say you know, even if we use a million tokens building a competitor to Polymarker right now, we're still only using a tenth of what he 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, yeah.
So let's see.
But now, as I say, I'm watching the tokens creep out.
All right, 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.
And maybe it's just because there were four agents that were doing all the work beforehand and now it's doing the work.
It feels like we're going to see something very different when we load what it built.
Yeah.
I don't think we gave it any visual design.
Do you recommend for folks to just get the MVP out, play around with it on local host, click some buttons and then update with the visual design from there?
That'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 multi-book ecosystem, I would probably say hey, I want to design a site that you know looks good, somewhat similar to or is inspired by.
You know uh open, open clawai and multbookcom right, take a look at those sites and get inspiration.
These models are great at doing stuff like that cool.
I'm really excited to see what this is doing, though.
I think we're now like well over 200 000 tokens.
They show how i could tell uh, but we're not at 10 million.
Yeah, We're not hitting any limits.
You know, we don't have to take out second mortgages on our... Yeah, there you go.
Yet.
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.
Yeah.
Can you spruce it up and make it look nicer?
Because we may as well have codecs working away too, right?
Yeah, so you didn't really give it any specific, it should look like square.com.
No, no.
We'll basically see if codecs, 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.
All right.
Okay, so now it's editing.
Index.html.
It looks like it's going to add motion hover polish.
Okay.
Yeah.
This current task for over 30,000 tokens, building the front-end UI.
Okay, it's done.
Yeah, Codex is fast, by the way.
I mean, that's pretty darn fast.
So we should be able to just go here.
It should have already automatically reloaded, but okay.
All right, I mean, it's not that different.
It's not that different.
I think...
Can I try something?
Yeah, go for it.
I would say, okay, thank you, but this was a minor design refresh.
I'm looking for a major one.
There you go, yeah.
And then I'm going to say, pretend you are Jack Dorsey.
There you go.
And How would he design this website to be clean, elegant, and full of interesting interactions?
Jack Dorsey for people who don't know, co-founder of formerly known as Twitter and Square Block now.
He's a design guy.
I don't know, he's the first guy that came to mind or first person that 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.
Okay.
You know what's interesting is it didn't.
I would have kind of hoped and maybe we're not quite at AGI yet.
I would have kind of hoped 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.
So 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.
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?
Let's see.
Okay.
So here we go.
This is the midstream test.
It's thinking about it.
43 000 tokens over here.
Okay yes okay, here we go.
Yes, jack dorsey is the co-founder of twitter, form of the docking square.
Okay, with a design style that's typically minimal, restraint and interaction focused beautiful okay, all right, so touche it showed us.
Yeah, now here's the weird thing it looks like it's.
Is it complete?
Did it complete 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 paused when you asked the question.
The major redesign.
Oh interesting, mostly if you want to resume.
Oh so that's weird.
So you're asking a question, it just stops.
But like uh, so like yes, of course continue.
Yeah okay, so that's 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 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 should be a work of art, whatever cycle this comes off.
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 dying for fast thesis iteration with transparent pricing.
Okay.
I mean, I would push it more, I think.
Yeah.
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.
Yeah.
Way more storytelling.
Yeah, exactly.
Et cetera, et cetera.
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 headquarters.
Like we finally got someone.
Totally.
It's a whale.
All right.
So Opus has finished.
I have no idea how many credits I would use, but probably, actually, let me ask it.
How many tokens in total did you use to put all of this together, including the four agents?
And then we can, oh, it's using token stance.
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, you know, Codex created 10 tests, right?
Opus created 96 tests, right?
So definitely a lot more detail on the testing side.
And it's called a forecast, whereas Codex called it signal market.
So different names.
A Polymark competitor is built and verified.
Here's what each team member delivered.
So the architecture technical lead decided modular monolith Nextjs 14 app router central limit order book database schema, restful 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.
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.
What's your initial take?
I mean, my... Hello, Jack Dorsey?
You know what I'm saying?
Yeah.
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.
It's got hover states.
Yeah.
It's actually got it organized.
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 preserve 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?
Like a leaderboard.
Yeah. which it's already populated with some initial stuff.
Portfolio section.
Yeah.
Interesting.
So let's see now.
So, I mean, I'm more impressed with those.
It was maybe worth the $150,000, $150,000 tokens.
Feeling better about it.
Will SpaceX land humans on Mars before 2030?
Only 8% it thinks, huh?
Yeah.
Oh yeah, look at this actually.
Whoa.
This is insane, bro.
That's clean.
That's clean.
I wasn't expecting to click in and actually get a well-designed page like this.
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, just 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.
You know what?
Actually, I'm going to take the username Greg.
Wow.
I'm going to 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.
I mean, it's clean.
This is pretty neat.
Yep.
Yeah.
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.
When you 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.
Yeah, I mean, I don't hate it.
It's definitely better.
Yeah.
I mean, it's...
It's got a lot going on, but it's different than any prediction market app I've seen from a UX perspective.
I just feel like this is just so clean, though.
This is so good and 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.
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 video, but like 20 times faster or something right.
Yeah, yeah.
Well, anything else you wanted to cover?
I don't think we'll have time to do another example, but anything else you wanted 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.
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 sub-agents, of like context and communication and coordination, and kind of breaks this down um, and then it has like a sample prompt uh, 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 um, use agents with opus 46 and they've got pretty good details on all the little uh tweaks that you can make with it 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 underfollowed, so I'm going to include...
Links where you can find Morgan and follow him on X. He talks a lot about vibe coding over there.
And Morgan, anything else, 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 customers.
Lots of amazing brands and retailers that you probably all know and love.
And, and, and me and my team, you know, we're using all of this tooling.
Like I had a meeting with my team this morning about, uh, Opus four, six and, 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.
So yeah, You know, the one thing I encourage all engineering teams to do is like and engineering leaders to do is like let your teams loose with this stuff.
Let them try it.
You know, 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.
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.
Craig, thank you so much.
Total honor.
