Obsidian

Obsidian is a local Markdown knowledge base. In braynee it isn't a viewer or a nicety — it is the second brain. Every durable thing lives here as plain text: your Claude Code session history, the settings braynee manages, project context, decisions, clients, goals, distilled notes. You can read and edit all of it without braynee; braynee just keeps it organized and fed back into Claude Code.

Why braynee uses it

A second brain has to outlive any one conversation, stay readable by a human, and be diffable and searchable by a machine. Plain Markdown in a local vault is all three. Obsidian gives that store a UI, a plugin surface, and a link graph — without locking the data into a proprietary format.

How it's set up

You install the Obsidian app yourself (it's a closed desktop app, so braynee can't ship it). From there /braynee:setup:

• scaffolds the PARA structure — 1. Projects/, 2. Areas/, 3. Resources/, 4. Archives/ — and seeds a starter knowledge base;
• writes the CLAUDE.md files that teach Claude Code how to use the vault;
• installs six community plugins into .obsidian/plugins/ (below).

It can only do the last step once it knows your vault path, which is why plugin install happens during setup rather than being bundled.

The six plugins braynee installs

Each runs inside this vault and has its own page:

Connects with

• Tools: QMD indexes this vault · the six plugins run inside it · beads surfaces tasks here
• Concepts: PARA is its structure · Architecture — Pillar 2
• Reference: skills that read and write the vault · hooks that keep it current