I Built My Own Jarvis with Claude Code (No Code Setup) — Transcript

Full transcript

1. 0:00Tony Stark had Jarvis, an AI that lived
2. 0:03inside his house, read his files, ran
3. 0:05his systems, built his suits, and
4. 0:07answered him wherever he was in the
5. 0:09world. Meanwhile, you're paying [music]
6. 0:11$20 a month for an AI that still can't
7. 0:13touch a folder on your own computer
8. 0:15without a thousand permissions first.
9. 0:18That's the gap we're closing today.
10. 0:20We're going to build your own Jarvis,
11. 0:22free, running on your computer, reading
12. 0:24your files directly, doing real work in
13. 0:27the background. [music]
14. 0:28And by the end of this video, you'll
15. 0:29have a personal AI assistant on your PC
16. 0:32and in Slack, ready to help from your
17. 0:34phone anywhere. And the best part is you
18. 0:36don't need to write a single line of
19. 0:38code to build this. No subscriptions
20. 0:40required to get started. One tool
21. 0:42handles most of the heavy lifting, and
22. 0:43I'll explain every piece as [music] we
23. 0:45go, so you're never guessing what you
24. 0:47just did. Let's build it.
25. 0:56Before we touch anything, let me show
26. 0:58you what you're getting. Because 10
27. 1:00minutes of setup is a lot to ask without
28. 1:02knowing what's at the end of it. This is
29. 1:05Open Jarvis. It's a free open-source
30. 1:07project on GitHub, built by developers
31. 1:09and available to anyone. Think of Open
32. 1:12Jarvis as the body of your assistant. On
33. 1:14its own, it's just a shell. We bring it
34. 1:17to life by connecting two things to it,
35. 1:19a brain, which is an AI model, and
36. 1:21hands, which is permission to read your
37. 1:23files and talk to other apps on your
38. 1:25computer. Now, you might be wondering,
39. 1:28why not just use ChatGPT or Claude's
40. 1:30regular app for this? Here's the honest
41. 1:32answer. Those tools live in the cloud.
42. 1:35They can't see your desktop. They can't
43. 1:36open a folder sitting on your D drive.
44. 1:39They can't rename files or build you a
45. 1:41website that saves to your machine.
46. 1:43Every time you want them to see
47. 1:44something, you have to manually hand it
48. 1:46over. Open Jarvis flips that. It runs on
49. 1:49your computer, so it already has access
50. 1:52to your files. It can read them, work
51. 1:54with them, and keep going without you
52. 1:56baby-sitting it. And the final piece,
53. 1:58the one that makes it feel like the
54. 2:00actual Jarvis, is that we're going to
55. 2:02connect it to Slack, so you can message
56. 2:04it from your phone when you're away from
57. 2:05your desk. You'll be sitting at a cafe,
58. 2:08type, "Pull up the notes from last
59. 2:09week's meeting and summarize them." And
60. 2:11your PC at home will do the work and
61. 2:13reply to you. That's what we're
62. 2:15building. Now, here's the question. How
63. 2:17do we actually build this without
64. 2:19writing any code? That's where our
65. 2:21second tool comes in. The tool doing the
66. 2:23real work for us is called Claude Code.
67. 2:26It's made by Anthropic, the same company
68. 2:29behind Claude, and it's designed to read
69. 2:31instructions in plain English and do
70. 2:33technical work for you. Think of Claude
71. 2:36Code as a developer who sits in your
72. 2:38terminal. You tell it what you want in
73. 2:40normal language. "Install this,
74. 2:42configure that, fix this error." And it
75. 2:45writes the code, downloads the files,
76. 2:47edits the settings, and troubleshoots
77. 2:49along the way. The stuff that would
78. 2:51normally take someone with coding
79. 2:53experience, Claude Code handles for you.
80. 2:56So, the plan is simple. We tell Claude
81. 2:58Code to build Jarvis. It builds Jarvis.
82. 3:02First, install Claude Code. Follow the
83. 3:04instructions on the Anthropic site. It's
84. 3:07a quick install. Once it's installed,
85. 3:09create a new empty folder somewhere on
86. 3:11your computer. This is where Jarvis is
87. 3:14going to live. Open that folder in your
88. 3:16terminal and start Claude Code inside
89. 3:18it. Now, paste in this prompt. "Install
90. 3:22Open Jarvis, configure the AI model, and
91. 3:24fix any errors you run into along the
92. 3:27way." Press enter. Claude Code starts
93. 3:29working. It will download Open Jarvis
94. 3:32from GitHub, start installing the
95. 3:34required pieces, and set up all the
96. 3:36configuration files. You'll see it
97. 3:38moving through the steps in real time,
98. 3:40reading things, writing files, running
99. 3:42commands. You don't need to understand
100. 3:44any of it. You just need to watch for
101. 3:46one specific moment. At some point,
102. 3:49Claude Code will pause and ask you for
103. 3:52an API key. Here's what that means in
104. 3:54plain English. An API key is like a
105. 3:57password that lets Jarvis talk to an AI
106. 3:59model. Without the key, Jarvis has a
107. 4:02body, the open Jarvis shell, but no
108. 4:04brain. It can't actually think or
109. 4:06respond. The key is what unlocks the
110. 4:09brain. Now, there are a lot of AI models
111. 4:11you could use. For this video, we're
112. 4:13starting with Nvidia's free models
113. 4:15because they genuinely cost nothing and
114. 4:17they're fast enough for daily use. Later
115. 4:20in the video, I'll show you how to
116. 4:21switch to Claude or how to run a model
117. 4:23fully offline on your own computer. But,
118. 4:26let's start with the free option. Open
119. 4:28build.nvidia.com
120. 4:29in your browser. Sign in. A free account
121. 4:32works. Once you're in, click on your
122. 4:34profile in the top right corner, go to
123. 4:36API keys, and click generate API key.
124. 4:39Give the key a name, something simple
125. 4:41like Jarvis, so you remember what it's
126. 4:43for later, and click generate. Nvidia
127. 4:46will show you the key. Copy it
128. 4:48immediately because this is usually the
129. 4:50only time it'll show you the full key.
130. 4:52Now, head back to Claude code. It should
131. 4:54have already opened a file for you to
132. 4:56paste the key into. Paste it in, save
133. 4:58the file, and type done back in Claude
134. 5:01code to let it know you're ready. One
135. 5:03thing before we move on. Treat that API
136. 5:05key like a password. Don't paste it into
137. 5:08chat messages, don't put it in
138. 5:09screenshots, don't share it. If someone
139. 5:12else gets it, they can use it on your
140. 5:14account. Claude code picks up where it
141. 5:16left off. It wires in Nemotron 3 Super
142. 5:19as the main brain. That's a strong
143. 5:21general-purpose model from Nvidia. Then,
144. 5:23it adds GLM 5.3 Flash, Nemotron 3.5
145. 5:27Lightning, and GPT-OSS 20B. Think of
146. 5:30them as alternatives Jarvis can switch
147. 5:33between depending on the task. The idea
148. 5:35is to use a more capable model for
149. 5:37complex tasks and a faster, lighter one
150. 5:40for simpler requests. Once the
151. 5:42installation finishes, Jarvis opens
152. 5:44automatically in your browser. Now, a
153. 5:47real-world moment. When we recorded
154. 5:49this, we hit one small error with the
155. 5:51memory system, the part that lets Jarvis
156. 5:53remember things across conversations. If
157. 5:56this happens to you, don't panic. This
158. 5:58is actually the easiest problem to
159. 6:00solve, and the pattern works for any
160. 6:02error you hit in this entire video. What
161. 6:04we did? Copied the error message, pasted
162. 6:07it into Claude Code, and typed something
163. 6:09like, "I'm getting this error. Please
164. 6:11fix it." Claude Code read the error,
165. 6:13figured out what was missing, installed
166. 6:15it, and we were back up. Remember that
167. 6:17pattern. Any error in this video, any
168. 6:20error at all, paste it into Claude Code,
169. 6:22ask it to fix it, let it work. That's
170. 6:25how non-coders handle technical problems
171. 6:27now. Your Jarvis is alive. All right,
172. 6:30you've got Jarvis running in your
173. 6:32browser. Let's actually use it, because
174. 6:34this is the part that makes everything
175. 6:36we just did worth it. Let me walk you
176. 6:39through four things you can do right
177. 6:40now, from easiest to most impressive.
178. 6:43One, summarize an entire folder in one
179. 6:46message. Say you've got a folder with 30
180. 6:49documents in it, project notes, meeting
181. 6:51transcripts, PDFs, random drafts. You
182. 6:54don't want to open each one. In Jarvis,
183. 6:57just type, "Go to D colon backslash
184. 7:00YouTube and summarize what's inside."
185. 7:02Jarvis opens the folder, lists what's in
186. 7:05it, reads through the files, and gives
187. 7:07you a clean summary. One message. No
188. 7:09uploads, no copy-pasting. The reason
189. 7:12this matters? This is the exact task
190. 7:14that costs you the most time with a
191. 7:16normal AI chat. You'd be uploading files
192. 7:19one at a time, waiting for each to
193. 7:20process, then losing context when you
194. 7:22hit limits. Here, it just works. Two,
195. 7:26find a specific document fast. You know
196. 7:29you wrote something, but you can't
197. 7:31remember where it is or what you called
198. 7:33it. Instead of digging through folders,
199. 7:35just ask, "In my client files folder,
200. 7:38find the Q3 marketing plan and tell me
201. 7:40the three main points." Jarvis looks
202. 7:42through the folder, finds the file,
203. 7:44opens it, and pulls out exactly what you
204. 7:47asked for. A 10-minute search turns into
205. 7:49a one-line question. Three, build you a
206. 7:52working website. This is where it stops
207. 7:55feeling like a chatbot. Try something
208. 7:57like, "Build me a simple note-taking
209. 7:59website. I want to add notes, delete
210. 8:01them, and have them saved so they don't
211. 8:03disappear when I close the tab." Jarvis
212. 8:05actually writes the code, saves it as
213. 8:08real files on your computer, and gives
214. 8:10you a working website you can open in
215. 8:11your browser. You didn't write a single
216. 8:14line of code. You described what you
217. 8:16wanted, and your assistant built it.
218. 8:18Four, hand it a job and walk away. This
219. 8:21is the shift that changes how you work.
220. 8:24Instead of sitting there going back and
221. 8:26forth with the AI, you give it a task
222. 8:28and let it run. Research the top five AI
223. 8:31assistants released this year, compare
224. 8:33their features, and write me a one-page
225. 8:35summary. Jarvis starts working. You go
226. 8:37make coffee. You come back, it's done.
227. 8:40That's the difference between a chatbot
228. 8:42and an assistant. A chatbot waits for
229. 8:44you. An assistant does the work. Now,
230. 8:47we've got Jarvis working great on your
231. 8:49computer. But, what if you want to
232. 8:51change the brain? Or run it fully
233. 8:53offline? Or talk to it instead of
234. 8:55typing? That's next. The Nvidia models
235. 8:58we set up are a solid default. But, one
236. 9:01of the best things about Open Jarvis is
237. 9:03that you're not locked into any one AI.
238. 9:06You can swap the brain depending on what
239. 9:07you need. Let me show you three upgrades
240. 9:10and when each one makes sense. Upgrade
241. 9:12one, run AI fully on your own computer.
242. 9:16If you care about privacy, or you want
243. 9:18to use Jarvis somewhere with no
244. 9:19internet, this one's for you. We're
245. 9:21going to install a tool called Ollama,
246. 9:23which runs AI models directly on your
247. 9:25machine. Nothing you type leaves your
248. 9:27computer. No cloud, no accounts, no API
249. 9:30calls. Go back to Claude code and paste
250. 9:33this. Set up a free local model for
251. 9:35Jarvis that works offline and added to
252. 9:38the model list. Claude Code installs
253. 9:40Ollama for you, downloads a compatible
254. 9:42model, and plugs it into Jarvis. The
255. 9:44download can take a few minutes
256. 9:46depending on your internet because these
257. 9:48models are big files. Once it's done,
258. 9:51refresh Jarvis in your browser, click
259. 9:53the model name at the top of the chat,
260. 9:54and you'll see your new local model in
261. 9:56the list. Select it. One honest
262. 9:59trade-off. Local models are slower than
263. 10:01cloud models, especially if your
264. 10:03computer doesn't have a dedicated
265. 10:05graphics card. If you're on a basic
266. 10:07laptop, expect longer wait times. If
267. 10:09you've got a gaming PC with a good GPU,
268. 10:12it'll feel snappy. The upside is total
269. 10:15privacy. Your prompts never leave your
270. 10:17machine. Upgrade two, use Claude for
271. 10:19stronger reasoning. If you want higher
272. 10:22quality answers for harder tasks,
273. 10:24complex writing, nuanced analysis,
274. 10:26trickier code, plug in Claude. Open
275. 10:29console.anthropic.com.
276. 10:31If you don't have an account, create
277. 10:33one. Go to billing and add some credits.
278. 10:35You can start with as little as $5. Then
279. 10:38go to API keys, click create key, give
280. 10:41it a name, and copy the key. Important
281. 10:44heads-up. This is paid and it's separate
282. 10:46from a Claude.ai subscription. If you
283. 10:49already pay $20 a month for Claude's
284. 10:51regular app, that does not cover API
285. 10:53usage. API is billed by how much you use
286. 10:56it. Every message costs a small amount.
287. 10:59For casual use, it's cheap. For heavy
288. 11:01use, it adds up. Keep an eye on the
289. 11:03billing page. Now jump to Claude Code
290. 11:06and tell it, add my Claude API key like
291. 11:08the Nvidia key. Then set up Claude in
292. 11:10Jarvis and restart it. Claude Code
293. 11:13installs the Anthropic connector,
294. 11:15restarts Jarvis, and when you refresh,
295. 11:17Claude shows up in your model list. Pick
296. 11:19it when you want its reasoning quality
297. 11:21for a specific task. Upgrade three, talk
298. 11:24to Jarvis instead of typing. This is the
299. 11:27one that really makes it feel like the
300. 11:28movies. Paste this into Claude Code. Set
301. 11:31up free local speech for Jarvis so I can
302. 11:34talk to it with my microphone and hear
303. 11:36it reply. Cloud Code installs a local
304. 11:38speech-to-text and text-to-speech
305. 11:40system. Everything runs on your machine,
306. 11:43so your voice isn't being sent anywhere.
307. 11:45Once it's installed, refresh Jarvis,
308. 11:47click the microphone icon in the chat
309. 11:49box, and your browser will ask for
310. 11:51microphone permission. Allow it. Now,
311. 11:53talk to it. Ask it a question out loud.
312. 11:56It transcribes what you said, thinks,
313. 11:58and replies back to you in a voice.
314. 12:01>> Assistants 2026 summary. txt
315. 12:05The summary covers these five notable AI
316. 12:08assistants from 2026.
317. 12:11One Siri AI, Apple.
318. 12:13>> You've now got Jarvis with a brain you
319. 12:15can swap running however you want it to
320. 12:18with a voice. We're getting close to the
321. 12:20real version, but there's still one
322. 12:22thing missing. Right now, Jarvis only
323. 12:25works when you're sitting at your
324. 12:26computer. Let's fix that. This is the
325. 12:28piece that changes everything.
326. 12:31Everything we've built so far lives on
327. 12:33your computer. The moment you walk away
328. 12:35from your desk, you can't reach Jarvis.
329. 12:37We're going to fix that by connecting it
330. 12:39to Slack. Then, you can message Jarvis
331. 12:42from your phone, and Jarvis on your PC
332. 12:44answers you back. Why Slack? It's free,
333. 12:47it has a great mobile app, and most
334. 12:49teams already use it for work. Here's
335. 12:51how the whole thing fits together. We're
336. 12:53going to create a tiny Slack app that
337. 12:55acts as the messenger between your phone
338. 12:58and Jarvis. When you type something in
339. 13:00Slack, the Slack app passes it to Jarvis
340. 13:02on your PC. Jarvis finds the answer, and
341. 13:05it comes back through Slack to your
342. 13:07phone. Setting this up takes seven
343. 13:09steps. I'll walk you through all of
344. 13:10them, but don't try to memorize
345. 13:12anything. Jarvis shows you the same
346. 13:14seven steps on screen while you do it.
347. 13:17Open Jarvis, go to data sources, then
348. 13:19messaging channels, then Slack. You'll
349. 13:22see the setup wizard. Let's walk through
350. 13:24it. Step one, create the Slack app. Open
351. 13:27api.slack.com/apps,
352. 13:30click create new app, and choose from an
353. 13:32app manifest. A manifest is just a
354. 13:35settings file. It tells Slack what kind
355. 13:37of app you're building and what
356. 13:38permissions it needs. Jarvis gives you
357. 13:40one, pre-written, ready to paste. Step
358. 13:43two, choose your workspace, select JSON,
359. 13:46and paste the manifest. Pick whichever
360. 13:48Slack workspace you want Jarvis to live
361. 13:50in. If you don't have one, create a free
362. 13:52one for yourself first. It takes 2
363. 13:54minutes. When you select the format,
364. 13:56pick JSON, and paste the manifest using
365. 13:59the copy button in Jarvis. Step three,
366. 14:01install the app. Click next, then
367. 14:04create. Then click install app on the
368. 14:06left, then install to workspace, and
369. 14:09allow it. This is Slack asking if you're
370. 14:11sure you want to add this app to your
371. 14:13workspace. Now, Slack has your app. Step
372. 14:16four, get the first token. In your Slack
373. 14:19app settings, click OAuth and
374. 14:21permissions. Right at the top, under
375. 14:23OAuth tokens, you'll see the bot user
376. 14:25OAuth token. It starts with xoxb.
377. 14:28Copy it. This is the key that lets
378. 14:30Jarvis read your messages and post its
379. 14:32replies. Step five, get the second
380. 14:35token. Click basic information, scroll
381. 14:38to app level tokens, and click generate
382. 14:40token and scopes. Name the token socket.
383. 14:44Add the scope connections:write.
384. 14:47This lets Slack send your messages
385. 14:48straight to Jarvis on your PC with no
386. 14:50website or server needed. Click generate
387. 14:53and copy the token that starts with
388. 14:55xapp. You now have two tokens. Same rule
389. 14:58as the API keys from earlier, keep both
390. 15:01private. Step six, app icon. This just
391. 15:04adds an icon so your app looks nice in
392. 15:06Slack. Totally optional. Skip it or add
393. 15:08one, your call. Step seven, connect
394. 15:11everything. Head back to Jarvis, paste
395. 15:14both tokens into their matching fields,
396. 15:16and click connect. It shows connected. A
397. 15:18real world moment, again. When we did
398. 15:21this, Slack showed as connected, but the
399. 15:23bot didn't reply to anything. So, we
400. 15:25told Claude code, "Slack shows
401. 15:27connected, but the bot never replies.
402. 15:30Please fix it." It found the missing
403. 15:32piece, installed it, and the bot started
404. 15:34replying. If you hit the same issue, you
405. 15:36now know the drill. Now the fun part.
406. 15:39Open Slack on your phone. Find Open
407. 15:41Jarvis in the app section. If you don't
408. 15:43see it, search for Open Jarvis at the
409. 15:45top. Tap it, open the messages tab, and
410. 15:48send it something. Do I have any meeting
411. 15:50scheduled today? Your phone sends the
412. 15:52message to Slack. Slack passes it to
413. 15:55Jarvis on your computer. Jarvis checks
414. 15:57your schedule and texts you back today's
415. 15:59meetings with the times right there in
416. 16:01the chat. No opening apps, no scrolling
417. 16:04through your calendar. You just asked
418. 16:05your assistant and it told you. One
419. 16:07thing to remember, Jarvis runs on your
420. 16:09PC, so keep it on and it'll reply from
421. 16:12anywhere. You just messaged your own
422. 16:14Jarvis from your phone. One important
423. 16:17catch, your computer has to stay on and
424. 16:20connected to the internet for this to
425. 16:21work. Jarvis is running on your machine,
426. 16:24not in the cloud. If you close your
427. 16:26laptop or shut down your PC, Jarvis goes
428. 16:28to sleep and won't reply until you wake
429. 16:31it back up. If you want Jarvis available
430. 16:33all day, leave your PC running when you
431. 16:35leave the house. Before you start
432. 16:37handing Jarvis the keys to your entire
433. 16:39digital life, three quick things to keep
434. 16:41you out of trouble. First, permissions
435. 16:44matter more than you think. Jarvis can
436. 16:46read any folder you point it at. It can
437. 16:48also create and change files and even
438. 16:51run commands if you switch that on.
439. 16:53Start small. Point it at one test folder
440. 16:55with sample files before you point it at
441. 16:58your entire documents directory. Get
442. 17:00comfortable with how it behaves before
443. 17:02you give it broader access. The same way
444. 17:04you wouldn't give a new employee the
445. 17:06keys to the whole office on day one.
446. 17:08Second, think before connecting personal
447. 17:10accounts. Beyond what we connected
448. 17:12today, you might want to connect Jarvis
449. 17:14to your email, your cloud storage, your
450. 17:16notes app. All of that is possible with
451. 17:19the right integrations. But, every
452. 17:21integration is another door into your
453. 17:23personal data. Read what permissions
454. 17:25each one asks for. If something asks for
455. 17:28more access than it needs, like an email
456. 17:30integration asking for permission to
457. 17:32send messages when you only want it to
458. 17:34read, stop and think about whether you
459. 17:36actually want that. Third, watch your
460. 17:39API spending if you go paid. The Nvidia
461. 17:42setup and the local Ollama setup are
462. 17:44free. If you plug in Claude's API or any
463. 17:47other paid model, you're being billed
464. 17:49per message. For light personal use, it
465. 17:51usually stays cheap. But, if you build
466. 17:53an automation that pings Jarvis hundreds
467. 17:56of times a day, or you ask it to process
468. 17:58massive files repeatedly, costs can
469. 18:00climb fast. Set a billing alert on your
470. 18:03API provider's dashboard so you don't
471. 18:05get a surprise invoice. You None of this
472. 18:07is meant to scare you off. These are the
473. 18:09same precautions you take with any new
474. 18:11tool that touches your personal stuff.
475. 18:13Set it up thoughtfully and Jarvis is one
476. 18:15of the most useful things you'll ever
477. 18:17add to your workflow. So, that's your
478. 18:19Jarvis. It reads your files. It finds
479. 18:22documents. It builds websites. It drafts
480. 18:24reports. It switches between different
481. 18:27AI brains depending on what you need. It
482. 18:29talks to you and it answers you on your
483. 18:31phone when you're nowhere near your
484. 18:33desk. Tony Stark had a team of
485. 18:35engineers, a billionaire budget, and
486. 18:37years of R&D. You had Claude code and
487. 18:40one afternoon. And honestly, we've only
488. 18:42scratched the surface here. Once you
489. 18:44start adding integrations, email, your
490. 18:47note app, your project tools, Jarvis
491. 18:49stops being a cool demo and starts being
492. 18:51the thing you actually run your day
493. 18:53through. That's the direction to take
494. 18:55this if you want to go deeper. If you
495. 18:57want to try this, every prompt from the
496. 18:58video is inside my free Staying Ahead
497. 19:01WhatsApp community. Link's in the
498. 19:02description. Join, grab the prompts,
499. 19:05build your own project. And if there's a
500. 19:07workflow you'd want me to break down
501. 19:08next, go ahead and drop it in the
502. 19:10comments. Our team will actually try to
503. 19:12pick the next video based on what you
504. 19:14ask for. All right, catch you in the
505. 19:16next one.