HomeVideos

Stop Prompting Claude. Use This Method Instead (100% Free)

Now Playing

Stop Prompting Claude. Use This Method Instead (100% Free)

Transcript

441 segments

0:00

You're not going to lose your job to an

0:01

AI, but you're going to lose your job to

0:02

somebody who uses AI.

0:05

>> What jobs are going to be made redundant

0:07

in a world where I am sat here as a CEO

0:10

with a thousand AI agents. I'm thinking

0:12

about my CFO, my graphic designers, my

0:13

video editors. What jobs are going to be

0:15

impacted?

0:15

>> All of them.

0:16

>> So, we actually built a personal Jarvis.

0:18

>> No

0:26

>> Hey Chad, how do I solve merge conflicts

0:28

here?

0:32

>> This is my Jarvis agent clone system

0:36

that makes me 10 trillion a month and

0:38

swipes on Tinder at the same time. I'm

0:40

just joking. This is a flashy HTML file.

0:43

It has absolutely no logic behind it. If

0:45

you have the same for you page like me,

0:47

you see all of these flashy AI operating

0:49

systems going around. But in reality,

0:51

either has no backend system hooked up

0:53

or it's completely overkill and it

0:55

actually doesn't do anything. So, how do

0:57

you actually set up Jarvis? Well, you

0:59

could be using the voice feature inside

1:01

of Claude, but it's pretty, pretty

1:03

terrible. It can't even spell its own

1:05

name right. So, I set out to build an

1:07

actual useful system. And look at this.

1:09

We can close down Claude and close down

1:11

this. Then, we can click on this app

1:13

right here, click toggle sessions

1:15

overlay, and I can say, "Build me a

1:17

clean website using the premium website

1:19

skill and build a website for a bakery."

1:23

And this AI orchestrator is now going to

1:25

[music] dispatch this to Claude code.

1:27

>> Spinning up a fresh bakery site now with

1:29

premium website skill. I'll make it

1:32

clean and modern. You'll hear from me

1:33

when it's live.

1:34

>> can see how realistic it sounds as well

1:36

because it's using the new fish audio

1:39

2.1 pro model. And now Claude in the

1:41

background is going to be working on

1:42

this site. And this works with both

1:44

Claude or Codex. And look at the

1:46

results.

1:47

>> Golden Crumb Bakery site's live at

1:49

localhost 5173. Full React build with

1:52

hero menu, scheduler, contact form.

1:54

[music] Everything's ready to customize.

1:56

>> How insane is that? In the top right

1:58

corner, you can now see that bigger side

2:00

is finished. Claude is done. It has

2:02

built out this entire thing literally

2:03

just from our voice without stepping

2:05

inside of Claude code. And the thing

2:07

that's even crazier is I built it so

2:09

it's completely free to run. It's

2:10

completely open source. And later in

2:13

this video, I'm giving you the code so

2:14

you can run it as well.

2:15

>> And I'm going to give you my exact

2:17

prompts for how I built it out so you

2:19

can build your own version and customize

2:20

it to your exact workflow. [music] Let's

2:22

not waste any more time. Let's get into

2:24

it.

2:24

>> But first, before we build this entire

2:26

thing out, let's talk about how cheap it

2:28

actually is to run this because you need

2:30

to know the price. For the AI model,

2:32

that's the orchestrator, we need

2:33

something that's fast and cheap. And for

2:35

that, we're using Haiku, which we can

2:37

use through our Claude subscription,

2:39

which basically means it's free. We're

2:40

not paying anything extra for it. For

2:42

hosting, the app is going to be running

2:43

locally, so that's free as well. And for

2:45

the voice API, we need something that

2:47

sounds really, really, realistic without

2:49

being too expensive. And for that, we're

2:51

going to use Fish Audio 2.1 Pro. And at

2:54

the time of recording this, we can

2:55

actually try this model completely for

2:56

free as well. However, that is probably

2:58

temporary. It is, however, still much,

3:00

much cheaper than something like 11

3:02

Labs. Let's actually do a price

3:04

comparison. I'm just going to ask

3:05

Claude, what is the price difference

3:06

between Fish Audio 2.1 Pro and then the

3:10

11 Labs equivalent. Just going to

3:12

dictate that and hit enter. And what

3:13

we'll see is that 11 Labs flagship model

3:16

cost about $85 more per million

3:18

characters, which is around six to seven

3:21

x the price of Fish Audio. And for the

3:23

budget version, the Flash Turbo, it is

3:25

still three times the price. And that's

3:27

why I decided for this build to go with

3:28

the Fish Audio model. And then, of

3:30

course, for the actual coding task, it's

3:32

going to dispatch Babel and Opus, which

3:34

is also included in our already existing

3:36

Claude subscription. And I think I want

3:38

to set it up so we can do that with

3:39

Codex as well, so it can basically use

3:41

both models whenever I want it to do.

3:43

So, this will be a full-on AI

3:45

orchestrator where we can do everything

3:47

with just our voice, much better than

3:49

the current Claude dictation. And this

3:50

basically means that it barely cost us

3:52

anything also run this orchestrator. The

3:54

only thing that's going to cost

3:55

something at one point is the Fish Audio

3:57

API, but it's still pennies. It's really

3:59

not going to cost us that much to run.

4:00

Cool. Now comes the most important

4:02

thing, which is well, how do you build

4:03

this? This first step is crucial because

4:05

if you don't do this, it's going to take

4:06

much, much longer to build. We're going

4:08

to go inside of settings, then inside of

4:11

connectors, and then we're going to

4:12

click add and add a custom connector

4:14

because I want to connect with the Fish

4:16

Audio MCP before we even start building

4:18

this entire thing because then Claude

4:20

can grab a lot of information when we

4:21

are planning it out and when we are

4:23

building. So, this makes it much easier.

4:24

Then we're going to go to this docs

4:26

right here, which is the Fish Audio

4:28

docs. And what you can see is that we

4:29

have this URL right here, the https API

4:32

Fish Audio MCP. I'm going to drop a link

4:34

in the description to this page right

4:36

here so you don't have to search it up

4:37

yourself. And then we're going to call

4:38

the connector for Fish Audio, paste in

4:41

this URL right here, and click add. And

4:43

this is now going to check the

4:44

connection and connect Claude with Fish

4:46

Audio. It now says you're not connected

4:48

to Fish Audio yet, so we need to log in

4:50

with our account. It now says Claude

4:52

wants to access your Fish Audio account.

4:53

This will allow Claude to use all these

4:55

AI audio tools, which is exactly what we

4:57

want, so we're going to click approve.

4:58

Now we can open Claude, and then it is

5:01

connected. In order to set this up, you

5:02

need a Fish Audio account. I'm going to

5:04

drop a link in the description to where

5:06

you can sign up for that. The link does

5:07

give some kickbacks, so really

5:09

appreciate it if you use that. That's

5:10

the best way to support the channel.

5:12

When we are connected, I'll recommend to

5:13

set it to always allow on these settings

5:16

right here. This basically just means

5:17

that Claude doesn't have to ask for

5:18

permission every single time it does a

5:20

tool call. And then we can close it

5:22

down, and now I am just going to ask it,

5:24

"Do you have access to the Fish Audio

5:26

MCP?" Now check the connection, and

5:28

Claude can now check if it has the right

5:31

access. And there we have it. Claude

5:33

says that it has access, which is great.

5:35

You already saw that Fish is a lot more

5:36

affordable than something like Eleven

5:38

Labs, but I want to show you something

5:39

really cool and the reason that we are

5:41

using it. If I go inside of

5:42

text-to-speech, I can set it to the Fish

5:44

Audio S 2.1 Pro, that is right now free.

5:47

We then test it to see, okay, what voice

5:49

do we want to use for our orchestrator?

5:51

And the thing that's so cool is that we

5:52

can add these brackets right here. So, I

5:54

can write laughing, for example, and

5:56

then the next thing is going to have

5:57

that bracket. So, now we can click

5:59

generate speech. It's actually crazy.

6:01

Like, listen to this.

6:02

>> I just started two tasks.

6:04

>> [laughter]

6:05

>> You can sit back and relax.

6:07

>> We can also try this female voice right

6:09

here, Sarah, and then maybe remove the

6:11

dot right here, and then try and

6:13

generate that speech as well. Then we

6:14

choose Sarah up here, then generate that

6:16

too.

6:17

>> And then we can listen to it.

6:18

>> Just started two tasks.

6:19

>> [laughter]

6:20

>> You can sit back and relax. Um

6:22

>> It even says, um, it's crazy how

6:24

realistic the voices are now. The

6:25

technology is really moving insanely

6:27

fast. And at the time of recording this,

6:29

the new model, the Fish Audio S 2.1 Pro,

6:32

is actually free right now at the time

6:34

of recording this. So, great, go ahead,

6:36

create your Fish Audio account, again,

6:38

link in the description, and then we can

6:40

start building the actual orchestrator

6:42

app. It took me a while to figure out

6:44

this next part, but I've basically

6:45

prepared this starter prompt right here.

6:47

It basically explains exactly what it is

6:49

that we want to build and how it should

6:51

be built. And with this prompt, we can

6:53

literally build this out in literally 10

6:54

to 15 minutes. I'll leave a link to this

6:56

starter prompt in the description below.

6:58

But basically, what we'll do is that I'm

7:00

going to right click, create a new

7:01

folder on my desktop, and I'm going to

7:03

call this for the orchestrator. I don't

7:05

know if I spelled that correctly. Then,

7:07

inside of Claude code, it's very

7:08

important that this is running locally.

7:10

We're not going to build this in the

7:11

cloud. We're going to run it as a local

7:12

desktop app. So, make sure you have set

7:14

it to local. Then, for the folder, make

7:16

sure you open the folder that we just

7:17

created, which is the orchestrator. And

7:19

literally, all we need to do is just

7:20

copy this entire prompt, paste it in,

7:22

and say, "Please build this out for me."

7:25

And then hit enter. Claude will now have

7:26

all of the context that it needs, and

7:28

you can build this out in Codex as well,

7:29

by the way. It doesn't have to be

7:30

Claude. And it's now going to build out

7:32

this mini app for us. That's going to

7:34

run locally on our computer. And you can

7:35

see the first phase is that it detects

7:37

the machine, the hardware we are on, and

7:39

then builds the tech stack for our

7:41

specific computer. And stay around

7:43

because later in this video, I'm giving

7:44

you the source code as well. I'm going

7:46

to build this open source, so you can

7:47

grab this as well. This will take a

7:49

little bit of time to build out. Great,

7:51

it is now done. Took about an hour.

7:53

Let's test it. This part is crucial

7:55

because there will probably be some

7:57

bugs. The first thing we're going to do

7:58

is that we're going to set the API key

8:00

cuz we're going to use the Fish Audio

8:02

API key for the voice. So, I can say,

8:04

"Please open where I insert the API

8:07

key." Thank you. The Fish Audio API key.

8:09

This looks very cool so far. I think we

8:12

go through this onboarding right here.

8:13

We allow the microphone. That restarts

8:15

the app. We allow the speech

8:17

recognition. We might need to add

8:19

something like an API key to understand

8:21

and transcribe our words, but let's see

8:23

if it works. All right. Push to talk.

8:25

Shift command space. Hello. Release

8:27

captured. Continue. It works. Basically,

8:29

just make sure that we have both

8:30

authenticated Cloud Code and CodeX on

8:33

our computer. And now comes the field

8:34

where we have to insert the Fish Audio

8:36

API key. We get one of those by clicking

8:39

in the top left corner where it says

8:40

developer right here and then API keys.

8:43

And then we create an API key. Going to

8:45

call it orchestrator.

8:48

Click create. Never expire. I can see

8:50

that it doesn't allow us to paste in.

8:51

So, I'm just going to say, "Right now, I

8:53

can't paste the key. Gives me a error."

8:57

Let's have it fix that right quick.

8:58

There we go. Cloud had to fix some kind

9:00

of input bug, but now we can paste in

9:02

the Fish Audio API key. We can click

9:04

continue. And for our first project, we

9:06

can just click finish for now. Okay, so

9:08

how does this work? We have a couple of

9:10

agents. We have a voice. We have our

9:12

projects right here. So, I wonder if we

9:15

can dispatch an agent now. So, if I say,

9:17

"Please create an agent for Actually,

9:21

create a website for a plumbing

9:23

company." And there we go. After a bit

9:25

of back and forth, look at how cool it

9:27

is now. We now have the app that's

9:29

called Conductor. And I can click on

9:31

toggle sessions overlay right here,

9:32

which basically just shows our active

9:34

sessions. And look at this. Now I can

9:36

say build out a website or a car

9:40

mechanic and run it on 4,520

9:44

and open it in my browser when you're

9:45

done. The coordinator is now going to

9:47

give this task to either Claude or Codex

9:50

and now you can see the task is running

9:52

right now in the right hand corner and

9:53

it's going to say

9:54

>> Running car mechanic site on 4,520 and

9:57

opening it now.

9:58

>> How cool is that? And there we go, then

10:01

it opens and says

10:02

>> Car mechanic site successfully built and

10:03

running on localhost 4,520

10:06

All sections complete with animations.

10:08

>> On the top right corner you can see this

10:09

session is now complete, but I could

10:11

also say the car mechanic site that we

10:13

just built, please make that blue

10:15

instead of yellow. And then it's going

10:17

to look at the past sessions we have had

10:18

and it's going to update the session

10:20

>> mechanic site to blue on it.

10:21

>> How cool is that? And now it says right

10:23

here that it's working again and it's

10:25

going to update the theme of this site.

10:27

>> Car mechanic site theme successfully

10:28

changed from yellow to blue. Dev server

10:30

hot reloaded at localhost 4,520.

10:33

>> So let's give it a refresh. It's still

10:35

yellow it seems, the car mechanic site.

10:37

>> Which site is still yellow? Mechanic,

10:39

salon or plumber?

10:40

>> The mechanic.

10:41

>> Should I debug why the theme didn't

10:42

change or fix something specific?

10:44

>> Please pass this task to Claude and tell

10:46

it to fix it.

10:46

>> Sending fix to Claude. Comic and sidebar

10:48

turning blue now.

10:49

>> And there we go, now the website is

10:51

blue.

10:51

>> Car mechanic site theme conversion to

10:53

blue completed. Server restarted. CSS

10:55

updated. Hard refresh localhost 4,520 to

10:58

clear yellow cache.

10:58

>> Ah, it was a cache it said apparently.

11:01

And if we go inside of settings and have

11:04

all connect is connected, for example I

11:06

have Google Calendar connected, I can

11:08

now say please check my calendar for

11:10

what events I have tomorrow specifically

11:12

just answer how many calls I have. And

11:14

just like before it sends out the

11:16

session, but this time it asks Claude to

11:18

check our MCP into Google Calendar and

11:20

it's now going to return what events I

11:22

have.

11:22

>> Tomorrow has three calls scheduled.

11:24

Stefan Bujic at 1:00 p.m., Volker Hilmer

11:26

at 4:00 p.m., Thomas at 6:30 p.m.

11:28

>> Thank you very much for that.

11:29

>> You're welcome. Ready for the next task.

11:30

>> How cool is that? We can control

11:32

everything that Claude can do without

11:33

being inside of the chat. I can also

11:36

tell it to what are the latest emails

11:38

that I've received today.

11:39

>> Checking your latest emails from today.

11:41

Today's emails, cold pitch from Pavya,

11:43

blood clot login code, two strike

11:44

notices including a lost $79 dispute.

11:47

>> Pretty cool. And if I don't want to see

11:48

this overlay, I can just click this off.

11:50

I can also click shift command O, that

11:52

opens it, toggles it on and off, but I

11:54

can also do that in this window right

11:56

here, toggle off the session overlay.

11:58

And inside of settings, we can change a

12:00

couple of things. We can say, "Okay, do

12:01

we want to launch it login?" We can set

12:03

it to bypass permissions on Claude and

12:05

Codex. I'll probably recommend doing

12:07

that. We can set the speaking rate for

12:09

how fast the speaker actually speaks,

12:11

and we can see the projects that has

12:12

been created. I want this to sound even

12:14

more human, however. So, what I'm going

12:16

to tell Claude is that I want to make

12:19

the voice sound even more human. Do that

12:23

by including brackets like these that

12:27

fits like laughing or serious.

12:31

Basically, what this does is that this

12:33

gives the tone of the voice. So, we can

12:35

prompt Haiku, the AI orchestrator, to

12:38

give it in this voice, which is going to

12:40

make it sound even more human. Cool. I

12:43

tuned it quite a bit. So, now I can add

12:46

something like, "Hello, how's your day

12:47

going?"

12:48

>> Going pretty smoothly, thanks for

12:50

asking. How about you? What's on the

12:51

agenda?

12:52

>> That sounds a lot more human. And that's

12:54

because we're using these brackets that

12:56

basically gives it like a mood or way to

12:58

speak, which is really cool that we can

13:00

do that. So, now we have a full-on voice

13:02

AI system that can dispatch Claude code

13:05

sessions. So, we can basically build

13:06

anything we want. And in my opinion,

13:08

this is a lot cooler way to build rather

13:10

than inside a regular Claude session. If

13:13

you want to set this up yourself, then I

13:14

have left this prompt right here in the

13:16

description. I'm also going to upload

13:19

the code for the app that I've built, so

13:21

you can just grab that if you are on

13:23

Mac. You can also take it and just

13:25

transform it into a Windows app just by

13:27

taking my code and telling Claude to

13:29

turn it into a Windows app. That will

13:30

definitely work as well. For the

13:31

official audio account, I've left the

13:32

link right in the description below. And

13:34

if you want to join one of the biggest

13:35

AI communities in the world that takes

13:37

you from a complete beginner to building

13:38

an AI business in 7 days, and where you

13:41

get all of my Claude skills, then I'm

13:43

also going to leave a link in the

13:44

description for that. You can start with

13:46

a completely free trial. Thank you so

13:47

much for watching. Albert out.

Interactive Summary

This video demonstrates how to build a personalized, open-source AI voice orchestrator, dubbed 'Jarvis'. The system uses Claude or Codex to execute tasks like coding websites or managing emails via voice commands, integrated with Fish Audio 2.1 Pro for realistic speech synthesis. The creator provides a guide on connecting these tools, configuring the orchestrator to run locally, and using specific prompting techniques to make the AI sound more human and efficient in managing workflows.

Suggested questions

4 ready-made prompts