plugin brain-suplement
The journal
Claude cannot skip.
You spend an afternoon with Claude Code deciding how to price something, or why the landing page says what it says. Six weeks later you need the reasoning, and it is gone. Claude does not remember it, and neither do you. The chat log is somewhere, in a format nobody reads.
This plugin makes Claude keep the record while the work happens. A note per session, an index per day, a file per decision with the reasoning as it was made, a hub per topic that points at all of it. Plain markdown with links, so you open the folder in Obsidian and read what happened in the words Claude used at the time. And four small checks make sure it never gets skipped.
Get it on GitHub Read the limits firstWhy it exists
There are memory tools for Claude Code, and some are very good. They store what Claude saw so that Claude can recall it next time. That fixes Claude's problem. It does not fix yours: the person who needs the record is you, later, and a vector database is not something you read.
The tools that do write readable notes write them after the session, by summarising the log. A summary written afterwards loses the reasoning. And every one of them is polite about it: if Claude forgets to write, nothing happens. I ran this inside my own consulting workspace for months before making it a plugin, and the notes only became reliable the day the hooks stopped being polite.
What it does
Seven kinds of note, each with one job
A daily note indexes the day. A session note says what happened in one sitting. A decision note freezes why you chose one thing over another and is never edited again. A research note keeps a snapshot with its sources. A logbook holds the living state of one topic. A weekly note sums up the week. And a map of content per topic points at all of the above, pointers only, no prose. Each folder carries a short README with the exact format, and Claude reads it before writing.
Written during the work, not after
The rule Claude follows is simple: the session note gets a line whenever a file is created, a decision is taken, something is sent, or something fails. In the same turn. So the reasoning behind a decision is written while it is still the reasoning, not reconstructed from a log.
Refuses to end a turn without the note
When a session starts, Claude is shown what exists today. When the notes go stale, it gets a one-line nudge. When it tries to finish a reply while today's notes are missing, or the session note is not linked from its topic hub, it is not allowed to. It writes the note, then finishes. Before Claude compacts its context, it is made to dump the session note first, so nothing is lost with the details.
Nothing to run, nothing to pay for
The whole thing is a handful of shell scripts and some markdown. No database, no server, no embeddings, no account. Search is the search you already have, or Obsidian. A new project gets its journal with one command.
What it cannot do
It cannot make the notes good. The checks look at whether a file exists, whether it was touched today, and whether the topic hub links to it. They do not read it. A lazy note passes. What makes the notes worth reading is the contract Claude follows, and a model has to follow it.
It cannot recover a session that never wrote. If Claude is killed mid-turn, or hits the limit of three refusals in one session, the turn ends without a note and the next session start says so. The limit exists so a broken setup can never trap you.
It is one journal per project, it needs bash (so on Windows it needs WSL or Git Bash), and it costs a few hundred tokens per session for the state it prints, plus whatever Claude writes into the notes. Usually three to five lines at a time.
Installing it
It is a Claude Code plugin. Inside Claude Code, two commands:
/plugin marketplace add aguevara92/brain-suplement /plugin install bitacora@bitacora
Restart the session, then in the project you want journaled, name the first topic:
/bitacora:scaffold Marketing
That creates the folders and their READMEs. From the next session on, Claude writes the journal on its own, and the checks make sure it does. The plugin's internal name is bitacora, Spanish for a ship's logbook, which is what this is.
Most of what I build ends up looking like this
A small, specific thing that removes one real problem, extracted from a system I actually run. If that is the kind of help you want inside your own business, that is what I do.
or just take the code, it is yours
Talk to me