Obsidian Cli

Obsidian CLI

The official Obsidian CLI (released in v1.12, February 2026) lets you control every aspect of Obsidian from the terminal. It communicates with a running Obsidian desktop instance via IPC.

Read references/command-reference.md when you need specific flags, output formats, or subcommands for any command group. It covers all 130+ commands with full parameter tables and has a table of contents at the top.

Prerequisites

Platform Notes

• macOS / Linux: The obsidian binary is registered in PATH automatically when you enable CLI in settings.
• Windows: Requires an Obsidian.com redirector file placed alongside Obsidian.exe. Must run with normal user privileges — admin terminals produce silent failures.
  • If colon subcommands (property:set, daily:append, etc.) with parameters return exit 127, check that Obsidian.com exists alongside Obsidian.exe. If missing, you have an outdated installer — download the latest from obsidian.md/download and reinstall.
  • Git Bash / MSYS2 users: Bash resolves obsidian to Obsidian.exe (GUI) instead of Obsidian.com (CLI), causing colon+params to fail with exit 127 even when Obsidian.com is present. Create a wrapper script — see Troubleshooting.
• Headless Linux: Use the .deb package (not snap). Run under xvfb. Prefix commands with DISPLAY=:5 (or your xvfb display number). Ensure PrivateTmp=false if running as a service.

Syntax

All parameters use key=value syntax. Quote values containing spaces.

bashCopy code
obsidian <command> [subcommand] [key=value ...] [flags]

Multi-Vault

Target a specific vault by making it the first argument:

bashCopy code
obsidian "My Vault" daily:read
obsidian "Work Notes" search query="meeting"

If omitted, the CLI targets the most recently active vault.

Command Overview

The CLI provides 130+ commands across these groups:

Quick Reference — Most Common Commands

Reading & Writing Notes

bashCopy code
obsidian read path="folder/note.md"
obsidian create path="folder/note" content="# New Note"
obsidian create path="folder/note" template="meeting-notes"
obsidian append path="folder/note.md" content="New paragraph"
obsidian prepend path="folder/note.md" content="Top content"
obsidian move path="old/note.md" to="new/note.md"
obsidian delete path="folder/note.md"
obsidian delete path="folder/note.md" permanent

Daily Notes

bashCopy code
obsidian daily                          # Open today's daily note
obsidian daily:read                     # Print content of today's note
obsidian daily:append content="- [ ] New task"
obsidian daily:prepend content="## Morning Notes"

Search

bashCopy code
obsidian search query="project alpha"
obsidian search query="TODO" path="projects" limit=10
obsidian search query="meeting" format=json   # Returns JSON array of file paths
obsidian search query="urgent" case

Properties & Tags

bashCopy code
obsidian properties path="note.md"
obsidian property:set path="note.md" name="status" value="active"
obsidian property:read path="note.md" name="status"
obsidian property:remove path="note.md" name="draft"
obsidian tags counts sort=count
obsidian tag name="project/alpha"

Tasks

bashCopy code
obsidian tasks                          # All tasks (done + todo) — same as tasks all in v1.12
obsidian tasks all                      # All tasks (done + todo)
obsidian tasks done                     # Completed only
obsidian tasks daily                    # Tasks in today's daily note
obsidian task path="note.md" line=12 toggle
obsidian tasks | grep "\[ \]"           # Workaround: filter to incomplete only

Developer & Automation

bashCopy code
obsidian eval code="app.vault.getFiles().length"
obsidian dev:screenshot path="folder/screenshot.png"  # Path must be vault-relative
obsidian dev:debug on                                 # Required before dev:console
obsidian dev:console limit=20
obsidian dev:errors

TUI Mode

Running obsidian with no arguments launches an interactive TUI (Terminal User Interface):

Common Agent Patterns

Daily Journal Automation

bashCopy code
# Append a timestamped entry
obsidian daily:append content="## $(date '+%H:%M') — Status Update
- Completed: feature branch merge
- Next: code review for PR #42
- Blocked: waiting on API credentials"

Create Note from Template with Metadata

bashCopy code
obsidian create path="projects/new-feature" template="project-template"
obsidian property:set path="projects/new-feature.md" name="status" value="planning"
obsidian property:set path="projects/new-feature.md" name="created" value="$(date -I)"
obsidian daily:append content="- Started [[projects/new-feature|New Feature]]"

Vault Analytics Script

bashCopy code
obsidian files total                    # Total file count
obsidian tags counts sort=count         # Most used tags
obsidian tasks | grep "\[ \]"          # Incomplete tasks across vault
obsidian orphans                        # Notes needing integration
obsidian unresolved                     # Broken links to fix

Search and Extract for AI Processing

bashCopy code
obsidian search query="meeting notes" format=json | jq '.[]'
obsidian read path="meetings/standup.md" | grep "Action item"

Sync Management

bashCopy code
obsidian sync:status                    # Check sync health
obsidian sync:history path="important.md"  # Version history
obsidian sync:restore path="important.md" version=3  # Rollback

Execute Obsidian Commands

bashCopy code
# Find a command ID, then execute it
obsidian commands | grep "graph"
obsidian command id="graph:open"

# Open settings, trigger a plugin action
obsidian command id="app:open-settings"
obsidian command id="dataview:dataview-force-refresh-views"

Tips

1. Paths are vault-relative — use folder/note.md, not absolute filesystem paths.
2. create paths omit .md — the extension is added automatically.
3. move requires full target path including .md extension.
4. Pipe-friendly — plain text output works with grep, awk, sed, jq.
5. JSON output — use format=json on search for a JSON array of file paths. The files command does not support JSON output.
6. Stderr noise — GPU/Electron warnings on headless are harmless; filter with 2>/dev/null.
7. daily:prepend inserts content after frontmatter, not at byte 0.
8. Use eval to run arbitrary JavaScript against the Obsidian API (app.*).
9. template:insert inserts into the currently active file in the Obsidian UI — it does not accept a path= parameter. If no file is open, it returns Error: No active editor. Open a file first. To create a file from a template via CLI, use obsidian create path="..." template="..." instead.
10. property:set stores list values as strings — value="tag1, tag2" writes a literal comma-separated string, not a YAML array. For proper array fields, edit the note's frontmatter directly (e.g. via read → modify → create --force) or use eval to call the Obsidian API.
11. eval requires single-line JavaScript — multiline JS passed inline fails with a token error. Write the script to a temp file instead:

    bashCopy code
    cat > /tmp/obs.js << 'JS'
    var files = app.vault.getMarkdownFiles();
    files.length;
    JS
    obsidian eval code="$(cat /tmp/obs.js)"
    

12. Multi-vault targeting may not work in all environments — obsidian "My Vault" command can return Error: Command "My Vault" not found on some setups. If this happens, omit the vault name (CLI targets the most recently active vault) and switch vaults manually in the Obsidian UI.
13. When colon subcommands are unavailable (e.g. Windows Git Bash without wrapper), prefer non-colon alternatives: use properties instead of property:read, and obsidian daily:path + append instead of daily:append.

Troubleshooting