YouTube2Text

Obsidian + AI 终极方案:Codex/ClaudeCode + VS Code + claudian + Obsidian CLI — Transcript

by 明立非 · Mingnify | Indie Maker · 4,294 words · 581 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Many people say
  2. 0:01Obsidian is the preferred knowledge management tool in the AI era
  3. 0:04Because it essentially relies on local Markdown files
  4. 0:08The content is naturally easier for AI to read and process
  5. 0:11And precisely because of this
  6. 0:12Obsidian + AI becomes very important:
  7. 0:14It doesn't just help you chat
  8. 0:16But helps you organize, restructure, and automate your knowledge base
  9. 0:19But the problem is
  10. 0:19There are many ways to integrate AI into Obsidian
  11. 0:22Plugins, IDEs, CLIs, MCP... they all seem usable
  12. 0:26But it also feels overwhelming to start
  13. 0:28So
  14. 0:29In this video, I will first help you sort out all mainstream solutions
  15. 0:33And at the end
  16. 0:34Give you what I consider the best Obsidian + AI workflow for long-term use
  17. 0:40Codex/ Claude Code+ Claudian + VS Code + Obsidian CLI
  18. 0:46This solution
  19. 0:47Balances experience, efficiency, cost, and automation capabilities
  20. 0:53There are many ways to integrate AI into Obsidian
  21. 0:56But don't rush to memorize tool names
  22. 0:58What's really important is not "which tool you use,"
  23. 1:01But at what level these tools operate
  24. 1:04If we don't categorize them first
  25. 1:05Plugins, IDEs, CLIs, Agents
  26. 1:08All these terms will make your head spin
  27. 1:11So before we dive into specific methods
  28. 1:14Let's grasp two core questions:
  29. 1:16First
  30. 1:17Who is driving whom—is AI actively operating Obsidian
  31. 1:21Or is Obsidian opening its capabilities for AI to call?
  32. 1:24Second
  33. 1:25Which layer is being operated—is it directly the file layer
  34. 1:28Or completing actions inside Obsidian
  35. 1:31Once these two dimensions are determined
  36. 1:33All subsequent methods will be clearer
  37. 1:35Based on these two dimensions
  38. 1:36We can map Obsidian AI integration solutions into a four-quadrant chart
  39. 1:41This way
  40. 1:42The responsibilities, boundaries, and use cases of each method
  41. 1:45Will be clear at a glance
  42. 1:47Quadrant 1
  43. 1:48Is AI actively working within the Obsidian layer
  44. 1:51Which means regular AI plugins
  45. 1:53Like the Copilot type
  46. 1:56They usually revolve around the current note, selection
  47. 1:59Or whole-vault indexing
  48. 2:00For Q&A, summarizing, rewriting, and lightweight RAG
  49. 2:05Its advantage is great immersion
  50. 2:07Closest to the native Obsidian workflow
  51. 2:10Suitable for having AI add a sentence, revise a paragraph, or explain a concept while writing
  52. 2:16But its limitations are also obvious: low privileges
  53. 2:19Not suitable for structural tasks like batch renaming, moving files, or restructuring directories;
  54. 2:24And these plugins mostly require configuring API keys separately
  55. 2:28Constantly consuming tokens
  56. 2:29Some features even require extra payment
  57. 2:32So this method is suitable for daily writing, single-page processing, and lightweight Q&A
  58. 2:37If your goal is just to make Obsidian better for writing and asking
  59. 2:41It's sufficient;
  60. 2:42But if you want AI to truly restructure your knowledge base
  61. 2:45And better reuse your AI subscriptions
  62. 2:47It won't be enough
  63. 2:49I am currently not using this method
  64. 2:51So I won't go into detail later
  65. 2:53Quadrant 2
  66. 2:55Is AI IDEs (including code editors) actively operating on the file layer
  67. 2:58That is, using AI IDEs like VS Code, Cursor, or Trae
  68. 3:02To open the Obsidian vault directly
  69. 3:04Treating the entire knowledge base as a project
  70. 3:08At this time, the objects AI operates on
  71. 3:09Are mainly Markdown files, YAML metadata, and folder structures
  72. 3:13Rather than the views and interfaces inside Obsidian
  73. 3:16Its advantage is very strong file-layer control
  74. 3:19Especially suitable for cross-file batch organization, unified naming, tag cleaning, generating index pages
  75. 3:25Or even restructuring the entire directory
  76. 3:27But it is further away from the native Obsidian ecosystem
  77. 3:31Its awareness of backlinks, views, and plugin states is less direct;
  78. 3:35If the changes are too radical
  79. 3:37It may bring risks like broken links, directory mess, and altered references
  80. 3:43So this category is better for deep editing, batch cleaning, new vault setup, and directory restructuring
  81. 3:48It's like an external engineering team, highly efficient
  82. 3:51But you must back up before construction
  83. 3:53Best used in conjunction with Git
  84. 3:55This middle layer
  85. 3:56Is the hybrid solution I want to emphasize the most:
  86. 3:58Plugin + CLI tool
  87. 3:59Method-wise
  88. 4:00You can use plugins like Claudian or Terminal
  89. 4:03To plug CLI Agents like Codex or Claude Code into Obsidian
  90. 4:07The key here is not "having one more chat window,"
  91. 4:10But Obsidian providing the context of the current note, selection, and folder
  92. 4:16While the CLI Agent handles the actual execution of cross-file tasks
  93. 4:20This way
  94. 4:21You can keep the immersive writing experience in Obsidian
  95. 4:24While calling upon stronger Agent execution
  96. 4:27To organize, rewrite, generate indexes, and maintain cross-files
  97. 4:32The downside is that installation and configuration are more developer-oriented
  98. 4:36And the privileges are high, so it's best to back up with Git
  99. 4:40And instructions to the AI should be as clear as possible
  100. 4:42So this category is ideal for writing-and-organizing, content production, cross-file tasks, and semi-automated vault maintenance
  101. 4:50This is also my favorite method right now:
  102. 4:53Not entirely leaving Obsidian
  103. 4:55And not getting stuck by the limitations of regular plugins
  104. 4:58Quadrant 3
  105. 4:59Is Obsidian exposing its file-layer capabilities outward
  106. 5:02That is, interface solutions like MCP and API
  107. 5:05Opening Obsidian's file read/write, search, and some commands to external AI or automation tools
  108. 5:12You can understand it as:
  109. 5:13Obsidian is no longer just a software you manually open
  110. 5:16But turning part of its capabilities into an interface
  111. 5:19For external systems to call according to rules
  112. 5:22Its advantage is being more structured and automated
  113. 5:25Suitable for integrating scripts, workflows, and multi-tool coordination
  114. 5:28Or even building your own knowledge management system
  115. 5:31But its configuration cost is higher, and it's more for developers
  116. 5:35Not very suitable for regular users who just want lightweight Obsidian AI
  117. 5:39So this category fits automated workflows, cross-app integration, batch calling, and developer self-built systems
  118. 5:47This method is not the focus of this video
  119. 5:50And won't be demonstrated further
  120. 5:52Quadrant 4
  121. 5:53Is Obsidian providing Obsidian-layer capabilities outward
  122. 5:56Meaning Obsidian CLI + AI Agent
  123. 5:59Method-wise
  124. 5:59It lets the Agent use Obsidian CLI
  125. 6:02To call Obsidian itself to execute searches, writes, templates, daily notes, summaries, etc.
  126. 6:08The biggest difference from modifying files directly is:
  127. 6:11It's not AI bypassing Obsidian to modify the disk
  128. 6:14But AI using CLI to let Obsidian complete the action itself
  129. 6:18Its advantage is a better understanding of Obsidian's backlinks, tags, templates, and plugin states
  130. 6:23And more suitable for deterministic automation tasks;
  131. 6:26At the same time
  132. 6:27AI doesn't have to repeatedly read the entire vault
  133. 6:30Often it can get results directly via commands
  134. 6:34Thus reducing token consumption
  135. 6:36The downside is a higher configuration barrier
  136. 6:38Currently leaning more towards terminal and Agent workflows
  137. 6:41And the ecosystem is still evolving
  138. 6:43So this suits tag summarization, daily note archiving, batch organizing, Canvas, or template automation
  139. 6:51As well as more system-level knowledge base tasks
  140. 6:54If the previous categories enhance "how humans use Obsidian,"
  141. 6:58This category enhances "how the system automatically gets things done."
  142. 7:01Next
  143. 7:02I will focus on sharing a few methods I'm currently using:
  144. 7:05AI IDE operating the Obsidian vault, Plugin + CLI tool, and Obsidian CLI + Agent
  145. 7:12And following this route
  146. 7:13We'll look at their respective capability boundaries layer by layer
  147. 7:16To ultimately get an optimal Obsidian+AI methodology
  148. 7:23Let's first look at the first advanced method:
  149. 7:25Opening the Obsidian vault directly with an AI IDE
  150. 7:28Its essence is not chatting inside Obsidian
  151. 7:31But treating the entire knowledge base as a Markdown project
  152. 7:34Letting AI directly handle the underlying files
  153. 7:36Obsidian is very suited for this
  154. 7:38Because its notes are essentially local Markdown files
  155. 7:42The AI IDE can directly see folder structures, note content, tags, YAML metadata, and backlinks
  156. 7:49For example, in this Obsidian vault
  157. 7:52I have a folder named vscode+codex
  158. 7:55I am now opening the same Obsidian vault using Cursor, Google Antigravity
  159. 7:58And VS Code respectively
  160. 8:02After opening it, you will find
  161. 8:04They all show the same file directory on the left
  162. 8:08We click into this vscode+codex folder
  163. 8:12And open the note files inside
  164. 8:14At this time, what's displayed on the right
  165. 8:16Is actually the Markdown source code corresponding to this Obsidian note
  166. 8:20There are many AI IDEs now
  167. 8:22Such as Cursor, Google Antigravity, and Trae
  168. 8:26But what I mainly use
  169. 8:27Is still VS Code + Codex plugin
  170. 8:30The reason is quite simple:
  171. 8:32Many AI IDEs are themselves built on the VS Code architecture
  172. 8:36While VS Code is purer
  173. 8:38And its plugin ecosystem is more mature
  174. 8:40Plus, I already have a Codex / ChatGPT subscription
  175. 8:44The quota is sufficient
  176. 8:45Many later AI workflows can reuse this setup
  177. 8:48No need to buy a separate subscription for each tool
  178. 8:51Next, let's get hands-on and see
  179. 8:53How an AI IDE can actually help us organize notes in Obsidian
  180. 8:58We select the note folder we just opened and viewed:
  181. 9:01vscode+codex
  182. 9:03We find the notes here have:
  183. 9:05Inconsistent naming, inconsistent tags, and scattered topics
  184. 9:09This kind of task is very tedious to organize manually
  185. 9:12But it's perfect for an AI IDE
  186. 9:14Here, I don't just tell the AI "help me organize my notes,"
  187. 9:18That scope is too vague
  188. 9:20I will first select this note folder
  189. 9:23Copy its relative path
  190. 9:25Like here, it's vscode+codex
  191. 9:28Then put this path into the prompt
  192. 9:31Telling the AI:
  193. 9:31vscode+codex
  194. 9:32Organize this group of messy notes
  195. 9:35And automatically generate an index page
  196. 9:37Specifically, AI will do three things for me:
  197. 9:381
  198. 9:38Unify naming
  199. 9:382
  200. 9:38Move to appropriate folders
  201. 9:393
  202. 9:40Generate an overview index note
  203. 9:40After execution, you can see the filenames are more uniform
  204. 9:43The directory is clearer
  205. 9:44And it automatically generated an overview index page
  206. 9:47This is the advantage of an AI IDE:
  207. 9:49It doesn't just process a single note
  208. 9:51But can do cross-file, cross-directory structural organization
  209. 9:55Although this method is very powerful,
  210. 9:58If changes are too radical
  211. 9:59Backlinks, reference relationships, and directory structures might get messed up
  212. 10:03Therefore, when using this method
  213. 10:05You must pay attention to safety
  214. 10:07Because it directly modifies underlying files
  215. 10:09So I suggest remembering three points:
  216. 10:11First, back up with Git before major changes;
  217. 10:14Second, have AI output a plan first, then execute;
  218. 10:18Third, only process one small folder at a time
  219. 10:21Do not restructure the entire vault directly
  220. 10:24I just mentioned
  221. 10:25It's best to back up with Git before major changes
  222. 10:28Simply put
  223. 10:29Git can help us record the modification history of the vault
  224. 10:32In case AI messes it up
  225. 10:34It's easy to revert to a previous version
  226. 10:36In Obsidian
  227. 10:37We can integrate Git via community plugins
  228. 10:41Here I open the community plugin market and search for git
  229. 10:45Find the Obsidian Git plugin
  230. 10:48Download, install, and enable it
  231. 10:50Here is another very interesting point:
  232. 10:53When we open the Obsidian vault with VS Code or another AI IDE
  233. 10:58We don't just see the note files
  234. 11:00We can also see
  235. 11:01Hidden configuration folders like .obsidian
  236. 11:05This saves many of Obsidian's configurations
  237. 11:07Like plugin configs, theme configs, workspace settings, etc.
  238. 11:12This means
  239. 11:13The AI IDE doesn't just help us organize notes
  240. 11:15It can also help us understand the configuration logic behind Obsidian
  241. 11:20For example, I now want to use the Obsidian Git plugin to back up my vault
  242. 11:25I can take
  243. 11:26The relative path of the .obsidian config folder and tell the AI
  244. 11:30Then ask it:
  245. 11:33"I want to use the Obsidian-git plugin
  246. 11:35To back up my Obsidian
  247. 11:37How should I configure it, help me outline the full process"
  248. 11:40This way, AI will base it on the actual situation of the current vault
  249. 11:43And outline a set of configuration steps for me
  250. 11:45I just need to reference the process it provides
  251. 11:48To complete the Obsidian Git configuration much faster
  252. 11:50Instead of digging through documentation and tutorials bit by bit myself
  253. 11:54So my understanding of an AI IDE is:
  254. 11:57It's more like an external engineering team
  255. 11:59It doesn't just help you modify a single note
  256. 12:01But can directly enter the entire vault
  257. 12:04To help you do structural work like batch naming, directory restructuring, tag cleaning, and generating index pages
  258. 12:10If you just want to polish an article
  259. 12:13Then an AI plugin inside Obsidian is enough
  260. 12:16But if you are organizing a batch of notes
  261. 12:17Or even the entire knowledge base
  262. 12:19Then an AI IDE is more appropriate
  263. 12:25This part is the method I want to highlight the most:
  264. 12:27Plugin + CLI Agent
  265. 12:29Its essence isn't installing yet another chat plugin
  266. 12:31But letting Obsidian provide contexts like current note, selection, and folder
  267. 12:36And letting Agents like Codex CLI or Claude Code actually execute tasks
  268. 12:42We've already used VS Code + Codex plugin earlier
  269. 12:45Here I'll continue using Codex
  270. 12:47Just changing the entry point from the VS Code plugin
  271. 12:49To Codex CLI
  272. 12:51This way you don't need to learn a whole new set of tools
  273. 12:53The underlying Agent is still the same
  274. 12:55It's just that this time it runs in the terminal
  275. 12:57Making it easier to integrate with plugins like Obsidian Terminal or Claudian
  276. 13:01Installation is also very simple, open the terminal
  277. 13:04Execute this one-line command to install
  278. 13:06Type Codex to launch Codex
  279. 13:09Complete login authorization on the first launch
  280. 13:11Then you can use it directly in the vault directory
  281. 13:14This solution can be divided into three layers
  282. 13:16Layer one
  283. 13:17Is directly entering the vault directory in the system Terminal to run Codex;
  284. 13:21Layer two
  285. 13:22Is using Obsidian's Terminal plugin
  286. 13:24To embed the terminal into Obsidian;
  287. 13:27Layer three is using a plugin like Claudian
  288. 13:29To package the CLI Agent into an AI collaboration panel within Obsidian
  289. 13:34The most basic method
  290. 13:35Is directly using your computer's built-in Terminal
  291. 13:38Navigate to the Obsidian vault directory
  292. 13:41Then run Codex CLI
  293. 13:43This way the Agent can directly read and process Markdown files in the vault
  294. 13:47If you don't want to switch to an external terminal
  295. 13:49You can also use Obsidian's Terminal plugin
  296. 13:53It just puts a terminal inside Obsidian
  297. 13:55Making it convenient to read notes
  298. 13:56While running Codex CLI
  299. 13:59The operation is also very simple:
  300. 14:00Press Cmd + P here
  301. 14:02To open Obsidian's command palette
  302. 14:05If you're on Windows, it's Ctrl+P
  303. 14:08Search for terminal
  304. 14:10Select this
  305. 14:12(Terminal: Open root directory in terminal: Integrated)
  306. 14:15Which is: Open root directory in integrated mode
  307. 14:17This will directly open a built-in terminal
  308. 14:18In the current vault directory
  309. 14:19(## Introducing Claudian:
  310. 14:19Why it's the focus)
  311. 14:20Taking it a step further
  312. 14:23Is using a plugin like Claudian
  313. 14:26Its value isn't "one more chat box,"
  314. 14:30But being able to directly pass the current note, selection, and path to the Agent
  315. 14:34Letting the Agent work around the content you are handling
  316. 14:37We open this GitHub project URL
  317. 14:41You can view the details of this claudian project
  318. 14:43From here, we can see
  319. 14:49It supports mainstream Agents like Claude Code and Codex CLI
  320. 14:50But plugins like Claudian
  321. 14:53Cannot be downloaded as casually
  322. 14:57From Obsidian's official plugin market like standard community plugins
  323. 14:58The reason is simple:
  324. 15:01It's not a lightweight plugin just responsible for "reading and writing text"
  325. 15:03But it breaks through Obsidian's original system
  326. 15:06To manipulate underlying files and external commands
  327. 15:09Precisely because it has higher privileges and stronger capabilities
  328. 15:12Its installation method leans more toward developers
  329. 15:16This kind of plugin is more like a "high-privilege collaboration interface,"
  330. 15:19Rather than a standard feature button
  331. 15:21There are a few main ways to install Claudian
  332. 15:24The first is using BRAT, which is quite simple
  333. 15:25Suitable for a quick trial
  334. 15:28The second is manually downloading the plugin files from GitHub
  335. 15:30And putting them in Obsidian's plugins directory
  336. 15:34This method is more stable, but requires manual operation
  337. 15:38The third is installing from source, more suitable for developers
  338. 15:40And makes future updates easier
  339. 15:42Here I'm using a more hassle-free method:
  340. 15:44Letting Codex install it for me directly
  341. 15:46I open Codex in the Terminal
  342. 15:47Then tell it:
  343. 15:50In the current Obsidian vault
  344. 15:52Help me install Claudian
  345. 15:53The repository URL is this
  346. 15:54Next
  347. 15:59Steps like downloading, placing in the correct location, installing dependencies, and generating plugin files
  348. 16:02Codex will handle all of it automatically
  349. 16:03Once installation is complete
  350. 16:05I go back to the Obsidian plugin list to check
  351. 16:07I don't see Claudian just yet
  352. 16:09Don't panic here
  353. 16:11I checked with VS Code
  354. 16:13And found the plugin is actually already installed
  355. 16:16It's just that Obsidian hasn't loaded it yet
  356. 16:19Restart Obsidian, go back to the plugin list
  357. 16:21And you'll be able to see Claudian
  358. 16:24Enable it, and you can start using it
  359. 16:26Claudian's basic usage is very intuitive
  360. 16:30By default, it uses the current file as the working context
  361. 16:33We can also use @ to specify a file
  362. 16:37To include a certain note in the collaboration scope
  363. 16:37In addition
  364. 16:41The selected note content will also be recognized by the plugin
  365. 16:43And automatically act as the context for AI collaboration
  366. 16:46This means it's not chatting blindly
  367. 16:49But will try to work around the content you are currently handling
  368. 16:51Just like in VS Code
  369. 16:55I can also let Claudian help me organize this messy group of notes
  370. 16:56I tell Codex directly:
  371. 16:57Help me organize this messy set of notes
  372. 17:00And generate an index page
  373. 17:01After execution
  374. 17:04This originally scattered group of notes becomes a clear little topic:
  375. 17:06Filenames are unified
  376. 17:08Notes are placed into appropriate folders
  377. 17:10And an overview index is generated
  378. 17:16Making it easy for me to quickly view and jump from a single entry point
  379. 17:17A quick reminder here
  380. 17:22Claudian's safety principles are the same as the AI IDE section earlier
  381. 17:26Whether you use VS Code + Codex
  382. 17:28Or Claudian + Codex CLI
  383. 17:33They essentially can both directly modify your vault files
  384. 17:37So we shouldn't let it modify the entire vault right away
  385. 17:39It's best to limit the scope first
  386. 17:43Like only processing a specific folder, or a few notes
  387. 17:46Or a very clear, small task
  388. 17:49If the task is large, let it provide a plan first
  389. 17:51Confirm it before executing
  390. 17:54Finally, to reiterate: before making major changes
  391. 17:56Always back up first
  392. 17:58For us, Git backup is the baseline protection
  393. 18:00This step cannot be skipped
  394. 18:01Besides Claudian
  395. 18:05You can also look out for plugins like Obsidian-Agent-Client
  396. 18:08Its concept is similar, but it supports more Agents
  397. 18:14Including Claude Code, Codex CLI, Gemini CLI, OpenCode, etc.
  398. 18:15So
  399. 18:18The most suitable scenario for Plugin + CLI Agent
  400. 18:24Is organizing while writing, cross-file maintenance, content production, and semi-automated vault management
  401. 18:29It balances Obsidian's immersive experience with the CLI Agent's execution capabilities
  402. 18:32It's the method I highly recommend trying first right now
  403. 18:33However
  404. 18:37This category essentially still has the Agent directly operating the vault file layer
  405. 18:40In the next section, we'll look at a more advanced method:
  406. 18:43Letting the Agent use Obsidian CLI
  407. 18:48To invoke Obsidian's own capabilities to complete tasks
  408. 18:48The last method
  409. 18:51Is Obsidian CLI + Agent invocation
  410. 18:53It's more like a system-level execution chain
  411. 18:55Rather than a standard plugin
  412. 18:57Previous solutions were more about humans manually using tools;
  413. 19:01This layer is more about letting the Agent directly invoke Obsidian's system capabilities
  414. 19:04Its greatest value can be summarized in three phrases:
  415. 19:07Saving tokens, higher safety, and stronger automation
  416. 19:08Why is that?
  417. 19:11Because it doesn't have the AI scan the entire vault
  418. 19:15Nor does it let the AI directly and crudely read/write files
  419. 19:17Instead, through the official CLI
  420. 19:20It sends instructions to the running Obsidian instance
  421. 19:21The benefit of doing this is
  422. 19:24AI doesn't need to repeatedly read massive amounts of context
  423. 19:27No need to cram the entire vault into the model
  424. 19:30So token consumption will be significantly lower
  425. 19:33At the same time, it's safer and more stable
  426. 19:36Because what's actually executing the changes is Obsidian itself
  427. 19:39Not an external tool randomly modifying files on the disk;
  428. 19:44This makes it easier to maintain the consistency of backlinks, templates, tags, and internal states
  429. 19:47So you can think of it as:
  430. 19:49Obsidian is not just a note-taking app
  431. 19:55It starts exposing a layer of system capabilities that can be invoked by an Agent via CLI
  432. 19:59If earlier solutions were enhancing "how humans use Obsidian,"
  433. 20:03This layer enhances "how the system does things automatically."
  434. 20:05Regarding installing and enabling Obsidian CLI
  435. 20:09We can refer to this official Obsidian CLI help page:
  436. 20:11It's mainly divided into three steps:
  437. 20:16Update Obsidian, enable CLI, register CLI
  438. 20:16Step one
  439. 20:20First, we confirm Obsidian is updated to a version that supports CLI
  440. 20:23The official requirement is 1.12 or above
  441. 20:25But in actual practice
  442. 20:28Just updating to the latest version is fine
  443. 20:29Step two
  444. 20:32We need to turn on the CLI switch inside Obsidian
  445. 20:35This is essentially telling Obsidian:
  446. 20:39I allow you to expose a command-line entry point
  447. 20:41Step three, register CLI
  448. 20:42In the General settings, we find:
  449. 20:44Command line interface
  450. 20:47After clicking to enable, a prompt will pop up
  451. 20:51Roughly meaning: set up the CLI in the terminal
  452. 20:53Just click confirm to register here
  453. 20:54Once registration is complete
  454. 20:58The terminal will be able to recognize Obsidian commands
  455. 20:58Finally
  456. 21:01I'll still use the terminal plugin to open the terminal
  457. 21:05Then input and execute: obsidian help
  458. 21:08If it's recognized properly and outputs results
  459. 21:11That means Obsidian CLI is successfully enabled
  460. 21:13Another point to note
  461. 21:16Obsidian CLI does not run detached from Obsidian
  462. 21:19It requires the desktop Obsidian app to remain open
  463. 21:21Before letting the Agent officially take over
  464. 21:26Let's manually run a few Obsidian CLI commands in the terminal
  465. 21:28To get a feel for what it can actually do
  466. 21:31Let's try the most intuitive action first:
  467. 21:32Open today's daily note
  468. 21:33In the terminal
  469. 21:36I inputted and executed this command
  470. 21:39And Obsidian automatically jumped to today's daily note
  471. 21:42I'll just write some random content here first
  472. 21:44So it's easier to continue testing later
  473. 21:45Next, in this note
  474. 21:47I'll append a task
  475. 21:50I inputted and executed this command again
  476. 21:51Going back to the daily note
  477. 21:55I found that new content has been added to this daily note:
  478. 21:56CLI test
  479. 21:58Finally, I'll try a search
  480. 22:00I input and execute this command
  481. 22:03The terminal directly returns the paths of relevant notes
  482. 22:05The key here is
  483. 22:08AI doesn't need to read the entire vault itself
  484. 22:11But can use Obsidian's search capabilities
  485. 22:12To get matched results
  486. 22:15At this point, we can intuitively feel:
  487. 22:17This isn't a "simulated operation,"
  488. 22:20But truly controlling Obsidian
  489. 22:23Obsidian CLI is highly suited for AI Agents to invoke
  490. 22:24So then
  491. 22:28How does the Agent know which commands to use and how?
  492. 22:29It relies on Agent Skills
  493. 22:33Here we use Obsidian's official Agent Skills
  494. 22:38I download the Obsidian skills into the same directory as the current Obsidian vault
  495. 22:40I tell Claudian: in the current directory
  496. 22:42Download Obsidian skills for me
  497. 22:44After AI executes
  498. 22:47It prompts that Obsidian Skills installation is complete
  499. 22:49I switch to VS Code to check
  500. 22:52The Skills file is already in the current vault
  501. 22:55Now, we enter the core of this section:
  502. 23:00Utilizing Agent + Obsidian skills + Obsidian CLI
  503. 23:02To complete an automated task
  504. 23:04For example: I read this webpage article
  505. 23:06And save it to the Obsidian vault
  506. 23:07While generating a reading note and canvas
  507. 23:09To visually demonstrate the Obsidian CLI workflow
  508. 23:12Here I'll continue using Claudian to initiate tasks
  509. 23:13But let me clarify first:
  510. 23:15Claudian is not the focus of this section
  511. 23:18Claudian itself can of course directly read and write vault files
  512. 23:21But what I really want to demonstrate here is another chain:
  513. 23:25Letting the Agent maximize its use of Obsidian CLI to invoke Obsidian's capabilities
  514. 23:27Instead of simply bypassing Obsidian
  515. 23:30To write files directly in the local file system
  516. 23:31So in this example
  517. 23:35You can understand Claudian as "the Agent entry point to initiate tasks,"
  518. 23:39While Obsidian CLI is the actual system interface connecting the Agent and Obsidian
  519. 23:40I tell the AI as follows:
  520. 23:42Please use Obsidian CLI
  521. 23:45To organize this webpage content into my current Obsidian vault:
  522. 23:49Save the original text, generate a reading note, generate a canvas
  523. 23:51Put files into the specified folder
  524. 23:54Do not just write files directly in the file system
  525. 23:56Webpage and skills are as follows
  526. 23:59The task wasn't completely successful on the first try
  527. 24:02For instance, initially the original text and reading note were generated
  528. 24:04But the Canvas failed to open
  529. 24:07At this time, I kept having the Agent fix it based on errors
  530. 24:10Finally, the Canvas was also successfully displayed
  531. 24:12I used Claudian for demonstration in this section
  532. 24:15But the focus is actually not Claudian itself
  533. 24:16As long as it's a local Agent
  534. 24:19As long as it can invoke Obsidian CLI
  535. 24:21It can hook into this workflow
  536. 24:28Like Codex App, Codex's VS Code plugin, Codex CLI, Claude Code, etc.
  537. 24:30They can all do similar things
  538. 24:31This way
  539. 24:34Obsidian is no longer just a note-taking app
  540. 24:37But a knowledge system that can be automatically dispatched by Agents
  541. 24:40So, if the previous solutions were enhancing "humans,"
  542. 24:45This layer is enhancing "the system."
  543. 24:48Finally, let's summarize: Integrating AI into Obsidian
  544. 24:49Is not just limited to one way
  545. 24:54But a continuous upgrade path from "assisted usage" to "system-level automation"
  546. 24:55In my system here
  547. 24:58Codex is the most core underlying capability
  548. 24:59Because it's not just a tool
  549. 25:01But a real Agent execution engine
  550. 25:02Of course
  551. 25:04If you usually use Claude Code mainly
  552. 25:06You can also just replace Codex with Claude Code
  553. 25:07Reusing this logic
  554. 25:10Around Codex, there is already a relatively mature ecosystem
  555. 25:14So a lot of times we don't need to install an extra bunch of tools
  556. 25:16Nor do we need to configure APIs everywhere
  557. 25:18For us, the ideal state is:
  558. 25:20Try to keep only one AI subscription
  559. 25:23Minimize the hassle, try to keep capabilities unified
  560. 25:24This way
  561. 25:27Only then can Obsidian + AI truly be simple, efficient, and powerful
  562. 25:29With costs kept low enough
  563. 25:32If you just want to view Obsidian's underlying files
  564. 25:34Or batch organize vault files
  565. 25:37Then you can use the VS Code + Codex plugin
  566. 25:39To directly operate on the file layer
  567. 25:42If you wish to preserve the immersive experience inside Obsidian
  568. 25:44While also wanting to use Codex's Agent capabilities
  569. 25:48You can invoke Codex CLI via the Claudian plugin
  570. 25:50If you want to build stronger automation
  571. 25:52You can have Codex act as the main Agent
  572. 25:55Controlling Obsidian via Obsidian CLI
  573. 25:57As for where you initiate tasks
  574. 26:00VS Code plugins, Obsidian plugins, CLI tools
  575. 26:02Or standalone apps, all work fine
  576. 26:04Ultimately, only the entry point is different
  577. 26:07If you found this video helpful
  578. 26:09Please like, subscribe, and share
  579. 26:12If you encounter any problems during hands-on practice
  580. 26:14Feel free to leave a message in the comments
  581. 26:16I'm Mingnify, see you in the next video

About this transcript

This page contains the full transcript of Obsidian + AI 终极方案:Codex/ClaudeCode + VS Code + claudian + Obsidian CLI by 明立非 · Mingnify | Indie Maker, generated from the public captions YouTube serves with the video. The transcript has 4,294 words across 581 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 choose a caption track available on the video.

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, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.