The SECRET Claude Code Upgrade That Has Everyone Going Nuts (Full Guide) — Transcript

Full transcript

1. 0:00Claude has a secret feature hidden
2. 0:02behind a weight list that turns it into
3. 0:04a master of cloud orchestration. You
4. 0:07just talk to one agent and it controls a
5. 0:09fleet of fullyfledged Claude sessions
6. 0:12that run 24/7. They share context, they
7. 0:16share memory and they never shut off.
8. 0:18It's called Claude projects and it's the
9. 0:21ultimate hack if you're someone who is
10. 0:23working on complicated applications and
11. 0:25you need to do so outside of your local
12. 0:27environment. So today I'm going to show
13. 0:29you how to get access to this feature,
14. 0:31how it actually works, and then we're
15. 0:32going to run through a quick demo so you
16. 0:34can start using it right away. Now
17. 0:36before I show you how to get access to
18. 0:37Cloud Code projects, let me explain why
19. 0:39you should even care about this at all.
20. 0:41The big cell is that with Claude
21. 0:43projects, Claude is now the project
22. 0:46manager. You talk to one agent and it
23. 0:48controls everything versus the normal
24. 0:51setup. When we are normally inside of
25. 0:53claude, when you're just sitting there
26. 0:54on the desktop app or inside of the
27. 0:56terminal, you are in charge of
28. 0:59everything. And that means you are in
29. 1:01charge of managing all of these
30. 1:03different terminals and all of these
31. 1:04different agents and you're also in
32. 1:06charge of keeping them all on the same
33. 1:07page. On top of that, unless you are
34. 1:10running something either in the cloud or
35. 1:12you have some sort of like Mac Mini
36. 1:13setup that's always on, when you start
37. 1:16shutting things down, whether that's
38. 1:17your laptop or your computer, your
39. 1:19machine just literally is not on, your
40. 1:21work stops. Compare that to clawed
41. 1:23projects, which runs in Anthropics Cloud
42. 1:26and importantly also uses your usage.
43. 1:30It's not a cloud situation where now
44. 1:32we're paying API cost. This is pulling
45. 1:34from your max plan. So we get pretty
46. 1:36much all the advantages of the cloud
47. 1:37with all the advantages of the
48. 1:39subscription plan which hasn't always
49. 1:40been the case when we talk about
50. 1:42Enthropic in the cloud. So instead of
51. 1:44you being in charge of managing all of
52. 1:46these separate threads, guess who does
53. 1:48it? Well, Claude does it. We just talk
54. 1:51to one orchestrator and it then does
55. 1:53said orchestration. On top of that,
56. 1:56these are not sub agents. It's
57. 1:58controlling full-blown Claude sessions
58. 2:00that also share context and memory
59. 2:02between each other and the orchestrator.
60. 2:04And because it's in the cloud, it's
61. 2:06always going to run no matter where we
62. 2:08are, whether that's overnight. I can
63. 2:10check in remotely from my phone. So, if
64. 2:13you are someone who deals with
65. 2:14complicated projects that you want
66. 2:16access to 24/7, no matter where you are
67. 2:18at, well, this Cloud project makes total
68. 2:22sense. It makes it super easy to manage
69. 2:24multiple agents. So, how do you get
70. 2:26access? Well, right now, you need to
71. 2:28submit an application on this page right
72. 2:30here, and I will put a link to it in the
73. 2:33description. It puts you on a wait list.
74. 2:36Now, when this first came out a couple
75. 2:37months ago and it was like very limited
76. 2:39release, it was kind of hard to get off
77. 2:40the wait list, but as of now, if you put
78. 2:42your name in on this wait list, you're
79. 2:43going to get access to it probably
80. 2:44within 24 hours. I know it was less than
81. 2:4624 hours for me. And a couple weeks ago,
82. 2:48they let everybody off the wait list.
83. 2:50So, there's really no excuse not to get
84. 2:52this up and running on your Claude. Now,
85. 2:55once you get access, it will populate
86. 2:57inside of your desktop app over here on
87. 2:58the left, and it says projects beta.
88. 3:01Remember, we used to have projects back
89. 3:03in the day, especially with the chat
90. 3:04app, where those were essentially just
91. 3:05like folders and you'd have
92. 3:06conversations that were all about some
93. 3:09specific subject. This is much different
94. 3:10than that. Like I said, this is running
95. 3:12in the cloud. This is all about
96. 3:13multi-agent orchestration. So, before we
97. 3:15jump into the next part, a quick word
98. 3:17from today's sponsor, me. I just
99. 3:19released an updated cloud code
100. 3:21masterass, and it is the number one way
101. 3:23to go from zero to AI dev, no matter
102. 3:25your technical background. So, it
103. 3:27doesn't matter where you are starting
104. 3:28from your technical journey. It could be
105. 3:30literally zero. I will bring you up to
106. 3:32speed on the most powerful AI tools in
107. 3:34the game today. I update this every
108. 3:36single week. So, if you want to get your
109. 3:38hands on this, you can find it inside of
110. 3:39Chase AI Plus. I will put a link in the
111. 3:42pin comment. So, if Cloud Code Projects
112. 3:43is all about multi-agent orchestration
113. 3:45in the cloud, when should we actually
114. 3:47use this and when shouldn't we use this?
115. 3:49Well, starting with the don'ts, if we're
116. 3:50just talking about quick tasks that you
117. 3:52can just knock out in a single chat
118. 3:54session, then obviously no. We don't
119. 3:56need to use cloud code projects for
120. 3:57this. We also need to be wary if we're
121. 3:59talking about work that needs to be done
122. 4:00on our machine. If it's manipulating
123. 4:03files and folders that quite literally
124. 4:04live on our computer, it's not something
125. 4:06that can be in the cloud. It's not
126. 4:07something that can be in a GitHub repo,
127. 4:09then we aren't going to want to use
128. 4:10cloud code projects because this is all
129. 4:12again operating inside of the cloud.
130. 4:14Ideally, it's connected to some sort of
131. 4:16GitHub repo. Now caveat I will say you
132. 4:19do have the ability to spawn sessions
133. 4:22you know that your orchestrator controls
134. 4:23that do live on your local machine but
135. 4:26that isn't what it's really built for.
136. 4:28Also this isn't something that's on team
137. 4:30or enterprise yet. So when we talk about
138. 4:32you know team projects this isn't what
139. 4:35it's really built for either. So what
140. 4:37should we use it for? Well we want to
141. 4:39use it if we have some sort of project
142. 4:40or an area that we're going to continue
143. 4:42to feed. If it's a complicated build
144. 4:44that we can split into different parts.
145. 4:46Think of all these sub sessions
146. 4:47controlled by the orchestrator being in
147. 4:49charge of certain sections of a task.
148. 4:52And Boris Churnney, the guy who actually
149. 4:54created Cloud Code, pretty much said he
150. 4:56stopped managing sessions inside of his
151. 4:58Cloud Code desktop app and really just
152. 5:00uses projects as like this backlog, this
153. 5:02dumping ground of any ideas or tasks
154. 5:04that come into his head. He dumps it
155. 5:05into projects because remember projects
156. 5:08and all of the subsessions beneath it
157. 5:10that the orchestrator controls all share
158. 5:12memory, all share context. So if it's
159. 5:14complicated, it's long running, and is
160. 5:16it something that can work best in a
161. 5:17cloud environment, we're going to want
162. 5:18to use projects. Otherwise, we probably
163. 5:21don't need it. So just keep that in
164. 5:23mind. And lastly, before we jump into
165. 5:24the demo and we actually see projects in
166. 5:26action, what is really the difference
167. 5:28between projects and sub aents? We keep
168. 5:30talking about we have these sub sessions
169. 5:32with context and memory. How is that any
170. 5:34different than just one session with sub
171. 5:36aents being spawned? Well, a lot of it
172. 5:38has to do with persistence. When we
173. 5:41spawn some sort of sub agent in a normal
174. 5:43cloud code session, it's going to do
175. 5:45whatever it's been tasked to do. It's
176. 5:47going to create a summary of all the
177. 5:48work it's done. It's going to send it
178. 5:50back to that main session you're working
179. 5:53in, and it's just going to continue to
180. 5:54fill up the context of that one session.
181. 5:56Versus in a project, that single
182. 5:59session, that orchestrator up top that
183. 6:01we're talking to, these quote unquote
184. 6:04sub aents it's creating. And they're not
185. 6:05really sub agents. They're full sessions
186. 6:08because they have their own context
187. 6:10window. Furthermore, they're persistent.
188. 6:12They'll own their own pull requests. And
189. 6:15because these workers are persistent and
190. 6:17they maintain context throughout, we can
191. 6:19also message them as much as we want. I
192. 6:21can actually go in there and talk to
193. 6:22worker one or worker two as if I'm
194. 6:24talking to the primary orchestrator. So,
195. 6:26there's a lot of things listed here in
196. 6:28terms of the differences. The biggest
197. 6:29ones you need to remember is in terms of
198. 6:31who is managing it. Normally you do all
199. 6:33the management in terms of projects.
200. 6:35Claude is managing it all and dealing
201. 6:37out the work accordingly. Secondly,
202. 6:40persistence projects. Those sub workers
203. 6:42are never shutting off. And so
204. 6:44ultimately sessions with the sub aents
205. 6:45is best when we're just doing one task
206. 6:47at a time. And these projects are great
207. 6:49if we have a stream of work we just
208. 6:50don't want to babysit. So now let's hop
209. 6:52into the demo. If you go into your cloud
210. 6:53desktop on the top left, you will see
211. 6:56something that says projects beta. We
212. 6:58simply click on this and you will see
213. 6:59this page pop up. Now, if you have
214. 7:01projects that have been sitting in
215. 7:02Claude for the past several years,
216. 7:04potentially back from like just the chat
217. 7:06days and they were just projects were
218. 7:08basically just folders, it's going to
219. 7:09ask you, hey, do you want to delete
220. 7:10these or you want to archive all these?
221. 7:12You can just archive all of them till
222. 7:14you get to, you know, essentially a
223. 7:15clean slate. So, we are going to click
224. 7:19new projects.
225. 7:21Then, we're going to give it a name. We
226. 7:22will call this projects demo. You have
227. 7:25the ability to give it a goal. So some
228. 7:27sort of overarching thing it's trying to
229. 7:30achieve. In this case, we will leave it
230. 7:32blank. And I also have the ability to
231. 7:33give it context. So if I already had,
232. 7:36you know, certain documentation
233. 7:38or files and folders that I want this
234. 7:40project to already sort of bring on
235. 7:42board, I can do that here as well. Then
236. 7:44I'm just going to hit create project.
237. 7:45And we're going to get a page that looks
238. 7:47like this. Now the first thing I want
239. 7:49you to do is come up here to the top
240. 7:51where we have this little gear icon. And
241. 7:53we're going to take a look at our
242. 7:54project settings. So again, we can edit
243. 7:57the goal at any point in time. We also
244. 7:59have the models that we can choose from.
245. 8:01And the big things we want to pay
246. 8:03attention to are the coordinator model
247. 8:04and the thread model. So the threads are
248. 8:07essentially the workers that the
249. 8:10coordinator spins up. In reality,
250. 8:13threads themselves can have multiple
251. 8:15workers, but just think of it as like
252. 8:17coordinator and then threads/workers
253. 8:20underneath it. So, the coordinator model
254. 8:22is going to by default go to Opus 5.5 on
255. 8:25a low effort setting. You might be like,
256. 8:26"Hey, do I really want it on a low
257. 8:27effort setting? What do I want to put it
258. 8:28on at least like medium or high if it's
259. 8:30doing all these things?" Well, in
260. 8:31reality, it's not really the one doing
261. 8:32the work. It's just the one coordinating
262. 8:35and diving out the work. So, not really
263. 8:37an issue to keep it on low. If for
264. 8:39whatever reason you feel like it's not
265. 8:40doing a good job of coordinating, you
266. 8:42could always bump this up to medium or
267. 8:43high. But if usage starts to become a
268. 8:47problem because usage is something that
269. 8:49projects can burn up pretty quickly
270. 8:51because we could be you know similar to
271. 8:53dynamic workflows you could have 5 10 15
272. 8:57sessions or threads or workers all doing
273. 8:59stuff at the same time 24/7. So we want
274. 9:02to keep an eye on that thread model opus
275. 9:055.5 on medium should be totally fine for
276. 9:08you. But if you even want to switch this
277. 9:09to something like sauna that works too.
278. 9:11We also have the ability to have it auto
279. 9:12continue when usage limits resets. So
280. 9:14let's say you burn through all 100%.
281. 9:16When the week rolls over and we get a
282. 9:18fresh reset, well, it's just going to
283. 9:19pick up from where it left off. We also
284. 9:22can pause the project, restart Claude or
285. 9:24archive the project from here, too. Then
286. 9:27we have memory. So the big one we want
287. 9:28to pay attention to is project
288. 9:30instructions. This is similar to agents
289. 9:31or claw.md.
290. 9:33This can be very powerful because
291. 9:34they're pretty much going to read this
292. 9:35in every single thread. But, you know, I
293. 9:40wouldn't blow this. Like, similar to how
294. 9:41we approach agents.mmd these days, less
295. 9:44is more. If there's something where
296. 9:45you're like, I really want it to always
297. 9:46do the specific thing in a specific way
298. 9:48every single thread, then maybe this
299. 9:50makes sense to fill it up here.
300. 9:51Otherwise, if you're not sure, just
301. 9:53leave it blank. It also has auto memory,
302. 9:55and that works pretty much the same way
303. 9:56as automemory inside of clawed code. as
304. 9:58you tell it to do things throughout your
305. 10:01sessions, it has its own little scratch
306. 10:02pad where if it thinks it's something it
307. 10:04should remember, it will just
308. 10:05automatically add essentially a little
309. 10:07sticky note to its memory. Next, we have
310. 10:10the environment tab. So, the first thing
311. 10:12we need to do is designate a project
312. 10:14repository. All these workers, all these
313. 10:16sessions are going to be in the cloud
314. 10:17and they need a GitHub repo where they
315. 10:19can communicate and send their PRs. So,
316. 10:22to do that, we just need to select a
317. 10:24particular GitHub repo. Mine is going to
318. 10:26be AI Creator Radar because I'm creating
319. 10:28this thing that goes out on the web,
320. 10:30goes out on Twitter, sees trending AI
321. 10:31news, and then turns that into a
322. 10:33dashboard which says, "Hey, here's
323. 10:34things that haven't been talked about on
324. 10:35YouTube. Here's how we can turn them
325. 10:37into short form. Here's how we turn to
326. 10:38carousels." That type of thing. So, you
327. 10:40can either create this manually inside
328. 10:43of GitHub or just hop into a normal
329. 10:45cloud code session and say, "Can you
330. 10:47create a GitHub repository for me that
331. 10:50I'm going to use inside my project?"
332. 10:52Next, we have the cloud environment. So
333. 10:54if you just keep this as is where it
334. 10:56says select the cloud environment, it's
335. 10:57just going to use the default anthropic
336. 10:59cloud environment, you also have the
337. 11:01ability to add a cloud environment. So I
338. 11:03could give it some sort of name. I can
339. 11:06define the network access everywhere
340. 11:08from none to full. And then I can start
341. 11:09uploading secrets and environmental
342. 11:11variables. So if I am doing something
343. 11:14that requires, you know, API keys and
344. 11:16secrets, I'm going to need to add a
345. 11:19cloud environment for it to be able to
346. 11:20work there. Now, we are going to leave
347. 11:23it on select a cloud environment. And
348. 11:24you will see later it's going to prompt
349. 11:26us to essentially change our cloud
350. 11:27environment to add some keys. And I'll
351. 11:29walk you through that. Next, we have
352. 11:31some local settings. Let cloud use your
353. 11:33device. Yes. Pre-approved folders. If
354. 11:35you have a session or a worker that is
355. 11:37going to need to work on your local
356. 11:39computer or access access it, that's
357. 11:41something we can do. By default, it's
358. 11:43always going to be in the cloud, but it
359. 11:44can actually, you know, go on your
360. 11:46machine. And so to do that, you just
361. 11:47need to select this to yes. And then we
362. 11:50want to give it some sort of folder it
363. 11:51can work in. In this case, I set my
364. 11:53radar-local folder. Then we have a usage
365. 11:55tab followed by debug access. So let's
366. 11:58say you have two projects, project A,
367. 11:59project B totally doing different
368. 12:01things. You can let project B take a
369. 12:03look at project A and vice versa to help
370. 12:05debug because perhaps you're running
371. 12:07into problems where maybe project A
372. 12:10can't debug on its own. Maybe we have
373. 12:11like some issue with the memory. Like
374. 12:13something is poisoning its context.
375. 12:14Well, how about we get a fresh set of
376. 12:16bias to take a look at what's going on.
377. 12:17We can do that by simply giving it
378. 12:20access via the debug access panel.
379. 12:22Probably won't use this a lot, but know
380. 12:23it's there. So, let's go ahead and give
381. 12:25it our prompt. So, we're saying we're
382. 12:28creating the AI creator radar. We've
383. 12:30given it kind of an end state we're
384. 12:31looking for. Again, I want it to be able
385. 12:32to scrape things off of X, and then I
386. 12:34want it to be able to take a look at
387. 12:35YouTube, see what's working, see what
388. 12:37hasn't been touched on, see where
389. 12:39there's some sort of gaps, and I wanted
390. 12:40to do it on a dashboard where I can just
391. 12:42see it all in one place. So, let's go
392. 12:45ahead and put it to work. and see what
393. 12:48happens. And as this is working, you'll
394. 12:50kind of see this has begun to populate
395. 12:51over here are the threads. So
396. 12:53coordinator main page right here, I can
397. 12:55talk to everything and like do
398. 12:57everything from this one window. But if
399. 13:00I want to kind of like click inside of
400. 13:02here and see what's going on at
401. 13:04individual thread or even worker level,
402. 13:06I have that ability too. So after
403. 13:08letting it run for about 25 minutes,
404. 13:09here is where we are at. First of all,
405. 13:12after we gave it the prompt, it split
406. 13:15into five parallel threads, and each
407. 13:17thread was given some piece of the pie
408. 13:19that it needed to execute on. We had
409. 13:21something working on the dashboard and
410. 13:23hosting, one working on the Xcanner, one
411. 13:25on YouTube coverage, one on content
412. 13:27packs, and one on cloud code news. If we
413. 13:29go over here to the right on the
414. 13:31threads, we can see I have two that are
415. 13:32now ready for review. I have three that
416. 13:35have some sort of blocker that require
417. 13:36me to come in and either make some sort
418. 13:38of decision or give it some more
419. 13:39information. And then we also have the
420. 13:42idle thread. Now at any point in time I
421. 13:45can click on any of these threads and
422. 13:47see what this particular worker is doing
423. 13:49at a more granular level. I can click
424. 13:51here and see the blockers. And so it's
425. 13:53really easy me to go really easy for me
426. 13:55to go into each individual session and
427. 13:57actually talk to it because as you see
428. 13:59when I click into here I do have an
429. 14:01ability to steer that thread. I also can
430. 14:03view these threads from the orchestrator
431. 14:05panel right here in the middle. So I
432. 14:07just click view thread and it pops up.
433. 14:10Also I can just handle everything
434. 14:12through here through the orchestrator.
435. 14:14So instead of going into each individual
436. 14:16thread like I would with sessions, you
437. 14:17know, when I'm sort of just normally
438. 14:18operating inside of cloud code, I can
439. 14:20just talk to the single agent and it
440. 14:22will handle it all for me. And the whole
441. 14:24time they're operating inside of my
442. 14:26GitHub repo, which we see right here. If
443. 14:28I hop into the pull requests, we can see
444. 14:30what all these individual threads,
445. 14:32individual workers are actually sending.
446. 14:34So let's handle some of these blockers.
447. 14:36The first one is related to the cloud
448. 14:38environment. Remember I mentioned how
449. 14:39earlier if we need API keys as part of
450. 14:42our project, we need to edit the actual
451. 14:44environment. Well, let's go ahead and do
452. 14:45that. So go up to project settings, go
453. 14:48to environments, and we're going to add
454. 14:51a cloud environment. Going to call this
455. 14:54demo environment. For network access,
456. 14:56we'll throw it to full. And now we need
457. 14:58to add a network secret. And so I put in
458. 15:00all the correct information and then I
459. 15:02just hit add. And now it's working in a
460. 15:04cloud environment that has my particular
461. 15:06secret. So then I can say, hey, I just
462. 15:08updated the cloud environment with the
463. 15:10YouTube key as a network secret.
464. 15:14And the coordinator is going to send
465. 15:16that information to that particular
466. 15:18thread. And now I'm just going to repeat
467. 15:20this process for the rest of the
468. 15:21blockers. And that's kind of how you
469. 15:22would run this. All right. So we got rid
470. 15:24of the blockers and right now it's
471. 15:25finishing up. One thing that's kind of
472. 15:27cool is like I said, you can tell
473. 15:29certain sessions that you want it to be
474. 15:30local. We did that with the session that
475. 15:32had to do with scanning X because X was
476. 15:35actually logged into my account on my
477. 15:37cookies. So it used the inapp browser
478. 15:39inside of cloud code desktop to do that.
479. 15:41And so it actually built a local
480. 15:44scheduled routine. So you can see on
481. 15:46theuler it created this routine. It's
482. 15:49inside of that folder that we designated
483. 15:51earlier is like the local folder it can
484. 15:53play around with. And you can see kind
485. 15:55of the instructions it gave it. And so
486. 15:56here's a look at the dashboard it
487. 15:58created. It shows me which stories are
488. 16:01trending on Twitter but really have no
489. 16:03coverage in the YouTube space. For each
490. 16:06of these, like, hey, Claude writes about
491. 16:0890% of Claude Code's code. It shows me
492. 16:11potential content pack, what the video
493. 16:14could look like, what a short could look
494. 16:15like, what a carousel could look like,
495. 16:18as well as what an X post could also
496. 16:19look like. It also gives me kind of a
497. 16:21breakdown of what's going on with X. So
498. 16:24like the top story right now is DeepSeek
499. 16:26version 4.1 Flash and GLM 5.3 Flash go
500. 16:29free in open code. So it shows me like
501. 16:32the posts per hour, the views. I can
502. 16:34actually click on the posts themselves
503. 16:36and it will bring it up. And it also
504. 16:39gives me more stats about my channel as
505. 16:42well as like some Clawude Code specific
506. 16:45news. Lastly, at the bottom, I can see
507. 16:47kind of a refresh log. And so overall,
508. 16:50this is pretty solid work considering it
509. 16:53was kind of a oneshot and this is just
510. 16:55the first pass that Claude Code Projects
511. 16:58has done on this. And the real cell for
512. 17:00projects at this point isn't the
513. 17:01singular thing it created. It's the fact
514. 17:03that this is now something that is
515. 17:05living in the cloud. I can access it at
516. 17:08any time and I have all of these threads
517. 17:11that still are sharing and maintaining
518. 17:14context. So I can work on this whenever
519. 17:16I want. I can constantly feed it new
520. 17:18information. it can run even when my
521. 17:20computer is shut down and I can continue
522. 17:23to add more and more complexity to it
523. 17:25all through a single orchestrator. So
524. 17:28while I do have the ability to you know
525. 17:30click on individual threads and handle
526. 17:32it one at a time I can just talk to one
527. 17:34agent from any place and have it control
528. 17:37everything. The last thing I'll mention
529. 17:39and I will also link this in the
530. 17:41description is the documentation on
531. 17:43cloud code projects. It is very
532. 17:45extensive. So, if there's anything you
533. 17:48feel like I didn't cover enough or you
534. 17:50want to go deeper and I highly suggest
535. 17:51you take a look at the documentation,
536. 17:53but besides that, that's all I have for
537. 17:56you today. Highly suggest if nothing
538. 17:58else, you hop on that weight list
539. 17:59because you will get access very, very
540. 18:00quick. I think this is a really cool
541. 18:02feature inside of Cloud Code. Kind of
542. 18:04niche, really depends on the type of
543. 18:06projects you're working on. And if
544. 18:08you're someone who really does need that
545. 18:09247 access, if that's not you, no
546. 18:13problem. But if it is, it's great
547. 18:14because you know in the past when we've
548. 18:16had these sort of anthropic cloud
549. 18:18options, they've always been draining
550. 18:20from the API. Now it just comes straight
551. 18:21from usage, which for many of us, I feel
552. 18:24like we have a lot of usage remaining.
553. 18:26Like Opus 5.5 has been pretty token
554. 18:30efficient, especially compared to
555. 18:31something like Fable 5.1. So having the
556. 18:33option to go into the cloud, stay on
557. 18:35usage, and always have complicated
558. 18:37projects running is a great value ad. So
559. 18:41as always, let me know what you thought.
560. 18:42Make sure to check out Chase AI Plus if
561. 18:44you want to get your hands on my cloud
562. 18:45code masterass.