The Tools
braynee is a thin layer over a small, required toolchain. What each tool is, why it's there, and how it gets installed.
braynee doesn't reimplement anything. It wires Claude Code into a handful of tools that already do their jobs well, and gets out of the way. Nothing here is a nice-to-have — every tool on these pages is required. The only optional piece is the email integration.
What you install vs. what the wizard does
You install two things by hand: Claude Code
and the braynee plugin. /braynee:setup handles the
rest, and it's explicit about it:
- It detects what's already on your machine.
- For anything missing, it shows the exact per-OS install commands and asks before doing anything: Install now? — Yes / I'll do it myself / Skip.
- On Yes, it runs them, then re-checks.
Detect, ask, install. No silent changes, and no manual tool-by-tool hunt.
The toolchain
| Tool | Role | How it arrives |
|---|---|---|
| Obsidian | The second brain — the PARA vault, plus its six plugins | You install the app; the wizard scaffolds it and installs the plugins |
| QMD | Search — turns the vault into context | Bundled inside the plugin; nothing to install |
| beads | Agent task memory across sessions | Wizard detects and offers to install |
| Email (optional) | Gmail / ProtonMail for the daily + email flows | Detected only; never required |
The Obsidian page covers the app and links each of the six plugins it installs (Dataview, Tasks, Templater, Calendar, Obsidian Git, Excalidraw) on its own page.
Plus the runtimes the toolchain rides on — git, Node.js, and Python 3 — which the wizard detects and offers to install like any other missing dependency. They're system binaries, so braynee never bundles or shadows them; it just makes sure they're present.
Connects with
- Concepts: Architecture · PARA · The Workflow
- Setup:
/braynee:setup· Getting Started