Claude Code forgets
everything.
Every session starts from zero. No memory of yesterday, nothing to pick back up. braynee gives it a second brain — scroll on, and watch how.
- 18
- skills
- 41
- hooks
- 15
- CC events
- 6
- agents
Brilliant. And amnesiac.
Four things break the same way for everyone using Claude Code. braynee quietly fixes each one — nothing to remember, it just happens while you work.
Context dies between sessions
Close the terminal and yesterday's work is gone. You re-explain the project every morning.
Next time you open Claude, it already has your last note, your branch, and where you left off — before you type a word.
No persistent memory
Claude relearns your preferences, decisions, and conventions every single time.
braynee keeps a memory of your decisions and how you like to work, and reminds Claude to check it before it guesses.
Knowledge goes nowhere
Good decisions and research evaporate into a transcript you'll never read again.
Every session is saved to your own Obsidian vault and stays searchable forever — by you, and by Claude.
Task continuity breaks
What was I doing? Which branch? What's blocked? Multi-session work falls apart.
Your tasks live in one place that always knows the answer — and it survives even a context wipe mid-session.
Today the loop is broken.
Close the terminal and the thread is cut. Tomorrow you re-explain everything from zero.
$ claude — without braynee
context: (empty)
memory: (none)
“what were we doing?”
→ re-explain the project
$ claude — with braynee
✓ session note loaded
✓ branch + 3 prior sessions
✓ memory searched first
→ resume mid-thought
← → · drag · dots — 8 slides, each one moves
It reads what Claude already knows.
Most plugins add a few commands and forget everything when the session ends. braynee goes the other direction — it audits Claude Code's settings, reads its history across your project folders, and turns that into durable context in your Obsidian vault.
What it reads
- Settings & configYour ~/.claude settings, hooks, permissions, and CLAUDE.md — audited so it works the way you've already set Claude up.
- TranscriptsThe raw conversation transcript Claude Code writes to disk for every session.
- SessionsWhat actually happened in each one — decisions made, files touched, where you left off.
- ProjectsAcross every project folder on your machine, not just the repo you're in right now.
- What you're on nowThe repo, branch, and task in front of you become the frame for everything it pulls.
All read and audited straight from the source— Claude Code's own files. You feed it nothing.
braynee
audits · structures · persists
Lifecycle hooks fire on every event — no command from you. It makes sense of the inputs and writes them down.
Your Obsidian vault
Session notes
a record of every project Claude works on
Memory
decisions and preferences, kept and resurfaced
Tasks
tracked in beads + TaskNotes, mirrored to the vault
inputs Claude Code already produces → braynee → a vault that outlives the session
Why that's different
Most plugins
braynee
Bolt on a handful of slash commands you have to remember to run.
Runs on Claude Code's lifecycle hooks — nothing to type, it just fires as you work.
Stateless — each session starts from zero, blind to the last one.
Reads Claude Code's own settings and history for real context, across folders.
Whatever it figures out dies when you close the terminal.
Writes it all to your own Obsidian vault — plain markdown, durable, searchable.
Watch a session fire.
braynee hooks into all 15 of Claude Code's lifecycle events — 41 hooks in total, none you ever call by hand. Here are the moments you'll actually feel. Step through a single session.
A day with braynee — what fires, when
09:00
Morning
You open Claude Code and it's already caught up — your note, your branch, yesterday's thread, all there before you type. (SessionStart)
11:30
Deep work
You pick up a task and it auto-branches; every change is tracked in three places, with a gentle nudge to commit at a healthy pace.
15:00
Compaction
The context window fills and resets — braynee saves your goal and open work, then hands it right back. Nothing is lost mid-thought.
18:00
EOD
You stop for the day; braynee closes the session note with the outcome and saves the whole thing — searchable tomorrow. (SessionEnd)
SessionStart
The moment you open or resume Claude Code
What braynee does
braynee loads your last session note, your branch, and the threads from earlier sessions — then surfaces the tasks you had open.
makes sure Obsidian is running · surfaces your beads work queue
Why it helps you
Claude is already caught up before you type a word.
9 hooks fire here — automatically, nothing you type.
grep is dead.
Asking 'where did we cover that?' the old way is slow and noisy. braynee answers it in seconds — a few ranked passages instead of a wall of files. Same question, both ways.
✗ without braynee
✓ with braynee
The grep side is illustrative; the right side is real qmdoutput — the actual RSC-bug fix recovered from this site's own session transcript.
It keeps the thread.
Come back to a project after a few days. Without anything tracking it, you rebuild the picture from scratch. With braynee, it just tells you where you were.
✗ without braynee
✓ with braynee
The right side is real bd output from this repository's own tracker.
18 skills for the moments you know.
Slash commands that drive the vault. Each flagship below is real captured output from running that skill against this very site while building it — then scan the full set.
✗ without braynee
✓ with braynee
The right side is real bd / qmd output captured from this repository while building it.
All 18 · generated from the installed plugin
/braynee:clientsClient relationship management. Look up client context, log engagement notes, track status, and prep for meetings/braynee:dailyOpen, create, or update today's daily note. Review yesterday, plan today, log progress/braynee:excalidrawCreate Excalidraw diagrams in Obsidian using the ExcalidrawAutomate (EA) API. Generates .excalidraw files saved directly to the vault — no external tools needed, Obsidian renders them natively. Two modes: (1) Single diagram on demand for any workflow, architecture, process, or data model — trigger on "diagram this", "draw a flowchart", "create an architecture diagram", "visualize this", "make an Excalidraw". (2) Full codebase walkthrough — autonomously reads a codebase and produces a complete visual system documentation (architecture, data flow, sequence, ER) plus interlinked Markdown notes — trigger on "document this codebase", "walk through this system", "diagram this app", "map out this repo", "create documentation for this project"/braynee:healthRun a Brain Check — audit your second brain across Setup, Connections, Memory, and Inbox/braynee:insightfulGenerate a comprehensive insights report from ALL Claude Code conversations across ALL projects. Covers every session ever, not just recent ones/braynee:obsidian-basesCreate and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries/braynee:obsidian-cliInteract with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM/braynee:obsidian-markdownCreate and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax/braynee:prdAuthor and manage Product Requirements Documents (PRDs) under "2. Areas/Product Manager/PRDs/". Scaffolds new PRDs against the braynee schema, audits existing ones, and seeds beads issues from the Acceptance Criteria section/braynee:querySearch your vault using QMD (semantic + BM25). Find notes, decisions, resources, and connections/braynee:recallLoad context from previous Claude Code sessions and vault notes. Temporal queries scan JSONL session files by date. Topic queries use QMD BM25 search with query expansion. Every recall ends with "One Thing" — the single highest-leverage next action/braynee:session-backfillBackfill structured session summaries from Claude Code .jsonl transcripts into the vault's per-project Sessions folder. Distills each CC session into TL;DR / Goal / Outcome / Decisions / Blockers / Next / References — agent- and human-searchable, not raw transcripts/braynee:sessionsExport Claude Code sessions to Obsidian markdown. Sync, list, resume, annotate sessions/braynee:settings-viewerOpens a live visual dashboard of your Claude Code configuration and usage analytics/braynee:setupSecond brain onboarding wizard. Scaffolds PARA vault structure, company knowledge base, detects git projects from the filesystem, seeds company notes from the web, installs Obsidian plugins, initializes Git/Beads/QMD, and writes CLAUDE.md/braynee:tasksCreate, complete, list, and query tasks via Obsidian TaskNotes/braynee:vault-queryThis skill should be used when the user asks about vault session management, project context loading, session lifecycle, or mentions 'vault-query', session start/close/list, or project context aggregation/braynee:zettelkastenCreate, find, and link atomic notes in your Zettelkasten. Distill insights into permanent notes with backlinksTwo modes. One brain.
braynee works in two contexts — out of your vault, and inside a project. It detects which from the project itself (no flag), and the hooks fire accordingly. Underneath, it's one layer between Claude Code and your brain.
Project mode
You're in a ~/code git repo
An actual codebase you're building in — apps, websites, dashboards, internal tools, whatever you ship. braynee tracks the work, guards the git workflow, and writes the session down so the next one picks up clean.
- braynee drives
- beads tracking · branch-on-claim · commit cadence · session export
- Hooks that fire
- everything in vault mode, plus the code lifecycle below
- Stays quiet
- nothing held back — the full set fires
same braynee · same vault · it just knows which mode you're in
The layer underneath both
Claude Code
the agentEmits 10 lifecycle events as you work — SessionStart through TaskCompleted.
braynee
orchestrationThe layer this whole site is about. Hooks fire on every event; skills add slash commands; agents take heavy jobs.
Obsidian
the brainSessions, decisions, memory, tasks — structured markdown that outlives every session.
6 agents braynee can dispatch
Runs the morning or evening ritual for the vault owner
Searches the vault from multiple angles and synthesizes what is known about a topic
Creates the full vault presence for a new project or client engagement
Process unprocessed Inbox items into structured wiki notes
Expert at organizing the Obsidian vault using PARA methodology
Vault health audit and healing. Finds stale sessions, unprocessed Inbox items, missing note sections, orphaned projects, and recurring themes that should become wiki articles. Run periodically or when the vault feels messy.
7 scripts · 1 monitor
Same morning. With braynee, and without.
Time off, then back to braynee-web. On the left, a normal Claude Code session starting cold. On the right, the same morning with braynee — real output from this site's own tracker.
✗ without braynee
✓ with braynee
The right side is real bd output captured from this repository while building it.
One stubborn problem. One fix.
braynee is what happens when an educator, a consultant, and a developer are the same person — and all three keep hitting the same wall.
End of context
Give your Claude Code
a memory.
Free, open Claude Code plugin. Install it once — the lifecycle hooks do the rest, every session after.