HomeVideos

GPT-5.5 vs Opus 4.8: The Real Winner Was /goal Mode

Now Playing

GPT-5.5 vs Opus 4.8: The Real Winner Was /goal Mode

Transcript

691 segments

0:00

Okay, today I'm excited about this one.

0:02

I haven't done one of these in a while.

0:04

This used to be all the rage about 6-8

0:07

months ago, but it has kind of fallen

0:09

off recently and I want to bring it

0:11

back. I think it's so much fun. It's

0:13

worth taking a look at. What I'm going

0:15

to do today is I have one kind of big

0:17

requirement. You'll see it in a second.

0:19

It's going to be a really cool fun

0:21

application to try to get agents to

0:23

build and I'm going to pit two agents

0:24

against one another. We're going to see

0:26

can GPT-55

0:28

or Opus 4-8 build this best. That's

0:32

really today's challenge. Which one

0:34

builds it best? And oh, by the way,

0:36

along the way I'll show you how I

0:37

designed the product and a couple other

0:39

things and hint at what I'm going to do

0:41

with this kind of series moving forward.

0:44

It's going to be kind of fun, I believe.

0:45

Okay, first before we go any farther,

0:47

I'm going to show you what we're going

0:49

to build. I'm going to show it to you

0:50

here for just a second so you can kind

0:52

of get the concept, but this is going to

0:54

be a native application on my Mac. So,

0:57

this is going to be a real normal

0:58

launcher application, not this web kind

1:01

of expression that you're seeing. What

1:02

it's going to be is an application that

1:04

you can line different

1:06

different kind of apps around a

1:08

a radial diagram here or kind of a

1:11

radial dial that you can select from.

1:13

You can use the arrow keys to select

1:16

different items or to go between the

1:18

different pages that you might have. And

1:21

then when you go into these things, you

1:23

should be able to edit them and put

1:24

different things in different locations,

1:26

different apps, that kind of stuff. So,

1:28

it's a launcher, but it's a lot more

1:29

than that because it also has a

1:31

mechanism to be able to open files with

1:33

certain applications. If you use this in

1:35

finder, you should be able to open those

1:37

files with a particular application. You

1:39

should be able to run websites. You

1:40

should be able to do just about anything

1:43

with this launcher. It's really a

1:45

complex request set with this kind of

1:48

expression, this diagram that you see

1:50

here as part of the request that I'm

1:52

going to be able to give to these very

1:53

advanced models right now to see how

1:55

they do to build it. That's really the

1:57

whole point. This is going to be pretty

1:59

hard to build especially in Swift, so I

2:01

want to see how it does. But moreover, I

2:03

want to compete models against one

2:05

another and now I want to get that

2:07

kicked off. Let's just get that started

2:09

now so that we can see that kind of

2:10

running and then I'll tell you how I got

2:12

this designed. Really easy and really

2:14

cool. Okay, this is going to be easy.

2:16

What I'm going to do is I'm going to use

2:17

the Codex desktop application which is

2:20

Codex CLI essentially. I'll get that one

2:23

kicked off. I'm also going to use the

2:25

Claude Code desktop application and get

2:27

that one kicked off. So, both of those

2:29

are off and building. It's of course

2:31

worth mentioning we're on Opus 48 extra

2:34

in Claude Code and we're on GPT 55 extra

2:37

high in Codex. But for fun, I am also

2:41

going to add some new ones here which

2:44

are goal items. So, I've built two new

2:47

work trees, same kind of thing for

2:49

Codex. I will do the same work here

2:51

using {slash} goal and then I will tell

2:54

it to

2:55

run a {slash} goal. You'll see it sends

2:57

in as a goal. I'll do the same thing

2:59

over here for Claude Code. All right, we

3:01

go. And the goal is, no pun intended,

3:04

those will actually both run using the

3:06

{slash} goal feature which is kind of a

3:08

more open-ended building process. So,

3:11

interesting to see with such a complete

3:13

version of definition around a product

3:15

that we want built is goal any better

3:18

than using just a direct representation

3:21

of a single agent that that master agent

3:22

then can spread out as much as it needs

3:24

to. I don't know. Let's find out. So,

3:26

one of the things I want to show you

3:28

just as kind of lagniappe here, a little

3:29

bit extra, is how I designed this

3:33

application because I've actually asked

3:35

for this system to be built before and

3:37

it kind of comes out pretty trash. And

3:39

so, I had to come up with a creative way

3:42

to allow a system to imagine a radial

3:45

diagram or radial system that would be

3:48

attractive and elegant and have some

3:50

animations to it which was not

3:52

necessarily an obvious thing for the

3:54

systems to come up with. Let me show you

3:56

the steps that I took. All right, so

3:58

first things first, I was using Claude

4:00

design. Claude design, great product if

4:03

you have Anthropic as a subscription,

4:05

you have access to Claude design. And so

4:07

my first request was kind of a big

4:09

request here, basically saying, "What we

4:11

want, we want radial rings, maybe three

4:13

different layers of rings with different

4:15

apps on them." So a lot of this was

4:16

because of the original request and how

4:19

spread out it was. It's okay that it's

4:21

this spread out, but I asked for six

4:23

variations on the theme, so we might be

4:25

able to choose from them. And this is

4:27

kind of what it gave me to begin with.

4:29

So you can see variations on the same

4:31

theme here, but very, very similar

4:34

between all of the different variations.

4:35

Then it came back, it created this, and

4:37

then I pushed back in a little bit and

4:39

said, "Well, keep this design." So this

4:42

document that we're looking at here, I

4:44

wanted to keep all of the ones that it

4:45

was already showing me and make sure

4:47

that it was going to essentially

4:49

version. And I said, "Do this again with

4:52

this extra information on the same

4:55

page." And so what it did is it put more

4:57

items down here. I wanted to kind of

4:58

create sections or something that might

5:01

create the modes that you see in the the

5:03

final design that we have. So okay, gave

5:05

me six more, all fine is what I would

5:08

say about these, not great. I wasn't

5:10

excited about them. I had mentioned I

5:12

wanted kind of a AAA gaming expression

5:15

so that it had an opportunity to be

5:16

highly graphical, and this feels a lot

5:19

more um mechanical than I would have

5:22

liked. So what did I do next? Okay, so

5:25

the next thing I did is I came out to

5:26

Chat GPT and thought, "Okay, let me use

5:28

the image model." The image model is

5:29

highly creative. Let me start there and

5:32

see if I can get ideation from here to

5:34

kind of go broad first. And so I gave it

5:37

pretty much the same original kind of uh

5:39

request that I said, but maybe a few

5:41

other things. And what it came up with

5:44

was relatively interesting. It certainly

5:46

wasn't uh extremely attractive, but it

5:49

these were very interesting graphically

5:51

compared to what we were just looking

5:53

at. And I thought, okay, I really like

5:54

the simplicity of one layer of icons and

5:57

one layer of kind of the modes that you

5:59

might be on and a button in the middle

6:01

you might be able to press to kind of

6:03

switch the modes. Really neat, very

6:04

simple, allows for a lot more icons in a

6:07

more creative pattern. So, quite

6:10

frankly, I took a screenshot just of

6:12

this bottom one. I grabbed my screenshot

6:14

utility and took a screenshot right here

6:16

of just this bottom one and passed it

6:18

on. Let's go back to Claude design.

6:20

Okay, here in Claude design, what I was

6:23

looking at for this one, I gave it the

6:25

the full screenshot here and later came

6:27

back and just gave it the smaller

6:29

screenshot and said, "Here's what I want

6:31

you to push in on. Think bigger and

6:33

better than you've been thinking

6:35

before." And I told it also to version

6:37

this file. So, I wanted to keep this

6:39

file and I wanted it to kind of create a

6:41

new version. And so, what it came up

6:43

with was more like this. You can it's

6:45

getting closer to what we were looking

6:46

at

6:47

from the ChatGPT display, better, but

6:50

still not quite there. So, then I took a

6:53

screenshot of this one and said, "Okay,

6:55

this is a very good start. I'm going to

6:57

start a brand new context." So, I

6:59

started a brand new conversation up here

7:01

and went to a brand new context, gave it

7:04

just that one image and said, "Okay,

7:06

from this one image, let's start pushing

7:09

in with a much simpler kind of

7:12

design message that you'll see here."

7:14

So, with that it started creating this

7:17

kind of version, which I thought was

7:18

fantastic. This is a great first step.

7:20

You can see it already has animation

7:22

around the outside ring. It was very

7:24

word heavy, these kinds of things. So,

7:27

this was a great start. I went back and

7:29

forth with it a few more times and got

7:31

to a place to where what we were looking

7:33

at earlier is the design that we have.

7:36

And I told it that I want arrow keys,

7:39

these kinds of things. So, there was

7:40

some iteration that I did here, working

7:43

as I was discovering and exploring more

7:45

things, working on the assets it was

7:47

giving me. I would push in and say,

7:49

"Well, let's duplicate instead of having

7:51

words in the middle, let's duplicate the

7:52

icon that maybe they're selected on at

7:54

any given moment. Let's put that into

7:57

the middle

7:58

down here so that it kind of feels like

8:00

as you move between nodes, you're

8:02

reinforcing the image. And let's use the

8:04

arrow keys to allow somebody to swim

8:06

around the outside and be able to hit

8:07

enter." All of that kind of stuff. So,

8:10

that's where they stopped. I then

8:11

packaged this up. There are ways to

8:13

share things from Claude Design. And in

8:17

here, you can use a send-off message.

8:20

You can just copy this prompt and give

8:21

it to your agent. I have found that to

8:23

be hit or miss, unfortunately. I'm sure

8:24

they're still working on this. I've had

8:26

the agent come back multiple times and

8:27

say, "Well, because of OAuth or

8:29

something else, I can't quite get to

8:30

that. Can you help me?" But, to solve

8:33

that, you can click this box to download

8:34

it, and then this will be the prompt

8:36

that you'll want to give your agent when

8:38

you give it the downloaded zip. You just

8:40

drop the zip on it, give it that, and it

8:42

has all the resources that it needs. So,

8:44

that really is kind of the the

8:46

methodology that I took taking this

8:50

this kind of ring mechanism and putting

8:53

it into Claude code or somewhere else to

8:55

be able to design from. So, that's where

8:57

we start. That's the resources that are

8:59

inside of this original build

9:00

environment. But, I want to show you one

9:02

other thing really briefly. This one

9:04

shocked me. Okay. So, I'm sharing a new

9:07

product here. Not It's new to me. It's

9:10

not new to many of you called Open

9:11

Design. A team has gone out and kind of

9:14

looked at what Claude Design was doing

9:16

and decided to put together almost

9:18

exactly the same product in an open way.

9:21

You can come in here and put in your own

9:23

subscriptions or your own

9:26

API keys, anything that you need. It

9:28

really is very, very open. And what I

9:31

ended up getting into was a version of

9:33

the same build. I will share this at a

9:35

later time cuz I want to do a comparison

9:38

of open design to to Claude design. I

9:41

just wanted to show this as quickly as I

9:42

could because if you're looking for

9:44

design tools and maybe you don't have a

9:46

Claude subscription or haven't found

9:47

great use out of it, definitely take a

9:49

look at open design. All right, let's

9:51

kick off. This is the apps that they're

9:53

building. They're popping up on our

9:54

screen trying to give us their version

9:56

of the build. And by the way, they

9:58

already look freaking great. [snorts]

9:59

Okay, taking a very quick peek.

10:01

>> [laughter]

10:02

>> Uh this is already fantastic. These

10:06

models are amazing these days. Oh,

10:08

excellent. Our first settings panel.

10:10

Interesting. See what we see here.

10:14

Ooh, all right.

10:16

>> [laughter]

10:18

>> Too many things happening at once, but

10:20

exciting. I kind of want to see that

10:22

settings panel again. Excellent. Kind of

10:25

awesome.

10:26

>> [laughter]

10:27

>> I'll just let them cook. I mean, windows

10:30

are popping up and closing all over the

10:31

place. A building four basically the

10:35

same application,

10:37

uh multiple builds all at the same time

10:40

is

10:42

maybe not the best idea.

10:44

But

10:45

it's awesome. Oh boy.

10:47

Uh so, it looks like it it won't be

10:49

surprising to many of you. It looks like

10:51

Claude is running quite a bit behind

10:54

GPT-55.

10:56

That tends to not be necessarily

10:58

surprising. GPT-55, both the goal and

11:00

the straight, are both complete, by the

11:02

way. And this is the straight version,

11:04

not on goal Opus build. Okay, we're

11:07

getting close. All except the goal

11:10

builder for Claude code is complete, but

11:12

the goal builder for Claude code, I

11:14

won't spoil it, is pretty impressive.

11:17

And it's also reporting the way that

11:19

it's been running its captures has been

11:22

off screen intentionally, apparently.

11:24

We'll see how that works out, but all of

11:27

the screen captures that it's been doing

11:28

and everything else, it's it's taking a

11:30

picture of what it renders and not the

11:32

rest of the system, which is really

11:33

quite nice. So, it's not accidentally

11:36

taking screenshots of my my desktop

11:38

while it's building. Oh, all right.

11:40

Well, we just got my very That's my very

11:43

first hint, and you saw it as well. It

11:45

looks kind of fantastic. I can't wait to

11:48

compare it to the non-gold version.

11:51

Uh yeah, very exciting. But, we're at 38

11:54

40 minutes at this point. That's worth

11:56

noting. Uh the the other ones I'll have

11:59

a whole table for you to see how this

12:00

worked out. For Codex, landed much much

12:03

faster, but it's not just about speed.

12:05

Okay, really briefly, while we're

12:08

waiting, let me talk to you about

12:10

{slash} goal. I'm not going to go deep

12:12

on this. I can do another video on it

12:13

sometime to really talk more about it.

12:15

What am I really doing when I say I have

12:18

a set of files, if you looked inside of

12:20

this repo, there's maybe 12 15 files and

12:23

that screenshot and some sample code

12:26

from the example that we were looking at

12:28

in design. That's all that's in here and

12:30

kind of describing what it should do.

12:32

So, it's kind of a complex set of files

12:35

that represent the request. Makes sense.

12:38

I have put that in to an agent like you

12:41

normally would. That agent will take a

12:43

look at that and then kind of put it

12:45

through a planning agent, figure out

12:47

what its plan is, work through that

12:48

plan, and work through it. So, that's

12:50

what's happening, and agents are very

12:52

very good at this these days. So, you

12:53

really don't need to do the planning

12:55

mode yourself. You don't really need to

12:57

break it down to a PRD, something like

12:58

that. But, there is another aspect of

13:01

work these days inside of some of these

13:04

agent systems, you know, these

13:05

harnesses, which is a goal. The concept

13:08

of saying I don't have an absolute set

13:11

of definitions of the things that I want

13:13

you to build. And by the way, this

13:14

system does not have an absolute set of

13:17

definitions. That's its intention is to

13:19

leave it a little bit vague and allow

13:20

the building system to kind of figure

13:23

out what else it might need to build,

13:24

but it does say you should be able to

13:26

open websites and applications, things

13:28

like that. A goal is there when you

13:30

don't have a series a known set of steps

13:34

to get to something and it allows the

13:36

agent system the harness harness system

13:38

to kind of figure out the path forward

13:41

to reach the end goal. The idea is you

13:43

would say I have a goal goal. Here's

13:46

what I'd like you to achieve. Here's the

13:48

stuff you can measure and here's the

13:50

level of measurement that you can use to

13:52

determine that you're done. So some

13:54

mechanism to kind of give it a read on

13:56

whether or not it's it's ready. I've

13:58

given it as you saw here, make sure that

14:00

it's professional release capable kind

14:03

of code. That's a very soft measurement

14:06

for it to hit, but it is going to use

14:09

that and try to keep running until it

14:10

feels like it meets that that target. So

14:13

that's really the reason I'm using goal

14:14

is to figure out on this somewhat

14:17

open-ended build, does it build better

14:20

when it's in goal mode or does it build

14:22

just the same as it would when you're

14:24

just doing a straight shot and let that

14:27

main agent determine the the path

14:29

forward to building it. So that's all

14:30

we're really interrogating. Okay, we're

14:32

finally done. Here we are, we're running

14:34

the first straight one from Claude Code

14:36

first. I'm going to give that a shot.

14:38

Let's just run it real quick and see. It

14:41

seems to have built. So let's try option

14:43

space one more time. Okay, I mean

14:46

>> [laughter]

14:47

>> maybe it doesn't perfectly fit the

14:48

brief. The idea is there, certainly. Up

14:51

and down moves around the different

14:53

areas. If I want to add an action, it

14:55

brings up an actions menu kind of with a

14:59

broken panel, interesting. Okay, so this

15:03

is straight. Remember, this is the

15:04

non-goal version on Claude Code. Let's

15:06

do straight on Codex and see if it did

15:09

any better cuz I'd say no. Okay, here we

15:11

go to run the Codex one straight. Built,

15:15

okay, not in the background, that's is

15:17

fine. What is our hot key here? There we

15:19

go. Hot key is control option space. All

15:23

right, if I click away from it, I put it

15:25

it works under my cursor. It obviously

15:28

is immediately better. It works there

15:31

perfectly well. It works around

15:33

perfectly well. My mouse cursor is

15:36

giving it focus to things. Oh, wow.

15:38

Yeah, this is really great. If I click

15:41

into one of these items, it brings up

15:44

the settings panel. Yeah, all kinds of

15:46

different excellent. These are the

15:48

different internal modes. Like the work

15:50

ring is this one, the web ring is that

15:52

one, and these are the different rings

15:55

or different modes themselves. So, very

15:57

cool. I think really entirely

16:00

meaningfully valuable right now. Like

16:02

this seems to work. I need to use it a

16:04

fair bit, and this is not a full test of

16:07

every single feature that's inside of

16:09

there, but really the first thing that

16:11

I'm trying to make sure is that it's

16:13

even close to really the intention that

16:16

we were asking for. Now, it's separated

16:18

each one of these objects. It's

16:19

separated the outside ring is not

16:21

animating. There's a lot of interesting

16:23

little details that it did miss that are

16:26

defined in the actual that that sample

16:29

that we handed off, but it got a lot

16:31

right. Like if this is where where we

16:33

started, I think I'd be very very happy

16:35

with it. So, that one that one gets a

16:37

pass. Good work. Okay, and so here we

16:40

are. We're going to stay in Codex once

16:41

again. I know this gets complicated.

16:43

We're staying in Codex and we're doing

16:45

the gold version of Codex. Let's see how

16:47

this one worked. Woo.

16:49

Yeah. Much better.

16:52

So, remember we were just looking at

16:53

Codex, and this again is Codex as the

16:56

circling right. Excellent. Golly. All

16:59

right, has all of that really right.

17:02

Let's get rid of it and move the mouse,

17:04

bring it back, and it does pay attention

17:07

to spaces on the screen. So, if it's off

17:10

screen, it stay it's forcibly staying on

17:12

screen. That's great.

17:15

Uh not that you'll be able to see this.

17:16

Let me try this on a different monitor.

17:18

Worked on a different monitor. Let's see

17:20

if that No, works great. Always going to

17:22

my cursor. Wow. [laughter] Okay, this

17:25

Yes, was the goal better? Yes.

17:28

Perceivably? Yes. Meaningfully? 100%

17:32

it's better. Let's take a look at the

17:34

settings that it has. Let's add one and

17:37

see what their setting mechanism looks

17:39

like.

17:40

Uh the different systems, what are on

17:42

each one of these different systems, how

17:44

you might kick them off. Oh, here's all

17:46

the parameters to be able to kick each

17:48

one of those off. So, yeah. I think this

17:50

is great. I I would have to play with

17:52

this. Obviously, it's pretty complex

17:53

piece of software, but yeah, I already

17:55

kind of want it. And it did load Google

17:58

when I selected that.

18:00

>> [laughter]

18:00

>> Of course. So, if I'm I'm in web and I

18:03

go to whatever's in brightness,

18:05

brightness is apparently weather.

18:07

Or I guess it's sunshine.

18:08

>> [laughter]

18:09

>> Okay. So, yes, I'm playing. I'm sorry.

18:12

Let's move on to the very last one,

18:13

which is Claude and kind of its goal

18:16

mechanism. I I have high hopes for this

18:19

one. All right, here we are in the

18:21

Claude goal version and it actually gave

18:24

me the way to run it as well as

18:27

information on how to kick it off once I

18:29

do. It's the only one that did that, so

18:32

give them real credit for that. All

18:34

right. All right, look for the ring icon

18:37

in the menu bar. Very cool. Okay, let's

18:40

Did you see that disclosure?

18:43

Oh, that's pretty sweet. The the animate

18:45

out. So, all of the icons are animating

18:48

out and it's subtle, but the icons blend

18:52

away from one another into the next icon

18:55

rather than being then rather than

18:57

snapping between them. See if I can get

18:59

one that's really pretty full. Nope,

19:01

it's got that loop back. So, this would

19:03

be moving something to a certain

19:06

kind of position in a circle. They move

19:08

it back to 0°

19:10

and it snaps back counteractively. So,

19:13

that's a very common CSS problem, common

19:16

everything. So, that's interesting to

19:18

see that they didn't see that. They

19:19

don't have the outside animating, but

19:21

they do have very tight lines.

19:23

Everything's closed in really correctly.

19:26

I mean, this feels very very close to

19:28

professional. Let's take a look at It

19:31

did dismiss the ring when we went into

19:33

the picker. This already looks much

19:34

better. Quite frankly, this feels like

19:37

it represents the app that I just saw in

19:39

some meaningful way.

19:41

are carried through here. You can choose

19:42

different colors for I really really

19:45

like what's going on here.

19:47

And was this appreciably different?

19:49

1,000%. If you remember, the last one

19:51

was janky all over the place. Really

19:53

didn't even work. So, is goal solving

19:56

some problems for me? Is it circling

19:58

back in? Yes. Now, I have a secret for

20:01

you. I want to share something with you.

20:02

Let's take a look at effective cost. How

20:05

many tokens did these burn? Okay.

20:07

I'll put this in a chart at the end, but

20:10

first, let me show you how it reports it

20:11

here. If we go to Codex first, Codex was

20:14

the fastest one. As you can see, the

20:17

straight version, so non-goal took 28

20:20

minutes to build, and in the end, it was

20:23

about 400,000, 500,000 tokens. Somewhere

20:26

in the half a million range. That was

20:28

the non-golden version, right? And it

20:31

only took roughly 28, 30 minutes. If we

20:33

go to the goal version here,

20:36

that's right. The goal version told me

20:37

straight up, goal finished faster, and

20:40

it was appreciably better, if you

20:41

recall. And with less token burn. That

20:45

is very interesting. Not sure about

20:46

that. That's surprising, but it was

20:48

faster. So, very interesting. So, 25

20:50

minutes, the best version over here

20:52

using goal. So, let's go take a look at

20:55

Claude code. When we look at the

20:57

straight version, this is just non-goal

20:59

straight on using it, it took, let's

21:02

see, 36 minutes. So,

21:05

8, 10 minutes longer, something like

21:07

that, to do the work, but that's

21:09

appreciable when we're talking half an

21:10

hour. Um and really it talked about uh

21:13

there are 36 million tokens, but it's

21:15

misleading cuz 35 million of them are

21:17

cash read, so it did the math out of

21:19

this, and it figured out that it really

21:21

was about 1.17 million tokens. So, this

21:24

is the straight one, 1.17

21:26

million tokens, which is kind of

21:28

incredible in 36 minutes. And that was

21:31

the one that was janky we couldn't even

21:32

use. So, very surprising. Last one, the

21:35

one we liked the most, let's take a look

21:37

at the goal one. Now, goal tells us that

21:40

it actually was about half a million

21:43

tokens in 48 minutes. Now, by far the

21:46

longest. This is another 12, 15 minutes,

21:48

or something along those lines. So, it

21:50

is getting long to do this work, but it

21:52

did burn not quite the least tokens, but

21:56

it burned the same amount as the gold

21:58

tokens or or or the straight version of

22:01

Codex. So, it kind of is in the middle,

22:03

but not nearly the 1. 17 that we saw

22:06

from the straight version, and it was by

22:08

far the best. So, if you're thinking

22:10

goals are bad because they're actually

22:11

going to go and eat all your tokens,

22:13

this is my example. I don't think that's

22:15

actually the case. So, it's worth

22:17

saying, sometimes when you have

22:19

open-ended kind of requests, things that

22:22

what you're asking for has enough

22:23

variability in it that you want teams

22:26

assigned to it, and you want the agents

22:28

to be able to figure out how to get

22:29

there, goals might be your way. You

22:31

might give them a shot. I really found

22:32

it to be much, much better here. And now

22:34

I have a cool application. Okay. So, I

22:36

hope you found that interesting. I

22:37

haven't done one of these bake-offs in a

22:39

while. This is really a lot of fun. I

22:41

always love building something with

22:43

multiple models. I'm sorry I gave you

22:44

four different builds. That's almost

22:46

impossible to keep in your head.

22:48

Obviously, goals in both cases were

22:51

were measurably, markedly better. Like,

22:54

it would be very, very easy to discern

22:56

for anybody to come in and go, "Well,

22:57

this one feels more like what was asked

22:59

for, at least, or this one works versus

23:02

really doesn't work.

23:04

So that's worth recognizing. There's a

23:06

lot of other features I didn't test to

23:08

figure out how integrated into the

23:09

operating system and those kinds of

23:10

things that I'll go off and test off

23:12

camera. I'll report back if if these

23:14

goals really didn't perform the way they

23:16

seem to have because maybe they made a

23:19

mess of everything else. I'll report

23:21

that back for sure. But at the same

23:22

time, really worth it to me. I would say

23:25

no question Claude wins. Claude wins

23:28

almost hands down. Um but Codex the

23:33

GPT-5 was really very excellent. If that

23:36

was the application I had to use, I'd be

23:38

fine. I could push back into the

23:39

settings panel a little bit and say

23:42

maybe work a little bit on this and do

23:44

maybe one or two other passes and get it

23:46

to where Claude got the the final build

23:49

using goal. So

23:51

you know, everything's very very close

23:53

these days. But here's all right. I

23:55

wanted to share with you the thing that

23:56

I'm going to do with this.

23:58

I run a benchmark and I share videos

24:00

about different models when they come

24:02

out. I actually have multiple models

24:04

that I've tested. The benchmark is open.

24:06

I'll put a link in the uh

24:08

in the description below. So you can go

24:10

look at the scores now. You don't have

24:11

to wait until my videos come out to

24:12

understand where MiniMax and

24:16

Grok and all of these other models

24:17

score. I haven't scored everything yet,

24:19

but I've scored a fair number of them.

24:21

I'll report those in other in other

24:24

videos. I am planning on doing a video

24:26

that has MiniMax and Kimmy and a couple

24:28

other models that people are very

24:30

interested in. I've had people ask me.

24:32

So I want to show those numbers, but my

24:34

goal is to actually allow a couple of

24:36

those models every now and then to try

24:38

to build this application so that we

24:39

also get a sense of how does it build? I

24:42

won't be able to do that with everything

24:44

cuz even these took half an hour to

24:46

build and an hour in the longest case

24:48

roughly. So I can't do it with

24:50

everything, but I can do it on a spot

24:52

check basis to where we can really

24:53

figure out it's not as good a model, but

24:57

how not a good as it is as it is.

25:01

How is it not You know what I'm saying?

25:04

All right. Thanks for coming along for

25:06

the ride on this one, and I'll see you

25:07

in the next one.

Interactive Summary

This video features a comparative 'bake-off' between AI coding agents (Codex and Claude) to build a complex, radial-menu desktop application for macOS. The creator tests both standard ('straight') prompting and 'goal'-oriented prompting to see which approach produces a superior application. The video details the design process using tools like Claude Design and ChatGPT, compares the results based on functionality and token consumption, and concludes with an assessment of which models and methodologies yielded the most professional outcome.

Suggested questions

4 ready-made prompts