-
Notifications
You must be signed in to change notification settings - Fork 0
Obsidian Integration
_dream_context/ is a directory of markdown and JSON, shaped like a knowledge graph (memory links to decisions link to features link to knowledge). The most natural way to browse that graph is Obsidian, which is built for exactly this shape.
dreamcontext init scaffolds an _dream_context/.obsidian/ vault config with curated settings:
-
app.json— enables attachment folder, always update internal links, show frontmatter. -
appearance.json— base theme alignment with the dreamcontext brand. -
graph.json— pre-configured node coloring, link forces, and filters so the graph view is useful on open rather than requiring setup.
Open _dream_context/ as an Obsidian vault and you get: wiki-link navigation between files ([[memory#decision-x]] etc.), the Obsidian graph view showing explicit links, backlink panels, and full-text search that operates directly on the markdown. No sync, no plugin, no dependency on Obsidian to run dreamcontext — this is purely a "you can open it this way if you want" integration.
The dashboard also ships with an Obsidian-style search library (dashboard/src/lib/obsidian-search.ts) that implements the same [[link]] and tag-query syntax so searching within the dashboard feels native if you also use Obsidian.
- Why It Exists
- The Problem in Depth
- The Architecture
- The Hook Mechanism
- The Sleep Cycle
- Neuroscience-Inspired Memory
- The Dashboard
- Project task overrides
- Council Debates
- Memory Recall (BM25 over the curated corpus)
- Lab (Insights)
- Automations
- Federation
- Brain Cloud Sync
- Linked Repos
- Obsidian Integration
- CLI Design
- Install & Update
- The Desktop App
- Design Tradeoffs
- What Comes Next