HomeVideos

DeepSeek Harness Setup: A Free Claude Code You Own In 10 Minutes

Now Playing

DeepSeek Harness Setup: A Free Claude Code You Own In 10 Minutes

Transcript

315 segments

0:00

Deep Seek just dropped Deep Seek harness

0:02

and it already has 190,000

0:06

stars. People are calling it the free

0:09

Claude code. So, in this video, I'm

0:12

going to install it, show you how to set

0:14

it up, and then show you exactly how to

0:17

run it. By the end of this video, you

0:19

will have a coding agent that is yours,

0:21

that no company can take away from you,

0:24

and that you can point at literally any

0:27

model you want. Let's get started. The

0:29

model is the brain. Everything you wrap

0:32

around that brain is the harness. Your

0:35

contacts, your tools, your plugins, your

0:38

MCP servers, your permissions, and your

0:41

memories. Claude code is not the

0:43

harness. Claude code is a harness where

0:46

somebody else made every decision inside

0:49

it and then closed those decisions. Deep

0:52

Seek harness ships the same job with

0:55

every one of those decisions still open

0:58

while it is running. Here's what that

1:00

means in practice. Pull a component out

1:03

of a normal coding agent and it breaks.

1:06

Lose a dependency halfway through a task

1:09

and it breaks unless you hard coded a

1:12

plan B in advance. In this one, every

1:15

component declares what it needs and the

1:18

runtime keeps the undo button for you

1:21

available for every change it makes.

1:23

Nothing is hard coded, so nothing has to

1:26

restart. You're going to see that later

1:28

in this video. There is a formal paper

1:30

behind this and a framework called

1:32

Cordis, but I'm not going to read a

1:35

paper for you. But, here's why I'm

1:37

making this video. The part of an AI

1:39

agent that used to cost you money just

1:42

went to zero. Everything written about

1:45

this so far has been written about the

1:47

repository, not from using it. So, what

1:49

we're going to do is install this

1:51

together and give it a real job. In In

1:55

install it, we're going to open the

1:57

website, and we can see it right here,

1:59

right at the front. Everything is a

2:01

plugin, and you're going to understand

2:03

why they say that in just a bit. And we

2:06

also have the GitHub repo over here.

2:09

190,000

2:11

stars. That is insane. The fastest

2:13

growing repo on GitHub by far. And we

2:17

can either get these from the website or

2:19

from the repo, but I've gone ahead and

2:22

copied this, and I'm going to run it on

2:26

my terminal right now. I'm just going to

2:28

paste it, hit enter, and let it install

2:30

itself. We'll give it a few minutes.

2:32

It's going to take about 5 minutes, but

2:35

here's where we are. We have our

2:37

dashboard. It actually just opened it,

2:39

and just like that, this is how fast the

2:42

install is. When it finishes, it will

2:45

open this local web app dashboard. And

2:49

the first time it loads, it's going to

2:51

ask you for a Deep Seek API key, but you

2:54

do not need to paste that in. You can

2:56

click configure it later, and we can

2:59

actually put in another API or whichever

3:01

API model that you would like to plug in

3:04

here. I'm going to go to settings, to

3:07

models. I'm going to add a provider, and

3:10

I'm going to be using GLM for this or my

3:12

GLM subscription. Applying it over here,

3:15

and boom, it's green. It's life. We're

3:17

good to go. The great thing is that the

3:19

model is a plugin here. Everything is a

3:21

plugin here, which means you're not

3:23

stuck with Deep Seek's paid API just

3:26

because Deep Seek wrote the harness. I

3:29

mean, a great thing that you can do if

3:31

you want to actually run it for zero

3:34

cost, absolutely for free. So, if you

3:36

have any open local models, you can go

3:39

to add a custom provider, put in the

3:41

provider's ID, display name. Here, you

3:43

can name it whatever you want. Say, for

3:45

example, you're running it on Ollama,

3:47

paste the base URL along with your the

3:50

key, and click on create provider. I'm

3:54

going to use this with my GLM

3:55

subscription that I'm paying $10 a month

3:58

for, and that is more than enough for

4:00

this. But, feel free to input whatever

4:03

subscription or API key or local model

4:07

that you have. A quick disclaimer

4:08

though, free hosted models have caps.

4:11

For example, Google's free Gemini tier

4:14

also works here, but they stopped

4:16

publishing their limits. The only

4:19

genuinely uncapped free path is running

4:21

the weights on your own local machine.

4:23

If you have a decent graphics card,

4:25

Ollama has one of the best one-line

4:27

installs for exactly this, and there's

4:30

no meter at all. I do not have that on

4:33

this hardware, so I'm not going to show

4:35

you something I can't actually run. What

4:38

is free forever, regardless of your

4:41

situation, is the harness itself. The

4:43

model is the only part anybody can ever

4:45

charge you for, and you get to pick who

4:48

that is. But, the way to find out what a

4:51

coding agent is actually worth is to

4:53

give it something real to do. Everything

4:56

is a plugin. That is literally the

4:58

headline on Deep Seek's own front page,

5:01

and they mean it far more literally than

5:04

you would expect. I mean, literally, you

5:05

can go to settings, go to plugins, and

5:09

you'll see that literally every single

5:11

thing in here is a plugin that you can

5:13

disable and enable. You can customize

5:16

this as much much as you want. Every

5:19

part of it is customizable. Literally,

5:21

the sidebar you're looking at right here

5:24

is customizable. The commands are a

5:27

plugin, and you can disable them. This

5:29

means you can add and create as many

5:32

plugins as you'd like into the harness.

5:35

Over here, we have creator mode that you

5:37

can select just like that, and that is a

5:40

preset that loads the plugin development

5:42

automatically. So, I'm going to build

5:45

the thing every coding agent should

5:47

already have, but none of them actually

5:50

do. And this is the prompt. Add a

5:52

plug-in that fires a Discord

5:54

notification when a run finishes and

5:55

puts the token count and what it cost me

5:58

into the notification itself. How crazy

6:01

is that? I mean, so many times I would

6:03

be just working on something else and I

6:06

would have another agent work on

6:08

something that runs for like 9 minutes

6:10

and I completely forget about it because

6:12

it's in another window and I never get

6:15

to see it finished its run. So, I'm

6:17

going to make the thing I wish I had

6:19

into a tool myself, like this. And while

6:22

it does its work, let me show you the

6:24

part that made me actually pay attention

6:27

to this thing. The job is running behind

6:29

me right now and I can watch every

6:31

single thing it's doing while it does

6:33

it. Every single run is traceable. The

6:36

context is traceable. The assistant, the

6:39

tool calls, every single call on this

6:44

list is traceable. Every single error

6:46

that you're seeing right now is

6:47

traceable. Not summarizable, traceable.

6:50

When you open the trajectory, you get

6:52

the exact system prompt that it used

6:55

right here. You get to see the context

6:58

that it injected word for word. You get

7:01

to see which skills loaded, which

7:03

didn't, and also why. Every tool call

7:06

with the payload it sent and the result

7:09

it got back, the thinking, how long each

7:11

step took. And you can even see the

7:13

payload, the result, the timing, how

7:15

long this took. Everything I just said

7:17

about components coming and going safely

7:20

sounds like gibberish until you test it.

7:23

So, I'm going to kill it mid-task. It

7:26

did complete the task we gave it, so I'm

7:27

going to give it another one so we can

7:29

kill it while it's doing it.

7:32

I'm going to ask it to make it into an

7:33

on-screen window in this session as

7:35

well. I'm going to hit run and then I'm

7:38

just going to let it start just a bit.

7:41

Let's look at its trajectory, what it's

7:43

doing. There you go. It's bringing in

7:46

the context. We can see turn two where

7:48

it started. And just like that, I'm

7:51

going to kill it right here.

7:53

Zoom where we left off, and I'm going to

7:56

send this right here. And you're going

7:58

to see that it's going to quite

8:00

literally pick up where we left off with

8:03

the same exact context that the same

8:06

exact user preference, the same exact

8:08

assistant and tool call that it listed

8:11

out. Because guess what? We have all of

8:14

this data. Now, to be fair to this, it

8:17

is a developer preview. The only tagged

8:20

release is a release candidate. So, what

8:22

I'm showing you right now is in its

8:24

beta. And the readme file literally says

8:27

in capital letters that there will be

8:28

breaking changes. Things will go wrong

8:31

for you that did not necessarily go

8:34

wrong for me, or things might go wrong

8:35

for me that will not go wrong for you.

8:37

But that is the difference. When this

8:39

breaks, it can come back. And the reason

8:42

it comes back is the same reason this

8:44

next thing I'm about to show you is

8:46

possible. So, let's go ahead and see

8:48

what it made. And there it is. A

8:50

[clears throat] notification bar just

8:52

right here. Now, obviously some things

8:54

to fix like the the black on black text

8:57

because we can't really read it unless

8:59

we highlight it. And it told us that we

9:02

need to load a job for us to test it in.

9:05

So, this would be the first job that it

9:07

does, the first run that it does while

9:08

being tracked. So, let's go ahead and do

9:10

that. Let's test it out. Also, please

9:15

change text color to white

9:18

so we're able

9:20

to read it. So, there you go. This run

9:22

just finished, and it fixed the color.

9:25

As you can see, the counter is broken.

9:28

So, I've gone ahead and told it to fix

9:30

it for us. But that is what a plug-in

9:33

looks like. Literally, you can create as

9:34

many plug-ins as possible as you would

9:37

like. You can disable them by clicking

9:39

this. If you click it, then there's also

9:41

a play button, so you can enable,

9:42

disable as much as you'd like, and you

9:44

can customize this as much as you want.

9:47

And this, ladies and gentlemen, is

9:49

something that you cannot get on Claude

9:52

Code or on Codex, either. Here's the

9:54

comparison between Claude Code and Deep

9:57

Seek Harness in one table. Yep, read

10:00

that last row twice. And then, let me

10:03

show you the thing that makes this whole

10:05

comparison collapse. There are two

10:08

packages sitting inside this repo that

10:10

almost nobody is talking about. One is

10:13

called {dash} sub agent Claude Code, the

10:16

other is called {dash} sub agent Codex.

10:18

These are not model providers. This is

10:20

not an Anthropic key in a settings box.

10:24

They spawn Claude Code and Codex's

10:26

actual child processes and hand them a

10:29

task. So, your agent gets two new tools,

10:32

one called sub agent Claude, one called

10:34

sub agent Codex. It can decide by itself

10:37

that a job is better handled by Claude

10:39

Code and then go and run Claude Code.

10:42

Now, there are three things you need to

10:44

know about this. It is one shot. Every

10:47

call starts a fresh process and a

10:49

conversation that cannot be resumed. One

10:52

task, one answer, no follow-up. Both

10:55

providers load dormant, so the preset

10:58

has to decide to give your agent the

11:00

tool. This is not switched on the first

11:02

time you open it by default. And the one

11:05

that will catch you out, it strips

11:07

credentials, shaped variables out of the

11:09

environment on purpose. So, whatever key

11:12

is already in your shell does not reach

11:14

the child. You have to pass it in

11:16

explicitly, which means this thing is

11:18

not a competitor to the agent you're

11:20

already paying for. It is a layer that

11:23

can drive it. This is how you can think

11:26

of this. Every take on this has been a

11:28

versus. This versus Claude Code, this

11:31

versus your current agent. Pick one.

11:34

That framing is wrong and the documents

11:37

themselves say so. Anthropic is in the

11:40

provider list that ships with Deep Seek

11:43

Harness. So is OpenAI, so is Bedrock,

11:46

Vertex, Codex. So you add a provider,

11:49

pick Anthropic, put your key in and now

11:51

you're running Opus inside the free

11:54

harness with the trace and with the

11:56

plugins, which means the question is not

11:59

Deep Seek or Claude. The harness and the

12:01

model were always two separate purchases

12:04

and one of them just went to zero. One

12:07

real limitation that is an API key, not

12:10

your Claude subscription and Claude API

12:12

is not famous for being cheap.

12:15

For two years the agent and the model

12:18

came as one product. If you wanted the

12:20

good model, you took whatever harness

12:23

came bolted onto it. That just stopped

12:25

being true. If I were starting today, I

12:28

would install it, point it at a free or

12:30

a cheap model for a week on the work

12:32

that does not need a frontier brain and

12:36

see how much of my month that actually

12:38

covers. Comment which model you're going

12:40

to point this at first because I want to

12:42

know whether everyone lands on the same

12:45

one. And if you have already run this,

12:47

tell me what you thought and what you're

12:50

currently using it for. If you enjoyed

12:52

this video, make sure to leave a like

12:54

and if you're new to my channel, then

12:56

subscribe because I have a ton more

12:58

content like this coming your way. Oh,

13:01

and the algorithm gods just told me

13:02

you're very likely to enjoy this video

13:04

as well. So click it and I'll see you

13:07

there.

Interactive Summary

This video introduces the 'Deep Seek harness,' an open-source coding agent framework that separates the AI model from the 'harness' (tools, memory, and interface). Unlike closed systems such as Claude Code, this harness is fully customizable, modular via plugins, and allows users to swap between different AI models, including running them locally. The host demonstrates the installation process, how to configure various API providers or local models, and how to use the framework to develop new features, all while maintaining a high level of transparency through detailed execution tracing.

Suggested questions

4 ready-made prompts