Obsidian Plugin — Open Source

Keep your AI /docs and Obsidian specs
in sync

Bidirectional sync between your Obsidian vault and local project folders. Your AI IDE reads fresh docs. You edit in Obsidian. Everything stays aligned.

Get Started Pack View on GitHub
Obsidian vault
LOCAL SYNC
repo/docs (AI reads)

The problem with AI + docs today

Your specs live in Obsidian. Your AI reads /docs. They drift apart.

Problem

AI IDE reads stale /docs

Solution

Local Sync keeps /docs fresh from your vault — always current.

Problem

Manual copy between Obsidian and repo

Solution

Auto-sync on change — watch mode keeps both sides updated without lifting a finger.

Problem

Afraid to let agents write to vault

Solution

Conflict resolution + dry-run preview + automatic backups before every overwrite.

How it works

Four steps. Two folders. Zero friction.

1

Map

Point vault folder ↔ external folder

2

Sync

Run manually or enable auto-sync

3

Edit anywhere

Obsidian or IDE — changes flow both ways

4

AI reads fresh context

Cursor, Claude Code, agents see current docs

mapping config
Vault folder: /specs/project-x
External folder: ~/projects/project-x/docs
Direction: ◄──► Bidirectional
Auto-sync: On change

Use cases

Three workflows where Local Sync shines.

Cursor / Claude Code

  • Write your PRD in Obsidian — it appears as /docs/PRD.md in repo
  • Agent reads fresh PRD on every request — no stale context
  • Edit PRD in Obsidian → agent sees changes without rebuild
workflow
Obsidian → edit specs/project-x/PRD.md
↓ auto-sync
repo → /docs/PRD.md updated
↓
Claude → reads /docs/PRD.md → fresh context

Shared specs, zero friction

  • Team writes specs in Obsidian — the tool they already know
  • CI/CD reads /docs from repo — single source of truth
  • Nobody copies files manually — ever
workflow
PM → updates spec in Obsidian
↓ auto-sync
repo → /docs/spec.md updated
↓
CI/CD → deploys with fresh docs
↓
Dev → IDE reads current spec

Team Relay + MCP

  • Obsidian vault as your team’s knowledge base
  • Team Relay MCP gives agents scoped read/write to vault
  • Local Sync keeps a local copy of docs in sync with vault
Learn more about Team Relay
architecture
Obsidian vault (knowledge base)
  ├─ Team Relay MCP → agents read/write
  └─ Local Sync → repo/docs
↓
Both paths stay in sync — always consistent

Get your AI workflow running in 5 minutes

Install the plugin, pick your AI tool, get pre-configured rules.

1

Install

Install via BRAT

Pending Community Plugins listing. Currently available via BRAT.

2

Pick your AI tool

.claude/CLAUDE.md 
## Documentation Sync Rules

This project uses EVC Local Sync to keep `/docs` in sync with an Obsidian vault.

### When working with /docs:
- Always read the current state of files in `/docs` before modifying
- After changes to specs or documentation, update the corresponding file in `/docs`
- Use clear commit messages referencing which doc was updated
- Do NOT delete files from `/docs` without explicit confirmation

### File structure:
- `/docs/PRD.md` — Product Requirements (source of truth in Obsidian)
- `/docs/architecture.md` — Technical architecture decisions
- `/docs/changelog.md` — Auto-updated changelog

### Sync behavior:
- Changes in `/docs` are automatically synced to Obsidian vault
- Changes in Obsidian are automatically synced to `/docs`
- Conflicts are resolved by keeping both copies (manual merge needed)
.cursor/rules/docs-sync.mdc 
---
description: Rules for working with /docs synced via EVC Local Sync
globs: docs/**/*.md
---

# Documentation Sync Rules

The `/docs` folder is bidirectionally synced with an Obsidian vault via Local Sync.

## Rules:
- Read `/docs` files before making changes to understand current state
- Update `/docs` when modifying project specs or architecture
- Never delete `/docs` files without explicit user confirmation
- Reference `/docs/PRD.md` as the source of truth for requirements
.windsurfrules 
## /docs Sync Rules
This project syncs /docs with Obsidian via EVC Local Sync.
- Read /docs before modifying specs
- Keep /docs updated when changing architecture or requirements
- /docs/PRD.md is the source of truth
- Never delete /docs files without confirmation
3

Get the full Starter Pack

Get Starter Pack on Spark

All configs + quickstart guide in one bundle. Free.

Features

Bidirectional sync

Vault to external and back. Changes flow in both directions.

Multiple mappings

Different projects, different folders. Map as many as you need.

Conflict resolution

Keep both, overwrite, or prompt. You decide the strategy.

Dry-run preview

See exactly what changes before syncing. No surprises.

Auto-sync

On change, on startup, on schedule. Set it and forget it.

Backup before overwrite

Files are never lost on conflict. Automatic backup every time.

How it compares

Local Sync vs the alternatives.

Local Sync Folder Bridge Manual copy Git submodules
Bidirectional ✓ ✓ ✗ ✗
Conflict resolution 3 strategies Basic — Merge conflicts
Auto-sync ✓ ✓ ✗ ✗
Dry-run preview ✓ ✗ — —
AI workflow presets ✓ ✗ ✗ ✗
Backup on overwrite ✓ ✗ — —

Open source. MIT license. 100% local — your data never leaves your machine.

Part of AI-native Toolbox

Team Relay

Need team access + MCP for agents? Real-time collaboration and web publishing for Obsidian.

Spark

Discover AI workflows, prompts, and agent skills. The marketplace for AI-native tools.

Community

Questions? Ideas? Join the discussion on Telegram.