Obsidian + AI 终极方案:Codex/ClaudeCode + VS Code + claudian + Obsidian CLI — Transcript
Full transcript
- 0:00Many people say
- 0:01Obsidian is the preferred knowledge management tool in the AI era
- 0:04Because it essentially relies on local Markdown files
- 0:08The content is naturally easier for AI to read and process
- 0:11And precisely because of this
- 0:12Obsidian + AI becomes very important:
- 0:14It doesn't just help you chat
- 0:16But helps you organize, restructure, and automate your knowledge base
- 0:19But the problem is
- 0:19There are many ways to integrate AI into Obsidian
- 0:22Plugins, IDEs, CLIs, MCP... they all seem usable
- 0:26But it also feels overwhelming to start
- 0:28So
- 0:29In this video, I will first help you sort out all mainstream solutions
- 0:33And at the end
- 0:34Give you what I consider the best Obsidian + AI workflow for long-term use
- 0:40Codex/ Claude Code+ Claudian + VS Code + Obsidian CLI
- 0:46This solution
- 0:47Balances experience, efficiency, cost, and automation capabilities
- 0:53There are many ways to integrate AI into Obsidian
- 0:56But don't rush to memorize tool names
- 0:58What's really important is not "which tool you use,"
- 1:01But at what level these tools operate
- 1:04If we don't categorize them first
- 1:05Plugins, IDEs, CLIs, Agents
- 1:08All these terms will make your head spin
- 1:11So before we dive into specific methods
- 1:14Let's grasp two core questions:
- 1:16First
- 1:17Who is driving whom—is AI actively operating Obsidian
- 1:21Or is Obsidian opening its capabilities for AI to call?
- 1:24Second
- 1:25Which layer is being operated—is it directly the file layer
- 1:28Or completing actions inside Obsidian
- 1:31Once these two dimensions are determined
- 1:33All subsequent methods will be clearer
- 1:35Based on these two dimensions
- 1:36We can map Obsidian AI integration solutions into a four-quadrant chart
- 1:41This way
- 1:42The responsibilities, boundaries, and use cases of each method
- 1:45Will be clear at a glance
- 1:47Quadrant 1
- 1:48Is AI actively working within the Obsidian layer
- 1:51Which means regular AI plugins
- 1:53Like the Copilot type
- 1:56They usually revolve around the current note, selection
- 1:59Or whole-vault indexing
- 2:00For Q&A, summarizing, rewriting, and lightweight RAG
- 2:05Its advantage is great immersion
- 2:07Closest to the native Obsidian workflow
- 2:10Suitable for having AI add a sentence, revise a paragraph, or explain a concept while writing
- 2:16But its limitations are also obvious: low privileges
- 2:19Not suitable for structural tasks like batch renaming, moving files, or restructuring directories;
- 2:24And these plugins mostly require configuring API keys separately
- 2:28Constantly consuming tokens
- 2:29Some features even require extra payment
- 2:32So this method is suitable for daily writing, single-page processing, and lightweight Q&A
- 2:37If your goal is just to make Obsidian better for writing and asking
- 2:41It's sufficient;
- 2:42But if you want AI to truly restructure your knowledge base
- 2:45And better reuse your AI subscriptions
- 2:47It won't be enough
- 2:49I am currently not using this method
- 2:51So I won't go into detail later
- 2:53Quadrant 2
- 2:55Is AI IDEs (including code editors) actively operating on the file layer
- 2:58That is, using AI IDEs like VS Code, Cursor, or Trae
- 3:02To open the Obsidian vault directly
- 3:04Treating the entire knowledge base as a project
- 3:08At this time, the objects AI operates on
- 3:09Are mainly Markdown files, YAML metadata, and folder structures
- 3:13Rather than the views and interfaces inside Obsidian
- 3:16Its advantage is very strong file-layer control
- 3:19Especially suitable for cross-file batch organization, unified naming, tag cleaning, generating index pages
- 3:25Or even restructuring the entire directory
- 3:27But it is further away from the native Obsidian ecosystem
- 3:31Its awareness of backlinks, views, and plugin states is less direct;
- 3:35If the changes are too radical
- 3:37It may bring risks like broken links, directory mess, and altered references
- 3:43So this category is better for deep editing, batch cleaning, new vault setup, and directory restructuring
- 3:48It's like an external engineering team, highly efficient
- 3:51But you must back up before construction
- 3:53Best used in conjunction with Git
- 3:55This middle layer
- 3:56Is the hybrid solution I want to emphasize the most:
- 3:58Plugin + CLI tool
- 3:59Method-wise
- 4:00You can use plugins like Claudian or Terminal
- 4:03To plug CLI Agents like Codex or Claude Code into Obsidian
- 4:07The key here is not "having one more chat window,"
- 4:10But Obsidian providing the context of the current note, selection, and folder
- 4:16While the CLI Agent handles the actual execution of cross-file tasks
- 4:20This way
- 4:21You can keep the immersive writing experience in Obsidian
- 4:24While calling upon stronger Agent execution
- 4:27To organize, rewrite, generate indexes, and maintain cross-files
- 4:32The downside is that installation and configuration are more developer-oriented
- 4:36And the privileges are high, so it's best to back up with Git
- 4:40And instructions to the AI should be as clear as possible
- 4:42So this category is ideal for writing-and-organizing, content production, cross-file tasks, and semi-automated vault maintenance
- 4:50This is also my favorite method right now:
- 4:53Not entirely leaving Obsidian
- 4:55And not getting stuck by the limitations of regular plugins
- 4:58Quadrant 3
- 4:59Is Obsidian exposing its file-layer capabilities outward
- 5:02That is, interface solutions like MCP and API
- 5:05Opening Obsidian's file read/write, search, and some commands to external AI or automation tools
- 5:12You can understand it as:
- 5:13Obsidian is no longer just a software you manually open
- 5:16But turning part of its capabilities into an interface
- 5:19For external systems to call according to rules
- 5:22Its advantage is being more structured and automated
- 5:25Suitable for integrating scripts, workflows, and multi-tool coordination
- 5:28Or even building your own knowledge management system
- 5:31But its configuration cost is higher, and it's more for developers
- 5:35Not very suitable for regular users who just want lightweight Obsidian AI
- 5:39So this category fits automated workflows, cross-app integration, batch calling, and developer self-built systems
- 5:47This method is not the focus of this video
- 5:50And won't be demonstrated further
- 5:52Quadrant 4
- 5:53Is Obsidian providing Obsidian-layer capabilities outward
- 5:56Meaning Obsidian CLI + AI Agent
- 5:59Method-wise
- 5:59It lets the Agent use Obsidian CLI
- 6:02To call Obsidian itself to execute searches, writes, templates, daily notes, summaries, etc.
- 6:08The biggest difference from modifying files directly is:
- 6:11It's not AI bypassing Obsidian to modify the disk
- 6:14But AI using CLI to let Obsidian complete the action itself
- 6:18Its advantage is a better understanding of Obsidian's backlinks, tags, templates, and plugin states
- 6:23And more suitable for deterministic automation tasks;
- 6:26At the same time
- 6:27AI doesn't have to repeatedly read the entire vault
- 6:30Often it can get results directly via commands
- 6:34Thus reducing token consumption
- 6:36The downside is a higher configuration barrier
- 6:38Currently leaning more towards terminal and Agent workflows
- 6:41And the ecosystem is still evolving
- 6:43So this suits tag summarization, daily note archiving, batch organizing, Canvas, or template automation
- 6:51As well as more system-level knowledge base tasks
- 6:54If the previous categories enhance "how humans use Obsidian,"
- 6:58This category enhances "how the system automatically gets things done."
- 7:01Next
- 7:02I will focus on sharing a few methods I'm currently using:
- 7:05AI IDE operating the Obsidian vault, Plugin + CLI tool, and Obsidian CLI + Agent
- 7:12And following this route
- 7:13We'll look at their respective capability boundaries layer by layer
- 7:16To ultimately get an optimal Obsidian+AI methodology
- 7:23Let's first look at the first advanced method:
- 7:25Opening the Obsidian vault directly with an AI IDE
- 7:28Its essence is not chatting inside Obsidian
- 7:31But treating the entire knowledge base as a Markdown project
- 7:34Letting AI directly handle the underlying files
- 7:36Obsidian is very suited for this
- 7:38Because its notes are essentially local Markdown files
- 7:42The AI IDE can directly see folder structures, note content, tags, YAML metadata, and backlinks
- 7:49For example, in this Obsidian vault
- 7:52I have a folder named vscode+codex
- 7:55I am now opening the same Obsidian vault using Cursor, Google Antigravity
- 7:58And VS Code respectively
- 8:02After opening it, you will find
- 8:04They all show the same file directory on the left
- 8:08We click into this vscode+codex folder
- 8:12And open the note files inside
- 8:14At this time, what's displayed on the right
- 8:16Is actually the Markdown source code corresponding to this Obsidian note
- 8:20There are many AI IDEs now
- 8:22Such as Cursor, Google Antigravity, and Trae
- 8:26But what I mainly use
- 8:27Is still VS Code + Codex plugin
- 8:30The reason is quite simple:
- 8:32Many AI IDEs are themselves built on the VS Code architecture
- 8:36While VS Code is purer
- 8:38And its plugin ecosystem is more mature
- 8:40Plus, I already have a Codex / ChatGPT subscription
- 8:44The quota is sufficient
- 8:45Many later AI workflows can reuse this setup
- 8:48No need to buy a separate subscription for each tool
- 8:51Next, let's get hands-on and see
- 8:53How an AI IDE can actually help us organize notes in Obsidian
- 8:58We select the note folder we just opened and viewed:
- 9:01vscode+codex
- 9:03We find the notes here have:
- 9:05Inconsistent naming, inconsistent tags, and scattered topics
- 9:09This kind of task is very tedious to organize manually
- 9:12But it's perfect for an AI IDE
- 9:14Here, I don't just tell the AI "help me organize my notes,"
- 9:18That scope is too vague
- 9:20I will first select this note folder
- 9:23Copy its relative path
- 9:25Like here, it's vscode+codex
- 9:28Then put this path into the prompt
- 9:31Telling the AI:
- 9:31vscode+codex
- 9:32Organize this group of messy notes
- 9:35And automatically generate an index page
- 9:37Specifically, AI will do three things for me:
- 9:381
- 9:38Unify naming
- 9:382
- 9:38Move to appropriate folders
- 9:393
- 9:40Generate an overview index note
- 9:40After execution, you can see the filenames are more uniform
- 9:43The directory is clearer
- 9:44And it automatically generated an overview index page
- 9:47This is the advantage of an AI IDE:
- 9:49It doesn't just process a single note
- 9:51But can do cross-file, cross-directory structural organization
- 9:55Although this method is very powerful,
- 9:58If changes are too radical
- 9:59Backlinks, reference relationships, and directory structures might get messed up
- 10:03Therefore, when using this method
- 10:05You must pay attention to safety
- 10:07Because it directly modifies underlying files
- 10:09So I suggest remembering three points:
- 10:11First, back up with Git before major changes;
- 10:14Second, have AI output a plan first, then execute;
- 10:18Third, only process one small folder at a time
- 10:21Do not restructure the entire vault directly
- 10:24I just mentioned
- 10:25It's best to back up with Git before major changes
- 10:28Simply put
- 10:29Git can help us record the modification history of the vault
- 10:32In case AI messes it up
- 10:34It's easy to revert to a previous version
- 10:36In Obsidian
- 10:37We can integrate Git via community plugins
- 10:41Here I open the community plugin market and search for git
- 10:45Find the Obsidian Git plugin
- 10:48Download, install, and enable it
- 10:50Here is another very interesting point:
- 10:53When we open the Obsidian vault with VS Code or another AI IDE
- 10:58We don't just see the note files
- 11:00We can also see
- 11:01Hidden configuration folders like .obsidian
- 11:05This saves many of Obsidian's configurations
- 11:07Like plugin configs, theme configs, workspace settings, etc.
- 11:12This means
- 11:13The AI IDE doesn't just help us organize notes
- 11:15It can also help us understand the configuration logic behind Obsidian
- 11:20For example, I now want to use the Obsidian Git plugin to back up my vault
- 11:25I can take
- 11:26The relative path of the .obsidian config folder and tell the AI
- 11:30Then ask it:
- 11:33"I want to use the Obsidian-git plugin
- 11:35To back up my Obsidian
- 11:37How should I configure it, help me outline the full process"
- 11:40This way, AI will base it on the actual situation of the current vault
- 11:43And outline a set of configuration steps for me
- 11:45I just need to reference the process it provides
- 11:48To complete the Obsidian Git configuration much faster
- 11:50Instead of digging through documentation and tutorials bit by bit myself
- 11:54So my understanding of an AI IDE is:
- 11:57It's more like an external engineering team
- 11:59It doesn't just help you modify a single note
- 12:01But can directly enter the entire vault
- 12:04To help you do structural work like batch naming, directory restructuring, tag cleaning, and generating index pages
- 12:10If you just want to polish an article
- 12:13Then an AI plugin inside Obsidian is enough
- 12:16But if you are organizing a batch of notes
- 12:17Or even the entire knowledge base
- 12:19Then an AI IDE is more appropriate
- 12:25This part is the method I want to highlight the most:
- 12:27Plugin + CLI Agent
- 12:29Its essence isn't installing yet another chat plugin
- 12:31But letting Obsidian provide contexts like current note, selection, and folder
- 12:36And letting Agents like Codex CLI or Claude Code actually execute tasks
- 12:42We've already used VS Code + Codex plugin earlier
- 12:45Here I'll continue using Codex
- 12:47Just changing the entry point from the VS Code plugin
- 12:49To Codex CLI
- 12:51This way you don't need to learn a whole new set of tools
- 12:53The underlying Agent is still the same
- 12:55It's just that this time it runs in the terminal
- 12:57Making it easier to integrate with plugins like Obsidian Terminal or Claudian
- 13:01Installation is also very simple, open the terminal
- 13:04Execute this one-line command to install
- 13:06Type Codex to launch Codex
- 13:09Complete login authorization on the first launch
- 13:11Then you can use it directly in the vault directory
- 13:14This solution can be divided into three layers
- 13:16Layer one
- 13:17Is directly entering the vault directory in the system Terminal to run Codex;
- 13:21Layer two
- 13:22Is using Obsidian's Terminal plugin
- 13:24To embed the terminal into Obsidian;
- 13:27Layer three is using a plugin like Claudian
- 13:29To package the CLI Agent into an AI collaboration panel within Obsidian
- 13:34The most basic method
- 13:35Is directly using your computer's built-in Terminal
- 13:38Navigate to the Obsidian vault directory
- 13:41Then run Codex CLI
- 13:43This way the Agent can directly read and process Markdown files in the vault
- 13:47If you don't want to switch to an external terminal
- 13:49You can also use Obsidian's Terminal plugin
- 13:53It just puts a terminal inside Obsidian
- 13:55Making it convenient to read notes
- 13:56While running Codex CLI
- 13:59The operation is also very simple:
- 14:00Press Cmd + P here
- 14:02To open Obsidian's command palette
- 14:05If you're on Windows, it's Ctrl+P
- 14:08Search for terminal
- 14:10Select this
- 14:12(Terminal: Open root directory in terminal: Integrated)
- 14:15Which is: Open root directory in integrated mode
- 14:17This will directly open a built-in terminal
- 14:18In the current vault directory
- 14:19(## Introducing Claudian:
- 14:19Why it's the focus)
- 14:20Taking it a step further
- 14:23Is using a plugin like Claudian
- 14:26Its value isn't "one more chat box,"
- 14:30But being able to directly pass the current note, selection, and path to the Agent
- 14:34Letting the Agent work around the content you are handling
- 14:37We open this GitHub project URL
- 14:41You can view the details of this claudian project
- 14:43From here, we can see
- 14:49It supports mainstream Agents like Claude Code and Codex CLI
- 14:50But plugins like Claudian
- 14:53Cannot be downloaded as casually
- 14:57From Obsidian's official plugin market like standard community plugins
- 14:58The reason is simple:
- 15:01It's not a lightweight plugin just responsible for "reading and writing text"
- 15:03But it breaks through Obsidian's original system
- 15:06To manipulate underlying files and external commands
- 15:09Precisely because it has higher privileges and stronger capabilities
- 15:12Its installation method leans more toward developers
- 15:16This kind of plugin is more like a "high-privilege collaboration interface,"
- 15:19Rather than a standard feature button
- 15:21There are a few main ways to install Claudian
- 15:24The first is using BRAT, which is quite simple
- 15:25Suitable for a quick trial
- 15:28The second is manually downloading the plugin files from GitHub
- 15:30And putting them in Obsidian's plugins directory
- 15:34This method is more stable, but requires manual operation
- 15:38The third is installing from source, more suitable for developers
- 15:40And makes future updates easier
- 15:42Here I'm using a more hassle-free method:
- 15:44Letting Codex install it for me directly
- 15:46I open Codex in the Terminal
- 15:47Then tell it:
- 15:50In the current Obsidian vault
- 15:52Help me install Claudian
- 15:53The repository URL is this
- 15:54Next
- 15:59Steps like downloading, placing in the correct location, installing dependencies, and generating plugin files
- 16:02Codex will handle all of it automatically
- 16:03Once installation is complete
- 16:05I go back to the Obsidian plugin list to check
- 16:07I don't see Claudian just yet
- 16:09Don't panic here
- 16:11I checked with VS Code
- 16:13And found the plugin is actually already installed
- 16:16It's just that Obsidian hasn't loaded it yet
- 16:19Restart Obsidian, go back to the plugin list
- 16:21And you'll be able to see Claudian
- 16:24Enable it, and you can start using it
- 16:26Claudian's basic usage is very intuitive
- 16:30By default, it uses the current file as the working context
- 16:33We can also use @ to specify a file
- 16:37To include a certain note in the collaboration scope
- 16:37In addition
- 16:41The selected note content will also be recognized by the plugin
- 16:43And automatically act as the context for AI collaboration
- 16:46This means it's not chatting blindly
- 16:49But will try to work around the content you are currently handling
- 16:51Just like in VS Code
- 16:55I can also let Claudian help me organize this messy group of notes
- 16:56I tell Codex directly:
- 16:57Help me organize this messy set of notes
- 17:00And generate an index page
- 17:01After execution
- 17:04This originally scattered group of notes becomes a clear little topic:
- 17:06Filenames are unified
- 17:08Notes are placed into appropriate folders
- 17:10And an overview index is generated
- 17:16Making it easy for me to quickly view and jump from a single entry point
- 17:17A quick reminder here
- 17:22Claudian's safety principles are the same as the AI IDE section earlier
- 17:26Whether you use VS Code + Codex
- 17:28Or Claudian + Codex CLI
- 17:33They essentially can both directly modify your vault files
- 17:37So we shouldn't let it modify the entire vault right away
- 17:39It's best to limit the scope first
- 17:43Like only processing a specific folder, or a few notes
- 17:46Or a very clear, small task
- 17:49If the task is large, let it provide a plan first
- 17:51Confirm it before executing
- 17:54Finally, to reiterate: before making major changes
- 17:56Always back up first
- 17:58For us, Git backup is the baseline protection
- 18:00This step cannot be skipped
- 18:01Besides Claudian
- 18:05You can also look out for plugins like Obsidian-Agent-Client
- 18:08Its concept is similar, but it supports more Agents
- 18:14Including Claude Code, Codex CLI, Gemini CLI, OpenCode, etc.
- 18:15So
- 18:18The most suitable scenario for Plugin + CLI Agent
- 18:24Is organizing while writing, cross-file maintenance, content production, and semi-automated vault management
- 18:29It balances Obsidian's immersive experience with the CLI Agent's execution capabilities
- 18:32It's the method I highly recommend trying first right now
- 18:33However
- 18:37This category essentially still has the Agent directly operating the vault file layer
- 18:40In the next section, we'll look at a more advanced method:
- 18:43Letting the Agent use Obsidian CLI
- 18:48To invoke Obsidian's own capabilities to complete tasks
- 18:48The last method
- 18:51Is Obsidian CLI + Agent invocation
- 18:53It's more like a system-level execution chain
- 18:55Rather than a standard plugin
- 18:57Previous solutions were more about humans manually using tools;
- 19:01This layer is more about letting the Agent directly invoke Obsidian's system capabilities
- 19:04Its greatest value can be summarized in three phrases:
- 19:07Saving tokens, higher safety, and stronger automation
- 19:08Why is that?
- 19:11Because it doesn't have the AI scan the entire vault
- 19:15Nor does it let the AI directly and crudely read/write files
- 19:17Instead, through the official CLI
- 19:20It sends instructions to the running Obsidian instance
- 19:21The benefit of doing this is
- 19:24AI doesn't need to repeatedly read massive amounts of context
- 19:27No need to cram the entire vault into the model
- 19:30So token consumption will be significantly lower
- 19:33At the same time, it's safer and more stable
- 19:36Because what's actually executing the changes is Obsidian itself
- 19:39Not an external tool randomly modifying files on the disk;
- 19:44This makes it easier to maintain the consistency of backlinks, templates, tags, and internal states
- 19:47So you can think of it as:
- 19:49Obsidian is not just a note-taking app
- 19:55It starts exposing a layer of system capabilities that can be invoked by an Agent via CLI
- 19:59If earlier solutions were enhancing "how humans use Obsidian,"
- 20:03This layer enhances "how the system does things automatically."
- 20:05Regarding installing and enabling Obsidian CLI
- 20:09We can refer to this official Obsidian CLI help page:
- 20:11It's mainly divided into three steps:
- 20:16Update Obsidian, enable CLI, register CLI
- 20:16Step one
- 20:20First, we confirm Obsidian is updated to a version that supports CLI
- 20:23The official requirement is 1.12 or above
- 20:25But in actual practice
- 20:28Just updating to the latest version is fine
- 20:29Step two
- 20:32We need to turn on the CLI switch inside Obsidian
- 20:35This is essentially telling Obsidian:
- 20:39I allow you to expose a command-line entry point
- 20:41Step three, register CLI
- 20:42In the General settings, we find:
- 20:44Command line interface
- 20:47After clicking to enable, a prompt will pop up
- 20:51Roughly meaning: set up the CLI in the terminal
- 20:53Just click confirm to register here
- 20:54Once registration is complete
- 20:58The terminal will be able to recognize Obsidian commands
- 20:58Finally
- 21:01I'll still use the terminal plugin to open the terminal
- 21:05Then input and execute: obsidian help
- 21:08If it's recognized properly and outputs results
- 21:11That means Obsidian CLI is successfully enabled
- 21:13Another point to note
- 21:16Obsidian CLI does not run detached from Obsidian
- 21:19It requires the desktop Obsidian app to remain open
- 21:21Before letting the Agent officially take over
- 21:26Let's manually run a few Obsidian CLI commands in the terminal
- 21:28To get a feel for what it can actually do
- 21:31Let's try the most intuitive action first:
- 21:32Open today's daily note
- 21:33In the terminal
- 21:36I inputted and executed this command
- 21:39And Obsidian automatically jumped to today's daily note
- 21:42I'll just write some random content here first
- 21:44So it's easier to continue testing later
- 21:45Next, in this note
- 21:47I'll append a task
- 21:50I inputted and executed this command again
- 21:51Going back to the daily note
- 21:55I found that new content has been added to this daily note:
- 21:56CLI test
- 21:58Finally, I'll try a search
- 22:00I input and execute this command
- 22:03The terminal directly returns the paths of relevant notes
- 22:05The key here is
- 22:08AI doesn't need to read the entire vault itself
- 22:11But can use Obsidian's search capabilities
- 22:12To get matched results
- 22:15At this point, we can intuitively feel:
- 22:17This isn't a "simulated operation,"
- 22:20But truly controlling Obsidian
- 22:23Obsidian CLI is highly suited for AI Agents to invoke
- 22:24So then
- 22:28How does the Agent know which commands to use and how?
- 22:29It relies on Agent Skills
- 22:33Here we use Obsidian's official Agent Skills
- 22:38I download the Obsidian skills into the same directory as the current Obsidian vault
- 22:40I tell Claudian: in the current directory
- 22:42Download Obsidian skills for me
- 22:44After AI executes
- 22:47It prompts that Obsidian Skills installation is complete
- 22:49I switch to VS Code to check
- 22:52The Skills file is already in the current vault
- 22:55Now, we enter the core of this section:
- 23:00Utilizing Agent + Obsidian skills + Obsidian CLI
- 23:02To complete an automated task
- 23:04For example: I read this webpage article
- 23:06And save it to the Obsidian vault
- 23:07While generating a reading note and canvas
- 23:09To visually demonstrate the Obsidian CLI workflow
- 23:12Here I'll continue using Claudian to initiate tasks
- 23:13But let me clarify first:
- 23:15Claudian is not the focus of this section
- 23:18Claudian itself can of course directly read and write vault files
- 23:21But what I really want to demonstrate here is another chain:
- 23:25Letting the Agent maximize its use of Obsidian CLI to invoke Obsidian's capabilities
- 23:27Instead of simply bypassing Obsidian
- 23:30To write files directly in the local file system
- 23:31So in this example
- 23:35You can understand Claudian as "the Agent entry point to initiate tasks,"
- 23:39While Obsidian CLI is the actual system interface connecting the Agent and Obsidian
- 23:40I tell the AI as follows:
- 23:42Please use Obsidian CLI
- 23:45To organize this webpage content into my current Obsidian vault:
- 23:49Save the original text, generate a reading note, generate a canvas
- 23:51Put files into the specified folder
- 23:54Do not just write files directly in the file system
- 23:56Webpage and skills are as follows
- 23:59The task wasn't completely successful on the first try
- 24:02For instance, initially the original text and reading note were generated
- 24:04But the Canvas failed to open
- 24:07At this time, I kept having the Agent fix it based on errors
- 24:10Finally, the Canvas was also successfully displayed
- 24:12I used Claudian for demonstration in this section
- 24:15But the focus is actually not Claudian itself
- 24:16As long as it's a local Agent
- 24:19As long as it can invoke Obsidian CLI
- 24:21It can hook into this workflow
- 24:28Like Codex App, Codex's VS Code plugin, Codex CLI, Claude Code, etc.
- 24:30They can all do similar things
- 24:31This way
- 24:34Obsidian is no longer just a note-taking app
- 24:37But a knowledge system that can be automatically dispatched by Agents
- 24:40So, if the previous solutions were enhancing "humans,"
- 24:45This layer is enhancing "the system."
- 24:48Finally, let's summarize: Integrating AI into Obsidian
- 24:49Is not just limited to one way
- 24:54But a continuous upgrade path from "assisted usage" to "system-level automation"
- 24:55In my system here
- 24:58Codex is the most core underlying capability
- 24:59Because it's not just a tool
- 25:01But a real Agent execution engine
- 25:02Of course
- 25:04If you usually use Claude Code mainly
- 25:06You can also just replace Codex with Claude Code
- 25:07Reusing this logic
- 25:10Around Codex, there is already a relatively mature ecosystem
- 25:14So a lot of times we don't need to install an extra bunch of tools
- 25:16Nor do we need to configure APIs everywhere
- 25:18For us, the ideal state is:
- 25:20Try to keep only one AI subscription
- 25:23Minimize the hassle, try to keep capabilities unified
- 25:24This way
- 25:27Only then can Obsidian + AI truly be simple, efficient, and powerful
- 25:29With costs kept low enough
- 25:32If you just want to view Obsidian's underlying files
- 25:34Or batch organize vault files
- 25:37Then you can use the VS Code + Codex plugin
- 25:39To directly operate on the file layer
- 25:42If you wish to preserve the immersive experience inside Obsidian
- 25:44While also wanting to use Codex's Agent capabilities
- 25:48You can invoke Codex CLI via the Claudian plugin
- 25:50If you want to build stronger automation
- 25:52You can have Codex act as the main Agent
- 25:55Controlling Obsidian via Obsidian CLI
- 25:57As for where you initiate tasks
- 26:00VS Code plugins, Obsidian plugins, CLI tools
- 26:02Or standalone apps, all work fine
- 26:04Ultimately, only the entry point is different
- 26:07If you found this video helpful
- 26:09Please like, subscribe, and share
- 26:12If you encounter any problems during hands-on practice
- 26:14Feel free to leave a message in the comments
- 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.