CLI · Knowledge and documents · Obsidian
Obsidian CLI
Search, read, create and append to notes in a local Obsidian vault from a terminal or script, through the running desktop app.
Wrong vault or file. Commands default to the active vault and file. Scripts that omit vault= and path= can edit a different note than intended.
The five-point review
Judgment, not a score. Documentation checked 2026-10-21.
- Value
- Use it when an agent or script should work with your notes through Obsidian rather than raw files, for example to search with Obsidian’s own index, append to today’s daily note or list open tasks. Because a vault is plain Markdown, read-only jobs can also just read the folder.
- Differentiation
- Appending to daily notes from scripts; Searching a vault with matching lines; Listing tasks, tags and backlinks. The evaluation below states what was actually executed.
- Replaceability and switching
- Review the related entries for alternatives. Commands, response schemas and authentication can differ; a shared protocol does not guarantee interchangeable behavior.
- Ease and technical aptitude
- Obsidian desktop app with the 1.12.7+ installer Command line interface enabled in Settings → General and registered on the PATH The app running, or launched by the first command
- Interoperability and portability
- None for local vaults; Sync and Publish commands use the signed-in Obsidian account in the app. Create, overwrite, append, move, rename and delete notes; install plugins and themes; run JavaScript with eval. Access to an API or MCP tool is not proof of complete data export. Verify the required read/write operations and migration coverage separately.
Connections: MCP connections · APIs · Portability and vendor lock-in.
Understand the tool
What it does.
The Obsidian CLI is the obsidian command that ships with the desktop app from the 1.12 installer. It controls a running Obsidian instance: daily notes, search with line context, file reads and writes, properties, tasks, links, templates, plugins, Sync history and Publish. A terminal interface adds autocomplete and history.
Why use it?
Use it when an agent or script should work with your notes through Obsidian rather than raw files, for example to search with Obsidian’s own index, append to today’s daily note or list open tasks. Because a vault is plain Markdown, read-only jobs can also just read the folder.
A useful fit for
- Appending to daily notes from scripts
- Searching a vault with matching lines
- Listing tasks, tags and backlinks
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Log a decision to today’s note
A founder wants agent summaries recorded in the daily note without opening the app.
- Target the vault explicitly with vault=.
- Run daily:append with the reviewed summary as content.
- Open the note and confirm the entry landed in the right place.
Intended outputA dated, searchable record in the vault.
Use case 02
Find every open task on a project
Before a weekly review, someone needs the outstanding tasks across project notes.
- Search the project folder with search:context.
- List incomplete tasks with tasks todo verbose.
- Review the list before marking anything done.
Intended outputA task list with file paths and line numbers.
A concrete starting point
Search a vault and show matching lines
Replace Notes with your vault name. Prints up to five files with the matching lines as path:line: text.
obsidian vault="Notes" search:context query="meeting notes" limit=5What this can change
Reads the vault through the running app and launches Obsidian if it is closed. Does not change notes.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- Obsidian desktop app with the 1.12.7+ installer
- Command line interface enabled in Settings → General and registered on the PATH
- The app running, or launched by the first command
- Authentication
- None for local vaults; Sync and Publish commands use the signed-in Obsidian account in the app.
- Can read
- Notes, properties, tasks, links and history in the targeted vault
- Can write or change
- Create, overwrite, append, move, rename and delete notes; install plugins and themes; run JavaScript with eval
- Network and data flow
- None for local vault commands
- Obsidian Sync and Publish services for sync and publish commands
- Approval and control
- The CLI has no built-in confirmation for writes. Require approval in the calling agent for overwrite, delete, plugin installs and eval.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Windows, macOS and Linux desktop installs
- Requires a running desktop app; not a headless server tool
- Text, JSON, CSV or TSV output on many list commands
Costs and account requirements
The CLI is part of the free Obsidian app. Sync and Publish commands need those paid add-ons.
Current pricing or plan information ↗Obsidian terms of service
The CLI ships inside the proprietary Obsidian app; no open-source license is asserted.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Wrong vault or file
Commands default to the active vault and file. Scripts that omit vault= and path= can edit a different note than intended.
Code execution
eval runs JavaScript inside the app and plugin:install adds third-party code. Keep these out of agent tool lists unless reviewed.
Where it may fall short
Observed behavior · 2026-10-21
Runtime and security findings.
Not run: the Obsidian CLI controls a running Obsidian desktop app with a vault, and the review environment had neither, so no command was executed.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Documented concern
Commands act on the active vault by default
Without vault=, the CLI uses the vault in the current folder or the active vault, and many commands default to the active file.
In practice: Pass vault= and path= explicitly in scripts so an agent cannot edit the wrong note.
Documented concern · medium severity under stated conditions
Write and developer commands are powerful
The CLI can overwrite or delete files, install community plugins and run JavaScript in the app with eval.
In practice: Give agents read and search commands by default; require approval before create overwrite, delete, plugin:install or eval.
Version, environment and fixture
- Version or deployment
- Not observed (documentation requires the 1.12.7+ installer)
- Tested target
- obsidian command registered by the Obsidian desktop app (not installed)
- Artifact identity
- Not available: no binary or endpoint was obtained or contacted for this record.
Checks and results
1 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free help outputCould not complete
- Method
obsidian help in a terminal after enabling Command line interface in Settings → General.- Expected
- The CLI lists its commands; the first command launches Obsidian if it is not running.
- Observed
- Not run: the CLI is shipped inside the desktop app installer and needs the app running, and IonBin had no desktop session with Obsidian installed for this review.
Practical caveats
- Behavior is as documented by Obsidian; none was observed.
- Obsidian Headless is a separate client for Sync and Publish that runs without the desktop app; it was not evaluated here.
What this evaluation does not establish
- Any CLI command, including help, search, read, create and delete, because the desktop app was not installed or running.
- Vault targeting, plugin installation, eval, Sync and Publish commands, and behavior on Windows, macOS and Linux registration paths.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
First-party CLI for Ion’s top-pick local notes app. Ranked after established developer CLIs because it needs a running desktop app and was not executed in this review.
The number is an editorial starting order within the cli tools collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Official CLI documentation
- Headless client documentation
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 21, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official Obsidian CLI documentation ↗obsidian.md
- Obsidian Headless (open beta) ↗obsidian.md
- Obsidian pricing ↗obsidian.md
- Obsidian 1.12 release notes introducing the CLI ↗obsidian.md