Obsidian Sync now has a headless client

Original Article ↗ Hacker News Discussion ↗

Use cases for headless Obsidian Sync

  • Enables server-side workflows without running the Electron app: backups, website publishing, research pipelines, scheduled automations, and feeding LLM/“agentic” tools from a vault.
  • Lets people who only use Obsidian on mobile still sync vaults to servers or desktop tools (e.g., edit notes in Neovim while relying on Sync for iOS).
  • Helpful for team/shared vaults on servers and for setting up web interfaces or blogs powered by an Obsidian vault.

Why not just Git/Dropbox/Syncthing/etc.?

  • Many run vaults on generic sync: Git (including auto-commit plugins), Syncthing, Nextcloud, Dropbox, iCloud, Backblaze/S3, CouchDB-based Livesync, Resilio, NAS tools, etc.
  • Reported issues with third-party sync: iCloud corrupting or losing notes, sync conflicts with Syncthing, complex Livesync setup and fragility. Others say these work “great” once tuned.
  • Obsidian Sync is praised as “it just works,” especially across platforms and on mobile, with integrated UI for status, conflicts, sharing, per-device settings, and end‑to‑end encryption. Critics find the subscription expensive and prefer self-hosting.

iOS and platform constraints

  • On iOS, background syncing and generic filesystem access are constrained; native iCloud or in‑app sync gets preferential behavior. This makes Obsidian Sync attractive compared to Git/Syncthing there.
  • Some argue iOS storage is still “pluggable” (e.g., via git clients), but others note that built-in apps (Notes) can’t be redirected, and third-party sync often breaks or can’t run reliably in the background.
  • Google Drive integration on iOS is a sore spot: users want to pick a Drive folder as a vault, but this isn’t supported; plugin-based workarounds don’t work natively on mobile.

Version history, conflicts, and limits

  • Obsidian Sync includes version history, but retention is capped (1–12 months depending on plan), which some see as a blocker vs. Git’s unlimited history.
  • Sync conflict handling: Markdown is merged with a diff algorithm; other files are “last modified wins”; JSON settings are merged by keys.
  • Some combine Sync for convenience and Git for long-term archival.

CLI, automation, and AI workflows

  • A separate Obsidian CLI (requires the full app) can run commands, search, read notes, and help debug/build plugins by accessing the Obsidian index.
  • Users combine CLI + headless sync + AI tools (especially Claude) for: RAG over vaults, semantic search, automatic journaling, D&D campaign management, and task-like workflows.
  • Debate over whether a dedicated CLI is needed since notes are plain Markdown; others point out value from Obsidian-specific indices, link graph, and commands.

Other product wishes and critiques

  • Requests: syncing dotfiles (e.g., .claude), scoped tokens or subdirectory‑only access for agents, webhooks on vault changes, Docker/Podman packaging, and single-file editing without creating a vault.
  • Mixed views on Obsidian’s “second brain” features like the knowledge graph and Canvas: some see them as eye-candy, others as integral; some complain about plugin safety and lack of a coherent vision.