Obsidian sync — your agent's work, in your vault
Every file your agent produces — decks, briefs, SOPs — lands in your Obsidian knowledge base. Notes you keep in the vault are visible to the agent as working context. One workspace, two doors.
Set it up once (~10 min)
1. Create a vault token
In the app, open Settings → Channels → Obsidian sync, enter a folder
name (e.g. notes or sop) and press Create vault token. Copy the token right away — it's shown only once. Each
token syncs exactly one workspace folder to one vault; create another token for a
second vault.
2. Install Remotely Save in Obsidian
In Obsidian: Settings → Community plugins → Browse, install Remotely Save and enable it. It's the standard way to sync a vault to a WebDAV server.
3. Point it at your vault folder
In the Remotely Save settings, choose WebDAV and enter:
- Server address:
https://www.getonepress.com/webdav - Username: anything (e.g. your email) — it isn't checked
- Password: the sync token from step 1
Run the sync. Your vault's root is the folder you picked — e.g. a token for notes maps the whole
vault to notes/ in your
workspace. Everything else in the workspace stays out of the vault's reach.
What ends up where
Vault → workspace. Your notes, SOPs, research dumps and templates appear in the workspace the agent already reads — ask "draft the update using my notes from last week" and the material is right there.
Workspace → vault. Agent artifacts land in the vault on the next sync — drafts you can edit by hand, then let the agent pick back up.
Scope & safety. A token only ever reaches the one folder it's bound to — sync mistakes and deletes stop at that folder's boundary, and other workspace files stay untouched. Revoke a token any time and only that vault loses access.
Settings → Channels → Obsidian sync