[verdict][generated prompt][source: obsidian.md]
Can I vibecode Obsidian Sync?
// one session, and a personal version you can actually use
If you already accept local Markdown files, syncing folders across devices is a solved problem; the hard part is not the app, it is conflict-free convenience.
confidence: high
what it is: Paid sync service for a local-first Markdown knowledge base
Buildability index · an editorial game
- Price 5 $/month · per seat weight: plus 1
- Time one sitting weight: plus 3
- Category notes and knowledge no weight
- Moat execution quality weight: minus 1
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site obsidian.md (si apre in una nuova scheda) no weight
The maths works, but not by much: look at what you lose before you start.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
// free tier: Sync itself has no free tier, though the Obsidian app is free.
What you build
Use a local Markdown folder, git/Syncthing/iCloud/Drive for sync, and optional scripts for backlinks/search.
what you need
- local Markdown folder
- Syncthing, Git, iCloud, Dropbox, or similar
- optional mobile file access
Very clean yes; lets the site distinguish app value from convenience subscription.
The prompt
One session with a coding agent and your version runs.
Build me a sync setup for my Obsidian vault to replace Obsidian Sync. Requirements:
- This is plumbing, not an app: the vault is a folder of Markdown files, sync it with
git. Syncthing is the zero-history alternative; use git here because I want history.
- A small watcher (Node + chokidar + simple-git, or a plain bash script on a
systemd/launchd timer, pick the simpler) that debounces 30 seconds after the last
change, commits with an auto message, and pushes to a private GitHub repo.
- On start and every 5 minutes: pull with rebase. On conflict, never lose data: write
the incoming version as <name>.conflict-YYYY-MM-DD.md, keep mine in place, and log it.
- .gitignore for .obsidian/workspace* and .trash so device-local state does not ping-
pong between machines.
- A `vaultsync status` command showing last push/pull time and any outstanding conflict
files.
- Mobile: point a git client (Working Copy on iOS, MGit on Android) at the same repo.
Document that in the README, do not build mobile anything.
- The repo stays private; token in .env or the system git credential helper. No accounts
beyond GitHub, no telemetry, notes stay plain Markdown on disk.
- Out of scope: an encrypted-vault workflow and a version-history UI. git log is the
history.
- README: second-machine setup steps and the conflict-file convention.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- official mobile sync polish
- conflict handling
- version history UI
- encrypted vault workflow
- Obsidian support
Why people still pay
They pay for no-drama sync across devices while keeping Obsidian's local-first model.
moat: Execution quality what a moat is
sync/polish
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Syncthing (opens in a new tab) — Open-source continuous file synchronization that can replace much of Obsidian Sync for tec (alive)
What it costs in a year
5 $/mese 60 $/anno
Listino 5 $ al mese a persona su Obsidian Sync. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
