Obsidian × REM · Deep Integration

Your vault,
thinking while you sleep.

Live two-way sync. Dream insights land in your notes as you work. Daily notes become queryable memory. Backlinks merge into the REM graph. Built as a first-class integration — not a plugin afterthought.

Connect your vault How it works
The flow

Notes in. Dreams out. Graph merged.

Your Obsidian vault becomes a live substrate. Every edit streams to REM. Every dream insight streams back. The graph is federated — backlinks, tags, and frontmatter all become first-class REM memory.

01 · INGEST
Vault → REM
Folder scan + file-watcher. Daily notes, MOCs, backlinks, frontmatter — all become typed memory in under 3 seconds per change.
02 · DREAM
REM consolidates
9 strategies run nightly. Patterns extracted, contradictions resolved, connections proposed, goals tracked. No prompting.
03 · WRITE-BACK
REM → Vault
Insights land in ~/REM Dreams/ as new notes or proposed edits. You keep the final say — every suggestion is diff-reviewable.
04 · FEDERATE
Graph merge
Obsidian backlinks merge with REM's knowledge graph. Query from either side — one intelligence, two surfaces.
Bidirectional

Nothing one-way. Nothing lossy.

Most integrations import once and drift. REM keeps your vault and your memory coherent forever — with conflict resolution, audit trails, and per-folder policies.

Obsidian Vault
Source of creation
New note · Daily/2026-04-17.md
Edit · Projects/REM Labs.md
Backlink · [[Dream Engine]]
@tag · #fact #decision
Frontmatter · status: active
→←→←→
REM Memory Layer
Source of intelligence
Parsed → typed memory (@Fact, @Decision)
Embedded + indexed in graph
Dream strategies run nightly
Insights written back as proposed notes
Graph merged with existing REM memory
Nine deep hooks

Every Obsidian primitive, natively understood.

Not a generic file sync. REM reads your vault the way Obsidian does — and then adds consolidation, federation, and reactivity on top.

Live sync
File-watcher streaming
Sub-3-second propagation on edit. No manual refresh, no cron jobs. Uses native fs events — invisible overhead.
Daily notes
Auto-ingest & summarize
Every daily note becomes a typed capture. At day-end, REM generates a dream summary written back as yyyy-mm-dd — Summary.md.
Backlinks
Graph federation
Your [[wikilinks]] merge into REM's knowledge graph. Queries traverse both sides — Obsidian links and REM associations as one mesh.
@Primitives
Typed tag extraction
Write @fact, @hypothesis, @decision, @goal, @model and REM auto-types the memory. Obsidian stays pure Markdown.
Dream write-back
Insights as notes
Nightly dream outputs become notes in ~/REM Dreams/ with frontmatter. Accept, reject, or merge — diff-reviewed like code.
Frontmatter
YAML as structured memory
Frontmatter keys become queryable metadata. status:, tags:, project: — all searchable in the REM API.
Per-folder policy
Granular sync scopes
Include, exclude, or read-only per folder. Work/ syncs. Personal/ stays local. Archive/ one-way to REM only.
Conflict merge
CRDT-style resolution
Edit a note on three devices. Dream while offline. Reconnect — REM resolves cleanly, keeping every edit auditable in the branch log.
Local-first
Vault never leaves disk
Self-host mode: the REM agent runs locally and talks to your vault directly. Zero cloud hop for private vaults — still get dream consolidation.
One command to start

Connect in 30 seconds.

From the REM console, point at your vault root. Or run the CLI. REM reads, indexes, and schedules the first dream cycle tonight.

# one-line CLI bootstrap $ npx @remlabs/cli obsidian connect ~/Documents/MyVault # or programmatic SDK import { remlabs } from '@remlabs/sdk'; await remlabs.obsidian.connect({ vault: '~/Documents/MyVault', mode: 'bidirectional', // or 'read-only' / 'write-only' dreamOutDir: 'REM Dreams', // where write-back lives includeGlobs: ['**/*.md'], excludeGlobs: ['Private/**', '_archive/**'], scheduleDream:'0 3 * * *' // nightly @ 3am local }); # query from anywhere const ideas = await remlabs.memory.recall('open threads on REM launch'); // → surfaces notes from both Obsidian + native REM memory + nightly dreams
Production spec

Built for vaults of every size.

Tested against vaults from 100 notes to 100,000. No indexing freeze, no memory bloat, no sync loops.

<3s
Edit → REM propagation
100k+
Notes per vault supported
9
Dream strategies, auto-scheduled
0
Cloud hops in self-host mode

Stop re-reading your own notes.

Obsidian stores what you wrote. REM remembers, connects, and evolves it. Connect your vault — wake up with insights you didn't have to ask for.

Connect your vault Integration docs