YouTube2Text

This Claude Code Second Brain Manages My ENTIRE Life in Obsidian (100% Private) — Transcript

by Brad Bonanno | AI Automation · 5,038 words · 695 segments · language it · Watch on YouTube

Full transcript

  1. 0:00Hey, I just built the ultimate AI second
  2. 0:02brain with Claude code and it lets me
  3. 0:05organize my brain dumps into ideas,
  4. 0:07people, projects, and tasks. I can even
  5. 0:10delegate any task to my specialized AI
  6. 0:13employees, all running in parallel on my
  7. 0:16laptop. In this video, I'm going to step
  8. 0:18you through how to set one of these up
  9. 0:19for yourself, plus give you the template
  10. 0:22for free. Here's how it works. Capture
  11. 0:24any thought in 5 seconds, whether that's
  12. 0:26a brain dump, meetings, ideas, or
  13. 0:28follow-ups, and Claude Code
  14. 0:30automatically classifies everything,
  15. 0:32creates the right files and links them
  16. 0:35together. The best part of all of this
  17. 0:36is that it's happening in Obsidian, so
  18. 0:38you can view your notes easily in a
  19. 0:40beautiful UI, plus sync them to all of
  20. 0:43your devices. Every morning, Claude
  21. 0:45scans what's due, what's overdue, and
  22. 0:47what projects need attention. It then
  23. 0:49creates you a daily brief ready to
  24. 0:51action. But it's not just an AI to-do
  25. 0:54list. You can actually delegate any task
  26. 0:57to your specialized AI employee. They're
  27. 1:00trained to handle the work for you, and
  28. 1:01they even check off their tasks when
  29. 1:03they're done and link to the files they
  30. 1:05create. This isn't just sub agents that
  31. 1:07block you from working, either. We're
  32. 1:09creating completely separate instances
  33. 1:12of Claude code to do content research,
  34. 1:14writing, spreadsheets, PDFs, or create
  35. 1:17PowerPoints. All of these running in
  36. 1:19parallel while you keep working on other
  37. 1:22tasks. Your AI employee even dings you
  38. 1:25when they're done. Plus, because
  39. 1:26everything is being tracked in Git,
  40. 1:28every single action that Claude takes is
  41. 1:30automatically logged with notes. Full
  42. 1:33audit trail near perfect recall. You can
  43. 1:35time travel on your entire work history,
  44. 1:38and Claude can see exactly what happened
  45. 1:40and when. And if you're scared of the
  46. 1:42terminal, Anthropic has just dropped a
  47. 1:44native VS Code extension that gives you
  48. 1:47all the power of Claude Code without
  49. 1:49ever touching the command line. It's the
  50. 1:51same agentic capabilities just wrapped
  51. 1:53in a nicer GUI. So whether you're a
  52. 1:56terminal warrior or prefer clicking
  53. 1:57buttons, I've got you covered in this
  54. 1:59video. Like always, I'm giving this away
  55. 2:01for free. No sign up, no wait list, just
  56. 2:04clone the repo and go. If you don't know
  57. 2:06me, my name is Brad. I've been building
  58. 2:08with AI for over 5 years now. I started
  59. 2:10in big tech where I built thousands of
  60. 2:13AI automations for massive companies.
  61. 2:15Now I help businesses build AI systems
  62. 2:18exactly like this one so they can out
  63. 2:20compete with AI. If that's you, links
  64. 2:22are in the description. Before we jump
  65. 2:24into the setup, I want to explain how
  66. 2:26the ultimate AI second brain is
  67. 2:28structured. The centerpiece is the
  68. 2:29second brain itself, a git tracked
  69. 2:31Obsidian vault which stores all of my
  70. 2:33thoughts as markdown files. Each of
  71. 2:35these files is organized into either
  72. 2:37ideas, people, projects, or tasks, and
  73. 2:40they all have a due date. Each one of
  74. 2:42these is also accessible inside of
  75. 2:44Obsidian, so I can easily navigate and
  76. 2:47search, plus add any tasks and make
  77. 2:49edits. Sitting on top of the second
  78. 2:51brain is my Claude code chief of staff.
  79. 2:54Basically, this chief of staff can run
  80. 2:56your entire work life. You brain dump
  81. 2:58into Claude and it creates, identifies,
  82. 3:00and decomposes your brain dump into the
  83. 3:02base level node structure. For example,
  84. 3:04if I write meeting with John to discuss
  85. 3:06an AI agent project, it becomes a new
  86. 3:09task to meet with John, a new person
  87. 3:12record for John, and a new project for
  88. 3:14the AI agent project. All of these are
  89. 3:16linked together. Think of it like an AI
  90. 3:18operating system for your knowledge
  91. 3:19work. Tasks, projects, people, ideas,
  92. 3:23all tracked in Markdown files that
  93. 3:25Claude can read, write, and reason
  94. 3:27about. Plus, you have the option of
  95. 3:29interacting with them all in Obsidian.
  96. 3:31Sitting adjacent to the chief of staff
  97. 3:32and second brain are the specialized AI
  98. 3:35co-workers. These are different claude
  99. 3:37code repositories or folders with
  100. 3:39specialist skills and workflows. For
  101. 3:41example, we have our head of content AI
  102. 3:43employee which can find the best winning
  103. 3:45content ideas. We built this one last
  104. 3:47week and if you haven't seen that video,
  105. 3:49please check out the link above. Our AI
  106. 3:51chief of staff can delegate any task
  107. 3:53from our second brain to an AI co-orker.
  108. 3:56These tasks run in parallel and
  109. 3:58completely unsupervised. Once they're
  110. 4:00done, they update the original task.
  111. 4:02This isn't just another productivity
  112. 4:04tool. This is a framework for building
  113. 4:06AI employees that actually do work. And
  114. 4:08the second brain plus chief of staff is
  115. 4:11the command center that sits above your
  116. 4:13other AI employees. All right, so here's
  117. 4:16how your second brain actually works.
  118. 4:18There are a few really key directories
  119. 4:20within our second brain folder. We have
  120. 4:23the ideas, the people, the projects, and
  121. 4:25tasks. These are where we're storing all
  122. 4:28of our different pieces of information
  123. 4:29that we ingest into the second brain. We
  124. 4:32also have some other folders in here as
  125. 4:33well. The context folder, the daily
  126. 4:35folder, and the outputs folder. I'll
  127. 4:37start with the context folder. The
  128. 4:39context folder is where you create all
  129. 4:41of the different markdown files that
  130. 4:42make this second brain your own. You can
  131. 4:45add in a writing style, a business
  132. 4:47profile, anything that's going to help
  133. 4:48you make Claude understand you even
  134. 4:51better. I already have a tweet style
  135. 4:52saved in here. It just says I like short
  136. 4:54tweets. So it can be as complex and
  137. 4:57detailed as you like and obviously the
  138. 4:59more context that you can give Claude
  139. 5:01code the better the results you're going
  140. 5:02to get. So outside of the context folder
  141. 5:04we have the outputs folder. So whenever
  142. 5:06I delegate a task to one of my AI
  143. 5:09employees or I use or I delegate a task
  144. 5:13within this particular repo and it has
  145. 5:15to do research, create a file, anything
  146. 5:17like that that's saved in the outputs
  147. 5:19folder. But each of these will be linked
  148. 5:21back to the original task. So every time
  149. 5:23I run a /to today command and it has to
  150. 5:25come up with a a daily plan for me, it
  151. 5:28will save that daily plan here. So
  152. 5:30that's separate from a task or anything
  153. 5:31like that. And that lets me work through
  154. 5:33this uh as my day goes on. So outside of
  155. 5:36those folders, we have a claude folder
  156. 5:38and aobsidian folder. So the important
  157. 5:40thing to remember is that this second
  158. 5:41brain is also an obsidian vault. So
  159. 5:44that's why we have theobsidian folder,
  160. 5:46which means we can actually go in and
  161. 5:47read all of these markdown files super
  162. 5:50easily inside of Obsidian. and it makes
  163. 5:52it a pleasure to work with. So I have
  164. 5:54the record here for Bruce Rain in the
  165. 5:56people folder. He's a CEO of Wayne
  166. 5:58Enterprises. Obviously much nicer to
  167. 6:00look at then would be looking at this
  168. 6:02inside of VS Code or cursor. So I guess
  169. 6:04I should give you the definition of what
  170. 6:05a task versus project versus an idea
  171. 6:08versus a person is. Obviously person is
  172. 6:10pretty self-explanatory. Any
  173. 6:11relationship that comes up as part of a
  174. 6:13brain dump that you put into cord will
  175. 6:15be saved there. A task is anything with
  176. 6:17a defined end date. So, I need to create
  177. 6:20an email for so and so or I need to uh
  178. 6:23write some copy for the marketing
  179. 6:25campaign, something like that. A project
  180. 6:27is a larger piece of work that's made up
  181. 6:29of tasks. So, typically a project uh
  182. 6:32file will be linked to several tasks and
  183. 6:34may even be linked to some people. Ideas
  184. 6:36are captured thoughts. They can be
  185. 6:37anything. Maybe it's a a content idea,
  186. 6:40maybe it's a new million-doll business
  187. 6:42idea that you've that you've come up
  188. 6:44with. Anything like that will be saved
  189. 6:46here. So, one of the example ones I have
  190. 6:49here is a prompt library for SAS. So,
  191. 6:51every single one of the files, no matter
  192. 6:53which folder they're saved in, whether
  193. 6:55that's an idea, people, project, task,
  194. 6:56or output, has a YAML header. So, we can
  195. 7:00see the type, the tags, the created
  196. 7:02date. And then for tasks, we can also
  197. 7:04see the due date, which is really
  198. 7:07important. All tasks need to have a due
  199. 7:09date, which helps because Claude is
  200. 7:10using looking for that due date whenever
  201. 7:12it's running the today command. There's
  202. 7:14also let's call it filter. So we can
  203. 7:16filter based on the tags, based on
  204. 7:17created date, whether it's overdue or
  205. 7:19not. So that's all of the data that
  206. 7:21makes the second brain the second brain.
  207. 7:23Now I want to talk about what makes the
  208. 7:25chief of staff agent or the clawed code
  209. 7:27that's running on this particular repo.
  210. 7:30Inside the claude directory, we have our
  211. 7:32hooks and our skills. Pretty
  212. 7:33self-explanatory if you've worked with
  213. 7:34CLA code before. Inside the skill
  214. 7:37directory, we have all of the skills
  215. 7:38that are making our chief of staff
  216. 7:40actually useful when running over the
  217. 7:42second brain. and I'll run you through
  218. 7:43what each of these does now. So, the
  219. 7:46first one I'm going to show you is the
  220. 7:47new command. The new command is probably
  221. 7:49the one you're going to use the most.
  222. 7:51Anytime you want to add something into
  223. 7:52the second brain or write down a
  224. 7:54thought, whether it's a new project,
  225. 7:56emails, ideas, whatever, you can use the
  226. 7:58new command. It's really, really
  227. 7:59variable. So, I'll just type / new and
  228. 8:02then I can write any thought. So, I want
  229. 8:05to create a library for Claude skills.
  230. 8:12Once I use that command, Claude then
  231. 8:14starts to pick the command apart or
  232. 8:16decompose it and create the relative
  233. 8:18tasks. This one is super simple. It's
  234. 8:20just one simple task. So, uh, when is
  235. 8:22this due? Let's say no due date. It's
  236. 8:25pretty open-ended. So, once I've
  237. 8:26selected that, Claude will create the
  238. 8:28task within the vault. So, we have it
  239. 8:31right here. We have the type task, and I
  240. 8:33can even click here and view it on the
  241. 8:34right hand side. If I wanted to go add
  242. 8:36some additional content or brain dump
  243. 8:38some more into Claude, it could update
  244. 8:40that task for me. But that's a really
  245. 8:42simple task. I want to show you exactly
  246. 8:44how powerful this new command is. If I
  247. 8:47do / new, I have a meeting with John
  248. 8:52Clemens about his new AI agent for
  249. 8:56customer support. I need to prepare an
  250. 8:59evaluation of the different vendors
  251. 9:02beforehand. So, this is a complex task.
  252. 9:04It's made up of several different
  253. 9:05components. We have a person in John
  254. 9:07Clemens. We have a a project in the AI
  255. 9:10agent for customer support. And I have a
  256. 9:12task in I need to prepare an evaluation
  257. 9:14of the different vendors beforehand. So
  258. 9:16I'll click enter. And then Claude will
  259. 9:18go to work in decomposing that brain
  260. 9:20dump into the specific subcomponents.
  261. 9:24So looks like it's mclassified one of
  262. 9:26those, but that's okay. I'm going to say
  263. 9:28this is due tomorrow.
  264. 9:30So the person it's picked that out
  265. 9:32correctly. It's created a task for the
  266. 9:35meeting with John Clemens the AI agent
  267. 9:37and it also has another task for prepare
  268. 9:39vendor evaluation. So I guess it wasn't
  269. 9:41that incorrect. So I probably would have
  270. 9:44created a project as well but obviously
  271. 9:45you can go and improve this as much as
  272. 9:47you want. Now I have these three
  273. 9:49different files here. I can go and click
  274. 9:51to John Clemens and I can click to the
  275. 9:53to the meeting here. So this chief of
  276. 9:55staff is trained with how Obsidian uh
  277. 9:58expects links within MD file. I have the
  278. 10:00person record for John Clemens linked to
  279. 10:02the task and also the other task to
  280. 10:05prepare a vendor evaluation for the AI
  281. 10:07agent. So if I go into Obsidian here and
  282. 10:10I search for meeting with John Clemens,
  283. 10:15I can see it right here. I can see that
  284. 10:16it's links to John Clemens here. Uh and
  285. 10:19then it also links to the other
  286. 10:21subtasks. So prepare evaluation of
  287. 10:23different AI agent vendors for customer
  288. 10:25support. So that's how the new skill
  289. 10:27works. It's super powerful and is how
  290. 10:30you can brain dump pretty much anything
  291. 10:32into your AI second brain without having
  292. 10:34to worry about organizing any of these
  293. 10:36MD files. Cord will just handle that for
  294. 10:38you. So that's the new skill. When you
  295. 10:40want to start your day in the morning
  296. 10:41and you want to see exactly what's in
  297. 10:42your second brain and what you need to
  298. 10:44action, the prioritized list of what you
  299. 10:46need to be working on right this moment,
  300. 10:48that's when you use the today skill. So
  301. 10:50I go slash today and that will tell
  302. 10:52Claude to go through all of my tasks and
  303. 10:55that are due today or in the next couple
  304. 10:57of days and rank them based on their
  305. 10:59importance and then give me a daily
  306. 11:01brief of tasks that I need to action
  307. 11:03right now. So you can see Claude's going
  308. 11:05through and reading all of the different
  309. 11:07tasks that I have that are due in the
  310. 11:08next couple of days or overdue. It
  311. 11:10prioritizes overdue tasks, so things
  312. 11:12that I've missed from the last previous
  313. 11:14days, and then it will list out today's
  314. 11:16tasks and then any tasks that are due in
  315. 11:18the future. So you can see it's reading
  316. 11:19a lot of information because I have a
  317. 11:22lot of data that I've put into the
  318. 11:23second brain for things that I need to
  319. 11:25start looking at. So I'd already run
  320. 11:26slash today. So it's already found my
  321. 11:30today brief and just made some updates
  322. 11:31based on some new tasks that I've added
  323. 11:33since I ran it earlier. Now it's given
  324. 11:35me a summary of that brief. But I
  325. 11:37actually want to go in and read the
  326. 11:38brief in full. So I'll open Obsidian up.
  327. 11:40I'll go to my files and then I can go to
  328. 11:41my daily tab. And I can see that I have
  329. 11:44my today briefing from today. So I can
  330. 11:46go see all the tasks that are due. So I
  331. 11:48need to write a proposal for document
  332. 11:50processing. I need to prepare a vendor
  333. 11:52evaluation for AI agents which is the
  334. 11:54task we just created. Write an X thread
  335. 11:56on Claude skills. Research AI automation
  336. 11:58YouTube trends and some YouTube other
  337. 12:01YouTube content. I also have a few
  338. 12:02overdue tasks which I haven't gotten to.
  339. 12:04An invoice creating a SAR workshop and a
  340. 12:07one-on-one with Marcus. It's also
  341. 12:09linking all of my active projects that I
  342. 12:11have at the moment and any recent
  343. 12:13activity in this repo. It's also telling
  344. 12:15me what I've completed as well. So I've
  345. 12:17completed some research about make
  346. 12:19versus naden and some AI automation
  347. 12:21questions from core and Reddit. So
  348. 12:23that's my plan for today and then I
  349. 12:25would go through and execute on these. I
  350. 12:27can either go and check these off
  351. 12:28individually or the most powerful part
  352. 12:30of this repo is I can delegate some of
  353. 12:32these. So I want to actually delegate
  354. 12:34this uh X thread for chord skills. What
  355. 12:38I'm going to do is show you how the
  356. 12:39delegate skill works. Now, before I get
  357. 12:41into that, I want to shout out to Indie
  358. 12:42Devdan, who is the original creator of
  359. 12:45the script for the delegate task. He
  360. 12:48made a really great video on how to fork
  361. 12:50terminals uh in chord code and created a
  362. 12:53great skill which I've adapted for this
  363. 12:55workflow. So, if you're not already
  364. 12:56subscribed to Indie Devdan, go check him
  365. 12:58out. I'll leave a link to that video in
  366. 13:00the description below. So, I want to
  367. 13:01delegate some of those tasks. I'm going
  368. 13:03to type in /delegate and then I'll paste
  369. 13:05in that task. So, right X thread for
  370. 13:09cord skills. Uh, and to the head of
  371. 13:13content. Now, if you haven't seen my
  372. 13:14video on the head of content that came
  373. 13:16out last week and it's a really great
  374. 13:18watch. So, I'll link it up here so you
  375. 13:19can go have a look. But what the head of
  376. 13:21content is is a specialized AI co-worker
  377. 13:24that has a bunch of workflows and
  378. 13:26scripts related to content research. So
  379. 13:29by delegating this to the head of
  380. 13:31content, it's going to open up a new
  381. 13:33terminal on my machine, not just use a
  382. 13:35sub agent. This means that I don't have
  383. 13:37to stop working because it's opened a
  384. 13:39new ver a new instance of claude code. I
  385. 13:42can continue to delegate other tasks or
  386. 13:44I can go on my phone or I can go create
  387. 13:47write some emails, any of that. That's
  388. 13:48an old one over here. So I'm just going
  389. 13:49to terminate that. But you can see that
  390. 13:51it's opened a new terminal. Uh it's
  391. 13:54given the prompt for what I need it to
  392. 13:56do based on the task. It has the
  393. 13:58directory where that task is saved and
  394. 14:00it's also been instructed to update that
  395. 14:02task once it's completed. So I'll leave
  396. 14:05that in the background now and it'll
  397. 14:07ding us when it's done. So I want to go
  398. 14:09back up here and I want to actually take
  399. 14:11advantage of that delegate skill even
  400. 14:12more and delegate some more. So I'm
  401. 14:14going to ask it to prepare that intake
  402. 14:16proposal. So I'm going to delegate that
  403. 14:18task
  404. 14:21and that ding. That was the agent
  405. 14:23finishing in the background there. So
  406. 14:24I'm going to delegate this prepare
  407. 14:25intake proposal task. I'm not going to
  408. 14:27use an AI coworker here because my chief
  409. 14:29of staff agent can handle this. I just
  410. 14:31don't want it to run in this terminal.
  411. 14:32So, I can see that it's finished uh the
  412. 14:35clawed code thread and it's saved that
  413. 14:38to the outputs here. Uh so, I am going
  414. 14:41to go take a look at that in Obsidian.
  415. 14:44I'll just actually let it run this other
  416. 14:46command here. So in the outputs I can
  417. 14:48see that here's that X thread for Claude
  418. 14:51skills
  419. 14:52and it's given me the first tweet the
  420. 14:55hook what are skills and a bit of a a
  421. 14:57bit of a breakdown here of of the thread
  422. 14:59that I could run. So you'll also find
  423. 15:01that when I search for that other skill
  424. 15:04X thread for chord uh for claude skills.
  425. 15:07So I go back to my daily uh brief and
  426. 15:09then I click on that thread, it's been
  427. 15:11marked as completed because I delegated
  428. 15:12that task to Claude code in the
  429. 15:15background. And then it's also linked to
  430. 15:17the actual output thread here. So that's
  431. 15:19really great and working as we want it
  432. 15:22to. While we've been talking, I actually
  433. 15:24delegated another task to uh a different
  434. 15:27version of claude code which is open in
  435. 15:28another terminal here. It's going to
  436. 15:30really struggle to write this proposal
  437. 15:31for any tech because I have absolutely
  438. 15:34zero context within this folder around
  439. 15:37it. But if I had taken the time to go
  440. 15:38and fill in this context folder with
  441. 15:40details around the project or had given
  442. 15:43it some more instructions as to where it
  443. 15:44could find that context, then it would
  444. 15:45go and write that proposal. But we're
  445. 15:48going to leave that in the background to
  446. 15:49keep running. And it's just finished. So
  447. 15:51every time one of these tasks finish in
  448. 15:53the background, it plays a sound so we
  449. 15:56know to go check that it's completed. So
  450. 15:58I can see that it's created a proposal.
  451. 16:01We'll see what it says because to be
  452. 16:02honest, it had nothing to go on. So it
  453. 16:04might be quite funny. So, in my output
  454. 16:07folder here, I have my in inite techch
  455. 16:09proposal. So, apparently they process
  456. 16:11over 10,000 invoices monthly. It's
  457. 16:13giving me the current state, some
  458. 16:14business impact, uh, vision model
  459. 16:17architecture, and a couple of different
  460. 16:18prices. Sounds like this is going to be
  461. 16:20a really expensive proposal for initech.
  462. 16:22So, that's great. So, that's the power
  463. 16:25of the second brain and delegate skill
  464. 16:27together. As you can see, the sky is
  465. 16:29really the limit here as far as what you
  466. 16:30can do with it. You can run as many
  467. 16:32claude code instances on your computer
  468. 16:34as your plan will allow and as your
  469. 16:36computer has memory. So we're not
  470. 16:39limited here by running sub agents in
  471. 16:41one claude. We can run as many tasks at
  472. 16:43the same time as possible. The other
  473. 16:44thing that we can do here and we saw
  474. 16:46with the head of content skill is
  475. 16:47delegate to AI employees. So we have an
  476. 16:50AI employee for head of for content
  477. 16:53research at the moment. But we can very
  478. 16:55easily go and build an AI employee for
  479. 16:57sales, for marketing, for customer
  480. 17:01support, for customer success. Any of
  481. 17:03those different verticals will have
  482. 17:04specific workflows and scripts that we
  483. 17:06can develop to help those AI employees
  484. 17:09do their job even better. But even
  485. 17:11without those AI employees, Claude's
  486. 17:13delegating it to just another instance
  487. 17:15of Claude is still does a pretty good
  488. 17:16job. There's one last thing that makes
  489. 17:18this chief of staff the ultimate AI
  490. 17:20second brain and that is the hooks that
  491. 17:23we've built in. So claude hooks are
  492. 17:25deterministic workflows that always
  493. 17:27happen when Claude does something. In
  494. 17:28the settings.json file, we have the two
  495. 17:30hooks that I've preconfigured for this
  496. 17:32repo and they're really really cool. So
  497. 17:34the first one is an auto commit hook and
  498. 17:36that runs after anytime Claude updates a
  499. 17:39file or creates a file within the repo.
  500. 17:41Whenever I use the new skill or the
  501. 17:43today's skill or delegate a task, the
  502. 17:46auto commit hook will run. That runs a a
  503. 17:49script that we have set up in the hooks
  504. 17:50folder. I'm not going to go through that
  505. 17:51now, but if you want to, it's there. The
  506. 17:53other hook that we have set up is a
  507. 17:55command for it to play a stop sound
  508. 17:57whenever Claude finishes its run. So, we
  509. 17:59obviously don't want the chief of staff
  510. 18:01to play a sound every single time we do
  511. 18:03something cuz that would be super
  512. 18:04annoying. So, what we've done is set an
  513. 18:06environment variable every time we're
  514. 18:09opening up a new claude instance. And
  515. 18:11that hook is listening for that
  516. 18:13environment variable to be set to one.
  517. 18:15When that's set to one, it'll play a
  518. 18:17little chime sound so we know that
  519. 18:18chord's finished doing that work. I need
  520. 18:20to zoom in on that git part because it's
  521. 18:22one of the most powerful parts of this
  522. 18:24second brain. Git isn't just for code.
  523. 18:27It's the world's best audit system when
  524. 18:29it comes to AI workflows. If AI can know
  525. 18:32exactly what changes were made and when
  526. 18:34they were made and by who ma and who
  527. 18:36made them, it's able to reverse engineer
  528. 18:39any mistakes that happened down the
  529. 18:40track. It's really, really powerful. I
  530. 18:42want to show you how easy it is to use
  531. 18:44your chief of staff to see what has
  532. 18:46happened with your tasks in the last
  533. 18:48couple of days. So, check the git log to
  534. 18:51see what updates I've made in the past 7
  535. 18:57days. So, this repo has only been around
  536. 18:58for three, so we won't have seven days
  537. 19:00worth, but we'll see. So, you can see
  538. 19:02every single commit or every single
  539. 19:04change that h has happened since this
  540. 19:06repo has been initialized. 27 commits on
  541. 19:09the first day, 44 on the second, and 22
  542. 19:12today. We have all of the different
  543. 19:14changes that have been made, every task
  544. 19:16that I've created, every task that I've
  545. 19:18marked as completed, every output file,
  546. 19:20everything is stored in Git. This is the
  547. 19:22real superpower of this second brain
  548. 19:24because a system that you might set up
  549. 19:26in notion or confluence with Zapia
  550. 19:28doesn't have this ability. You can't
  551. 19:30tell what has changed within your second
  552. 19:32brain over 1 day, 2 days, 7 days since
  553. 19:35it's begun. Git gives you a complete
  554. 19:37history of every change that has
  555. 19:39happened in this repo. It gives you
  556. 19:40total flexibility and the ability to
  557. 19:42revert any change at any time. You can
  558. 19:45compare two points in time to see
  559. 19:47exactly what it's what's changed. you
  560. 19:49can branch out and and experiment on one
  561. 19:51path and then revert back to the other.
  562. 19:53It really is a superpower and blows away
  563. 19:56notion or confluence or just obsidian by
  564. 19:58itself. I want to pause for a second
  565. 19:59because this AI system can literally 10x
  566. 20:02the amount of work that you get done if
  567. 20:04you use it correctly. But this is really
  568. 20:05just the foundation. We've proved the
  569. 20:07concept with the head of content plugged
  570. 20:09into the second brain with the chief of
  571. 20:11staff. What comes next is more AI
  572. 20:13employees. Like what if you had a head
  573. 20:14of research that monitored competitors
  574. 20:16daily? a head of marketing that drafted
  575. 20:18content based on your playbooks, a head
  576. 20:20of ops that manage your calendar and
  577. 20:22email. Each one of these lives in its
  578. 20:24own repo or folder with its own
  579. 20:25specialized skills. The chief of staff
  580. 20:28orchestrates all of them. You end up
  581. 20:30with a full AI workforce, all spawning
  582. 20:32from one place, all tracked in Git and
  583. 20:35all without another expensive
  584. 20:37subscription that you weren't already
  585. 20:38paying for. This is what I mean when I
  586. 20:40say we're building AI employees, not AI
  587. 20:43tools. If you want to see me build out
  588. 20:45more employees, head of research, head
  589. 20:47of writing, head of whatever, hit the
  590. 20:49subscribe button. This repo is just the
  591. 20:51start. So, if you want to get started
  592. 20:52with your second brain, here's exactly
  593. 20:54how to do that. Clone the repository
  594. 20:56from the link in the description below
  595. 20:58to your local machine. Whether you're
  596. 20:59using git to do that or whether you're
  597. 21:01just downloading the zip files, it
  598. 21:02doesn't matter. But what you need to do
  599. 21:04is get that repository open in an ID
  600. 21:06like VS Code or cursor. Once you do have
  601. 21:08that open, create a new terminal and go
  602. 21:10to claude code. Now, I've made it super
  603. 21:13super easy to get started with this. All
  604. 21:15you need to do is go /st start second
  605. 21:17brain. This will create all of the
  606. 21:20folders that we need and it will start
  607. 21:21the git tracking so that we have that
  608. 21:23audit log for all of the second brain uh
  609. 21:26tasks, ideas, and projects that we
  610. 21:28create. So, I'm just going to say yes.
  611. 21:30So, it's gone ahead and created all of
  612. 21:33the folders that we need here. And now
  613. 21:35it's going to initialize git.
  614. 21:39Great. So we have everything we need to
  615. 21:41get started with the second brain. Now
  616. 21:43that's literally it. We can do a few
  617. 21:46things to really increase the power of
  618. 21:48our second brain. So in the docord
  619. 21:50folder there is a few different
  620. 21:52reference files. So you want to go to
  621. 21:54doclord references and then
  622. 21:55employees.json. If you have any other
  623. 21:58employee directory set up on your
  624. 21:59machine, whether that's the head of
  625. 22:00content that we created last week or a
  626. 22:03different AI repo that you want to save
  627. 22:05here, you can do so. So you can just
  628. 22:07either edit this here. You can edit the
  629. 22:10head of content example or you can
  630. 22:12create another one. So this is just
  631. 22:13JSON. So if you want to add another one,
  632. 22:15you would just go down here and create a
  633. 22:18new line.
  634. 22:20So what you want to put here is the
  635. 22:22relative path to where that repo is from
  636. 22:24this repo. So for my example, I have
  637. 22:27both the head of content and my second
  638. 22:29brain repos in the same folder, GitHub.
  639. 22:32So if you have a similar setup, you
  640. 22:34would do uh something very similar to
  641. 22:36that. But if you do have problems or
  642. 22:37need help trying to find exactly what
  643. 22:39you need to put there, just ask Claude.
  644. 22:41So once you have your employees.json set
  645. 22:43up, the other thing that you want to set
  646. 22:44up is your context folder. So inside of
  647. 22:47your context folder, you can add as many
  648. 22:50markdown files as you want. Whether that
  649. 22:52is your company profile, some branding
  650. 22:54guidelines, whatever. The more context
  651. 22:56you can add here, the better the better
  652. 22:58outputs you'll get from your chief of
  653. 23:00staff and second brain. So that's it.
  654. 23:02Once you have the repo initialized using
  655. 23:05the start second brain command and you
  656. 23:08have added in your settings and content
  657. 23:10that's all you need to get started. If
  658. 23:12you want to use the second brain inside
  659. 23:14of Obsidian, what you need to do is
  660. 23:16first go download Obsidian and there'll
  661. 23:17be a link in the description below if
  662. 23:18you don't have that already. It's free.
  663. 23:20So I'm going to open Obsidian on my
  664. 23:22machine. So once you've got Obsidian
  665. 23:23opened up on your machine, you want to
  666. 23:25go to the open folder as a vault and
  667. 23:28find the folder that you've saved your
  668. 23:30Second Brain in. So I've got second
  669. 23:31brain here and I'll press open. Now I
  670. 23:34have all of the files open in Obsidian
  671. 23:36and any markdowns we markdown files or
  672. 23:38tasks we create will be available here
  673. 23:40as well. So that's it. Once you have the
  674. 23:42repo cloned, you've got it open in
  675. 23:43Obsidian, that's all you need to do. Uh
  676. 23:45there are also detailed instructions in
  677. 23:47the readme of the repo linked in the
  678. 23:49description below. Yeah, that's it. Or
  679. 23:51you can now just go start new and
  680. 23:53whatever's on your mind, projects,
  681. 23:55ideas, tasks, anything. So second brains
  682. 23:58are innately personal. So, I want you to
  683. 24:00try mine. Obviously, you're going to
  684. 24:01want to make some changes to make it fit
  685. 24:03you perfectly, but I'm really excited to
  686. 24:06see where you guys go with it and to see
  687. 24:07what you guys create. If you found this
  688. 24:09video useful, do me a favor, hit like
  689. 24:11and subscribe. I'm planning a lot more
  690. 24:13content around Claude Code, AI
  691. 24:15employees, more co-worker directories,
  692. 24:17more skills. If you want to see specific
  693. 24:20capabilities or employees, drop a
  694. 24:22comment telling me exactly what you want
  695. 24:24to see next. Thanks for watching.

About this transcript

This page contains the full transcript of This Claude Code Second Brain Manages My ENTIRE Life in Obsidian (100% Private) by Brad Bonanno | AI Automation, generated from the public captions YouTube serves with the video. The transcript has 5,038 words across 695 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.