# Obsidian Vault Sync

> Links one folder of an Obsidian vault to a project's memory, the shared notebook every agent of the project reads (see project-memory).

- Area: Desktop app
- Plans: All plans
- Last checked against the product: 2026-10-20
- Web page: https://agentsroom.dev/docs/obsidian-vault-sync

## What it does

Links one folder of an Obsidian vault to a project's memory, the shared notebook every agent of the project reads (see [Project Memory](https://agentsroom.dev/docs/project-memory.md)). What you write in Obsidian becomes memory your agents can read, and what the agents save comes back to the vault as Markdown, with its `links` and unknown YAML properties left intact. No Obsidian plugin, Obsidian button, Obsidian menu, where is Obsidian sync, no Obsidian Sync subscription and no agent running inside the vault: the desktop app watches the folder on disk while it is running and online, even with the panel closed.

Two directions: **Both ways** (vault edits reach the memory, agent notes are written into the folder, and the notes already in the memory are exported too) or **Vault to memory only** (nothing is ever written into the vault). When the same note changed on both sides, or was deleted on one side, that note stops and waits for your choice; every other note keeps syncing. Nothing is resolved by timestamp.

This is different from **Import from Obsidian**, the one-time import offered in the same menu.

**Video (1 min 19 s):** [Obsidian Vault Sync, shown in the real app](https://youtu.be/q-cQzPxDLYM). A vault folder is linked to a project in both ways, an agent started afterwards reads two Obsidian notes, writes a new one, and the note shows up in the vault a few seconds later.

## Where to find it

Desktop, inside a project: the **Project memory** item of the dock (brain icon) opens the memory window; its toolbar carries one **Obsidian** button (the Obsidian logo with a small arrow) that opens a menu with **Import from Obsidian** and **Obsidian sync** (since 2026-10-20; they used to be two separate buttons). A warning sign with a number on that button means conflicts are waiting, a warning sign alone means the last sync failed. The **Obsidian sync** window carries a **Tutorial** link to the video in its header.

## How to use it

1. Open **Project memory**, click the **Obsidian** button of the toolbar, then **Obsidian sync** in its menu.
2. **Choose a vault folder**: the vault itself or one of its subfolders (the vault is the folder that contains `.obsidian`).
3. Pick the **Sync direction**: **Both ways** or **Vault to memory only**.
4. Read the notice (every Markdown note of the folder is shared with everyone who has access to this project's memory), then click **Link this folder**.
5. Start your agents after linking: an agent already running before the link did not read the new notes.

Once linked, the panel shows **Last sync**, **Sync now**, the direction (**Save mode** to change it) and **Unlink**. New notes coming from the vault land under `features/obsidian` in the memory, with their subfolders.

**Conflicts.** Under **Conflicts to resolve**, each note shows the **Obsidian version** and the **Project Memory version**; pick **Use Obsidian version** or **Use memory version**. Both versions are kept until you choose. If either side changes again in the meantime, the choice is refused and you review the updated conflict.

**Another computer.** The link belongs to your account. On a second computer the panel says the project is linked on another computer: click **Locate this folder on this computer** and pick the matching local folder.

**Unlink** stops the sync on every computer of the account and keeps the notes and the vault files.

## Settings

None. The direction is chosen in the panel, per project.

## Agent tools (MCP)

No dedicated tool: agents read and write the synced notes with the usual memory tools.

- `memory_list`, `memory_get`: read the notes, including those coming from the vault.
- `memory_save`: a note saved by an agent is written back into the vault in **Both ways** mode.

## Providers

All providers, no difference: every agent CLI reads the same project memory.

## Mobile

Not available on mobile: the phone has no Project memory screen and a local folder can only be chosen on a computer. Agents driven from the phone still read the synced notes.

## Limits

- One linked folder per project and per account. A folder that overlaps another project's linked folder is refused.
- 2,000 notes, 1 MB per note, 16 MB in total, eight levels of subfolders. Attachments, hidden folders and symbolic links are excluded.
- Syncs only while the desktop app is running and online; a network error or an unplugged disk keeps both versions and retries later.
- A deleted file always asks for a choice; a confirmed deletion moves the file to the vault's `.trash`.
- Exported notes gain an `agentsroom_id` property at the top: it is how a renamed file is recognised, so keep it.
- A note with no `description` property shows "(no description)" in the memory, and agents may not open it: give your important notes a `description`.

## Common questions

- **How do I let Claude Code read my Obsidian notes?** Open **Project memory** in the project, click the **Obsidian** button then **Obsidian sync**, **Choose a vault folder**, pick **Both ways** (or **Vault to memory only**), then **Link this folder**. Start the agent after linking. Video: https://youtu.be/q-cQzPxDLYM
- **Is there a video that shows it?** Yes, 1 min 19 s, a vault linked both ways and an agent reading and writing notes: https://youtu.be/q-cQzPxDLYM
- **Do I need an Obsidian plugin or Obsidian Sync?** No. AgentsRoom works on the folder on disk.
- **Will an agent overwrite my notes?** Not silently: two edits of the same note wait for your choice, and **Vault to memory only** never writes into the vault.
- **My agent does not know about my notes.** It was started before the link, or the note has no `description`: restart the agent, add a `description` property.
- **What is the difference with Import from Obsidian?** The import is a one-time copy; Obsidian sync keeps the folder and the memory in step.

## Related

- [Project Memory](https://agentsroom.dev/docs/project-memory.md): the memory the vault is synced with.
- [Linked folders](https://agentsroom.dev/docs/linked-folders.md): give agents access to another folder of code, not of notes.
