# brain.aide cookbook

recipes for the brain plugin interface.

# pick a recipe from the rail. each one stands alone — no need to read top-to-bottom.
# the skeleton generator on the right stays sticky so you can experiment as you read.

RECIPE

quickstart

Wire the bundled Obsidian default in three commands. Total time: under two minutes if you already have a vault.

step 1

install + scaffold

Creates .aide/ and pre-fills .aide/config/brain.aide with the obsidian template. The args list lands with one YAML null — that's the vault path slot.

step 2

wire the slot

Inside Claude Code. AIDE asks for your vault path, edits brain.aide, runs sync, and tells you to restart. Sync is what actually writes the brain entry into .mcp.json.

step 3

restart, then seed

After restart, run /aide:brain config a second time. This time the args list has a string, so the seeding flow runs — it presence-checks the four entry-point artifacts and writes any that are missing.

✓ brain ready. boot reporter shows ok; the orchestrator advances; /aide works.

STICKY · LIVE GENERATOR

brain.aide preview

---
name: obsidian
mcpServerConfig:
  command: npx
  args:
    - "@bitbonsai/mcpvault"
    -
---

<!-- aide-orientation-start -->
Your brain is an Obsidian-backed knowledge store. Use `mcp__brain__read_note`
to open files by their brain-relative path. Use `mcp__brain__search_notes`
for keyword queries across every note in the store.

The store has four entry-point artifacts:
  - `coding-playbook/coding-playbook.md`
  - `coding-playbook/study-playbook.md`
  - `coding-playbook/update-playbook.md`
  - `research/research.md`

Start from the relevant entry-point for your task, follow references it lists
to deepen context, and stay in scope.
<!-- aide-orientation-end -->

<!-- aide-config-start -->
You are completing the wiring of an Obsidian brain. The required value is
the absolute path to the user's Obsidian vault, to be placed at the last
entry of `mcpServerConfig.args`.

Steps:
1. Read brain.aide and quote the last entry of args.
2. If YAML null → WIRING flow: ask for vault path, edit brain.aide, run sync, STOP.
3. If string path → SEEDING flow: write each entry-point artifact via
   `mcp__brain__write_note` from the seed-section bytes.
<!-- aide-config-end -->

(... four seed sections ...)