Nearly every Obsidian guide assumes you showed up to take notes — fair, it is a Markdown editor — but the people who stay discover that notes are the least interesting thing in the vault. Nolen Jonker’s piece at XDA on replacing an entire productivity workflow with one vault is the best recent tour of why: the vault is just a folder of plain Markdown and JSON on your disk, which means every other tool you own — git, sync clients, backup jobs, and increasingly your agents — can read and write it too. Once that clicks, Obsidian stops being a notes app and becomes the user interface for a folder that everything else can participate in.
A dashboard layer without a plugin stack
Jonker’s first move is a folder called /index/: separate Markdown files for active projects, this week’s priorities, stalled work, orphaned notes. Each dashboard is nothing but a table and some wikilinks, so it renders natively in Obsidian — no Dataview, no plugin stack — and an agent (Claude Code, in their setup) crawls the vault’s frontmatter and file modification times to keep the tables honest. Add a deadline to a project brief, ask for a regenerate, and this-week.md picks it up.
Project trackers die of two failure modes: nobody updates them, and nobody opens them. A dashboard that lives with the work kills the second one — it’s one click from the notes you’re already in — and an agent that regenerates it from the source files kills the first. The information was already in the vault, scattered across folders; it just needed a view on top of it. Bonus: the index folder becomes the spine of the graph view, which used to be a disconnected mess and is now something you can actually navigate.
The vault as a cache, not just a source
Most AI-plus-notes setups run in one direction: feed your notes into a chatbot, get an answer, lose the answer. The pattern worth copying runs the other way. A /Cache/ folder holds the synthesis-heavy answers your agent has already produced — named Markdown notes — and a root instruction file (CLAUDE.md) tells the agent to check that folder before re-reading the same thirty raw sources.
The first payoff is arithmetic: you stop burning tokens re-deriving the same synthesis every time you ask a variant of the same question. The second payoff matters more. Those cache notes are ordinary files in an ordinary folder, so they ride the same sync and backup pipeline as everything else. If the provider’s app went away tomorrow — or just got worse — the work the agent did for you is still yours: on your disk, greppable by anything. Chat history in a vendor’s app is rent; a Markdown cache in your own vault is ownership.
Canvas is JSON, so diagrams become programmable
The Canvas whiteboard looks like a drawing tool, but a .canvas file is a small JSON document — the JSON Canvas spec has been public since March 2024: one array of nodes, one array of edges, a handful of node types, coordinates in pixels. That’s simple enough for an agent to write correctly, which changes what the tool is for. Low-fi wireframes, UX flows, persona maps: generate the JSON in your design directory where the agent already has context, copy the file into the vault, and refine it by hand in the app. Opening a full design tool for a rough sketch is overkill; opening a programmable one is a workflow.
Ops notes: keep generated and hand-written apart
Once agents write into your vault, you owe the folder the same discipline you’d give any generated artifact tree:
- Scope by folder. Generated content lives in
/index/and/cache/; your own writing lives everywhere else. Don’t hand-edit generated files — fix the source and regenerate, the same rule as any Terraform output. - Put the vault in git (or at least snapshot it). Agent writes become reviewable diffs instead of silent mutations, and “regenerate the dashboard” becomes reversible.
- Your backup pipeline already covers it. The vault is a folder, so Syncthing, rsync or restic handle it with zero new machinery — no export button, no lock-in ritual, no vendor watching your export limits.
The note-taking is fine. It’s just the least of it. What replaces a whole workflow stack is the substrate: a folder of plain files your editor, your scripts, your sync, your backups and your agents can all treat as home turf. Apps are rentable; that folder is yours.