Comment by scalemaxx
3 hours ago
I use Obsidian with my Claude (and Codex) but not sure what additional value the CLI would provide since it's just markdown files. What am I missing that a CLI provides for AI? And not sure how the sync fits into it unless there's a copy of the vault that the AI is working with over CLI? Can use a tip.
The headless sync is the key piece here imo. The scenario is: you have a VPS or server running your AI agents, and you want them to read/write to your Obsidian vault without installing the full Electron app on a headless linux box.
Before this, your options were either syncthing (works but no conflict resolution that understands Obsidian's link format), git (works but terrible on mobile), or just not syncing and manually copying files around.
Now you can run obsidian-headless on your server, it syncs via Obsidian Sync, and your agents just read/write markdown files locally. Changes propagate to your phone and laptop automatically. The CLI part is less important than the headless sync part for this use case.
I've been doing something similar with a janky rsync cron job and it breaks constantly when I edit the same file on my phone. This is a proper fix for that.