HomeVideos

The creator of Claude Code just revealed 7 secrets to using Claude Code (Opus 4.7)

Now Playing

The creator of Claude Code just revealed 7 secrets to using Claude Code (Opus 4.7)

Transcript

373 segments

0:00

The creator of Claude Code just revealed

0:02

seven secrets to get the most out of

0:04

Claude Code and Opus 47. In this video,

0:07

we'll not only go over every single

0:09

secret he revealed, but also demonstrate

0:12

them live as we build an app together.

0:14

By the end of this video, if you follow

0:16

along, you'll not only be a master of

0:18

Claude Code and Opus 47, but you also

0:21

have an entire amazing app that you'll

0:24

build out side by side with me, even if

0:26

you've never coded before a day in your

0:28

life. Let's lock in and get into it. So,

0:30

Boris Cherny, one of the creators of

0:32

Claude Code, just put out two things.

0:34

This amazing thread on X that goes over

0:36

all these tips and tricks, as well as an

0:39

entire blog post with a bunch of tips

0:43

and tricks. What we're going to do is

0:44

not spend the next 20 minutes reading

0:46

the blog post and thread word by word

0:47

like every other AI channel out there.

0:49

We're instead going to be about that

0:51

action, boss. We're going to go and

0:52

implement every single one of these into

0:55

a live app we're going to build

0:56

together. So, let's do this. We're going

0:58

to do this all Claude Code CLI. I know

1:01

in the last video I said Claude Desktop

1:04

is the best way to use Claude Code at

1:06

the moment. The thing is, a lot of these

1:09

new features they just dropped on our

1:10

heads for some reason is only available

1:12

in the CLI. So, we're going to do this

1:14

in the CLI for now. The first trick

1:16

before we start building this app is

1:17

we're going to go into auto mode. So, if

1:19

you hit shift tab, then shift tab, then

1:22

shift tab, you will see auto mode. And

1:24

yes, we're going to make it the default

1:26

mode. Auto mode is really cool cuz it's

1:28

going to make Claude Code go so much

1:30

faster. My one complaint about Claude

1:33

Code, to be honest with you, is it just

1:35

asks for permission way too much. If

1:37

you're trying to build complex apps like

1:39

I am, every literal 5 seconds it's

1:42

asking, "Hey, can I do this? Hey, can I

1:43

do that? Hey, can I do this?" Even when

1:44

you're in accept edit mode, it's doing

1:46

that. The issue is is now everything

1:49

requires your attention every 5 seconds.

1:51

You can't multitask and do other things.

1:53

Well, they just released this fix. They

1:55

released auto mode, which is now what I

1:58

recommend as a default mode for everyone

2:00

using Claude Code. What it's going to do

2:02

is it's going to use the AI to determine

2:04

what permissions it should have. So,

2:05

instead of asking you, "Should you do

2:08

this? Should it do that? Should I have

2:09

permission for this?" it's just going to

2:11

ask itself and kind of make good

2:13

judgment. What this will allow it to do

2:15

is work continuously for hours on end

2:18

without having to interrupt you every 5

2:21

seconds, and that's incredible and makes

2:22

Claude Code so much better. So, what I'd

2:25

highly recommend doing is hitting shift

2:26

tab until you go on auto mode, and now

2:29

Anthropic will handle all the

2:30

permissioning itself, allowing you to

2:32

give a prompt and it just goes on its

2:33

own. That's the first of the seven

2:35

tricks Boris gave. Let's go into the

2:37

second one here, and let's start

2:38

building our app out together now that

2:40

we're in auto mode. The second trick he

2:43

gave is to front-load as much

2:45

information as humanly possible into

2:48

Claude Code before you start a session.

2:50

So, what makes Opus 47 so special is

2:53

it's a lot better at listening to your

2:56

directions. And so, what you can do is

2:58

when you first go into Opus, now that it

3:01

can run for a long time on its own, you

3:03

want to front-load as many instructions

3:06

as humanly possible because it will be

3:08

really good at parsing and following all

3:10

those instructions without having to

3:12

interrupt you at all. So, let's build

3:13

this app out together. I'll put this

3:15

prompt down below. What we're going to

3:16

do is build a really helpful app. If

3:18

you're at all familiar with Linear, it's

3:20

the number one project management tool

3:22

right now. It's like completely free and

3:24

awesome, but I personally like building

3:27

my own version of every app I use. So,

3:29

we're going to build our own version of

3:31

Linear, and if you do this with me,

3:32

you'll have an awesome app that you can

3:34

use for the rest of your life. It's

3:35

really good at helping you manage your

3:37

tasks and projects. So, before when I

3:39

was building out projects in Claude Code

3:41

or Codex, I would kind of build it out

3:43

one step at a time. Just give the first

3:45

step and the second step and the third

3:46

step and the fourth step. What we're

3:47

going to do instead is we're just going

3:49

to give it all at once. I want to build

3:50

a Linear clone out. This should be a

3:52

project management tool where I can

3:54

build projects, then put tasks and

3:55

issues in those projects. Every project

3:58

task and issue should have status and

4:00

priority. It should be a really clean,

4:02

simplistic, linear-like interface. I

4:03

should be able to assign users each task

4:06

and add any other features you think

4:07

will be helpful. Use Next.js to build

4:11

this out. Next.js is just a web

4:12

framework a lot of popular web apps are

4:14

built on. We'll make this really easy to

4:16

build and I'm going to hit enter on

4:18

that. What you're going to see now is

4:20

Claude Code will be able to obey every

4:23

single instruction I gave that I

4:25

front-loaded there and I'm not going to

4:27

have to give permission at all. It's

4:28

just going to do it all at once because

4:30

we're in auto mode. And in a second, I'm

4:32

going to give you two more tricks that

4:33

are going to be really amazing and make

4:35

this experience so much better, but

4:36

let's get the V1 of this app done. And

4:38

if you took the prompt down below and

4:40

used it, you're going to have a really

4:41

amazing app with me here. And just as

4:43

this is building, I get this question

4:44

all the time. Hey, when should I be

4:46

using Claude Code? When should I be

4:47

using Open Claude to build things? Just

4:49

as a reminder, as this is building out,

4:52

I like to use Open Claude to build

4:54

prototypes of apps when I'm on the go

4:56

since I can just hit it up in Telegram.

4:58

I also like to use Open Claude for

5:00

building out tooling for Open Claude, so

5:02

building out tools for my agent to use.

5:04

But when I'm building out deep, complex

5:07

apps, if I'm building out

5:08

consumer-facing apps, if I'm going into

5:10

a deep coding session like we're doing

5:11

right here, I'm using Claude Code. It's

5:13

just going to be a lot better at coding

5:15

by itself. All right, looks like it's

5:17

done and it's already running. Let's

5:18

take a look to see what we got here. And

5:20

boom, look at that. That's good-looking.

5:22

Anyone who's ever used Linear before

5:24

will definitely recognize this. So what

5:26

you can see here is a list of the tasks

5:29

that are assigned to each project. So we

5:31

can go in, we can create new tasks.

5:33

Let's say finish this YouTube video, put

5:37

it in to do, assign it to me, create and

5:39

boom. This is beautiful. I mean, this

5:41

looks pretty much exactly like Linear.

5:45

This is really, really nice. You even

5:46

have tags in it. This is great. If you

5:48

took the prompt from down below, you now

5:50

have an awesome project management tool

5:52

you can be doing for all your vibe

5:54

coding. This is sick. Which brings us to

5:56

the third tip that they revealed in the

5:59

thread and blog post that they just

6:00

released, which is recap. If you do

6:03

{slash} recap, this will generate a

6:06

one-line sentence recap of everything

6:09

your agent has done to this point. This

6:11

is really helpful because if you

6:13

followed my previous tips around

6:15

front-loading information and having

6:17

your agent run for hours on end, it'll

6:20

do a whole bunch of things that you're

6:21

not even aware about. If you do {slash}

6:23

recap after a long-running session or

6:26

after maybe you gone to bed and you woke

6:28

up the next morning and want to get back

6:29

to work, it will give you a rundown of

6:32

everything you've done up to that point.

6:34

This is unbelievably helpful if you

6:36

treat Claude Code like an employee,

6:38

which you should be doing and letting it

6:39

just do its thing for long periods of

6:41

time. Which brings us to our next tip,

6:44

which is effort level. They made it a

6:46

lot more configurable how much effort

6:49

your model puts in when you give it

6:51

tasks to do. So, if you do {slash}

6:53

effort, you hit enter there, you can

6:55

select your effort level. So, they have

6:58

added a couple of things here. First,

7:00

they added extra high and max mode. And

7:02

what I found based on my tests is you

7:04

basically want extra high for pretty

7:07

much everything unless you give a super

7:10

complex task. So, what I would recommend

7:12

is if you do what I said earlier, which

7:14

is give you know, front-loaded

7:16

information on every single thing you

7:17

want in app, I would go into max mode

7:20

for that. And then afterwards, as you're

7:22

configuring, adding new features,

7:23

changing things around, switch it to

7:25

extra high mode. The only reason I would

7:28

ever use high, medium, low is if one,

7:31

you're not on the $200 a month plan,

7:33

which I highly recommend. If you're on

7:35

the lower plans, then I probably would

7:36

want to get more granular and switch to

7:38

low for things like changing button

7:40

colors and things like that. But other

7:42

than that, if you're on the $200 a month

7:43

plan, I've gotten away with using extra

7:45

high for pretty much everything other

7:47

than that front-loaded max big prompt I

7:51

give to kick off apps. So, if I'm you,

7:54

use extra high for pretty much

7:55

everything unless you're on one of the

7:57

lower plans, then you can switch that.

7:58

But /effort

8:00

will help you configure how much effort

8:02

it's putting in on every single task.

8:04

The next tip they gave, and they gave

8:06

this in this blog post, I'll put the

8:07

link for the blog post in the thread

8:09

down below. this where our tip number

8:11

five here is notifications.

8:13

You should be turning on notifications

8:15

for Claude Code, so that after it's done

8:18

running these long-running tasks, it'll

8:20

ping you, put a notification here that

8:22

says, "Hey, I'm done. Check this out."

8:23

The theme of a lot of these tips I'm

8:25

giving is you're now increasing your

8:28

trust of Claude Code to have it run by

8:30

itself. Instead of hand-holding it

8:32

through a whole bunch of tasks, you're

8:34

giving it trust and you're letting it

8:36

run on its own. So, what you can do to

8:39

set up notifications is actually really

8:40

simple. Say, "Hey, set up

8:41

notifications." So, you can say, "After

8:44

every piece of work you do, please send

8:48

me a notification." And just by doing

8:51

that, it's going to set up its own

8:53

automation to ping you every single time

8:56

it's done something. So, I'm going to

8:57

hit enter on that, and it's going to set

8:59

up that notification. So, after

9:01

long-running tasks, it pings me, and I

9:03

can come back and quickly get into focus

9:06

with Claude Code. So, as you can see,

9:07

it's actually loading up a skill that

9:10

can actually send you those

9:11

notifications. So, it's setting up a

9:13

skill, it's setting up a hook, and every

9:15

time a prompt is done, it's going to use

9:17

that hook to say, "Hey, Claude Code

9:20

here, all finished. Check out what we've

9:21

done." This will speed up your workflow

9:23

so much cuz you can give a long-running

9:25

task, let it work for a while, come

9:27

back, and now it will ping you every

9:29

time it's done, so you can always stay

9:31

in flow. By the way, just as a little

9:33

side tip here, what I'm doing, when I

9:36

give these long-running tasks, I'm

9:38

always switching to the chat in the

9:40

desktop app. I actually find for the

9:42

first time I love just straight-up

9:44

chatting with Opus. Previously, I

9:47

preferred Chat GPT for chatting and

9:49

bouncing business ideas, but Opus 4.7

9:52

has actually been really, really good

9:54

for me when it comes to coming up with

9:56

new ideas for my business. So, when I

9:58

give a long-running task to Claude Code

10:00

and I'm waiting for that notification to

10:02

come in, I'm going to chat mode in the

10:04

desktop app and I'm talking about

10:06

whatever it is I'm building and coming

10:08

up with brand new ideas for that app and

10:11

for that business. Highly recommend that

10:12

workflow, by the way. Before I give this

10:14

last tip, by the way, leave a like down

10:15

below if you learned anything at all.

10:17

Make sure to subscribe and turn on

10:19

notifications. Also, I do a live boot

10:21

camp every single Friday in the Vibe

10:24

Coding Academy. I also do live Vibe

10:27

Coding sessions every Thursday. So, if

10:29

you join now, you can hop in, watch me

10:31

vibe code live with Claude Code. I

10:33

narrate everything I do, show you every

10:35

single tip and trick I'm using as I'm

10:37

vibe coding. So, if you want to watch me

10:39

vibe code live and ask me questions as I

10:41

do it, join the Vibe Coding Academy.

10:43

Link down below for that, biggest

10:44

community in AI. The last tip I'll give

10:46

here is working with adaptive thinking.

10:48

So, they actually removed extended

10:51

thinking with Opus 4.7. Before in Opus

10:54

4.6, you can turn on extended thinking

10:57

and it will use a lot more tokens to

10:59

think every step of the way. Now,

11:01

instead what they're having you do is

11:03

you're actually going to use prompts to

11:06

initiate extended thinking. So, for

11:08

instance, say I want to make it so I can

11:10

invite other people to use my project

11:12

management tool, right? I want to invite

11:14

other people in and they can add task

11:16

and manage task with me. This is great

11:17

if you have a team. I would say, I want

11:20

to make a collaborative mode here where

11:24

I can invite other people to use this

11:28

project management tool with me. Think

11:31

carefully, step by step, about this. So,

11:36

you have two different knobs you can

11:37

control here. How much effort it's

11:40

putting in, and how much thinking it's

11:42

going to do. Effort is basically going

11:44

to be, in total, how long they'll spend

11:46

on a task you give it, and thinking will

11:49

be how long it spends on each individual

11:51

micro step of that task. I like to use

11:54

the extended thinking for when I give a

11:57

smaller task that might be more complex.

12:01

Like this, this is a collaborative mode.

12:02

So, this isn't some gargantuan task that

12:06

with a hundreds of different features in

12:07

it. Instead, it's one task, but it's

12:10

really challenging. So, I want to think

12:12

extra hard about this one simple task.

12:14

So, I'll just say, "Think carefully,

12:15

step by step." If this was a smaller

12:18

task, like, "Hey, just update the color

12:19

of a button." I'd go in and I'd say

12:21

something like, "Prioritize responding

12:23

quickly, rather than thinking deeply."

12:25

So, now you can control the thinking

12:27

budget of each one of these tasks. This

12:30

is the new way to do adaptive thinking.

12:32

So, just putting on some extra prompt

12:35

that says, "Think hard about this." or

12:37

"Don't think too much about this at

12:38

all." This will control the amount of

12:41

tokens that are spent on each individual

12:42

task, rather than overall. Those were

12:45

the seven tips of getting the most out

12:47

of Claude Code that was just revealed by

12:50

Boris, the head of Claude Code. I hope

12:52

this was helpful. If this was, leave a

12:54

like down below. Subscribe, turn on

12:55

notifications. I also live stream

12:57

Monday, Wednesday, Friday, 11:00 a.m.

12:58

Pacific. So, I'll see you there. I will

13:01

see you in the next video.

Interactive Summary

The video outlines seven key tips from the creators of Claude Code for optimizing the use of the tool alongside the Opus 47 model. By transitioning from manual permissions to an 'auto mode' and using advanced prompting strategies, developers can build complex applications more efficiently. The guide covers practical techniques like front-loading instructions, managing effort and thinking budgets, and automating notifications to maintain a productive, long-running workflow.

Suggested questions

4 ready-made prompts