Important: Obsidian must be running for CLI commands to work. The CLI communicates
with the running instance via IPC.
Platform Notes
macOS/Windows: The Obsidian installer typically places the CLI binary in PATH automatically.
Linux: You may need a wrapper script to avoid Electron flag injection that breaks CLI arg parsing. Ensure your wrapper is in PATH before the system obsidian binary. If running as a service, ensure PrivateTmp=false for IPC to work.
π Tips & Best Practices
CLI connects to running Obsidian via IPC singleton lock
For non-interactive use (scripts/cron), ensure Obsidian is running first
move requires the full target path including .md extension
