
Brainbox
io.github.thebasedcapitalPublished by GitHub account thebasedcapitalv0.1.6Updated Oct 24, 2026
Hebbian memory for AI agents. Learns file patterns, predicts next tools, saves tokens.
Overview
Gives a coding assistant local procedural memory: it records file, tool and error patterns and recalls likely files before the agent searches.
- What you can do
- BrainBox watches what a coding agent actually does and stores it in a local SQLite graph: which files are read and edited together, which errors were fixed by which edits, and which tool chains repeat. On later tasks it recalls the right files up front, predicts the next tool, and can surface error-to-fix procedures. It exposes eight MCP tools including record, recall, explain, error, resolve, predict_next, stats and decay, and also ships a CLI.
- When to use it
- Worth adding for repeated work in the same repository, where an agent spends many tokens re-searching for the same files. It is aimed at coding agents and can be seeded from git history and a code graph to reduce the cold start.
- Requirements
- Runs locally over stdio as the npm package brainbox-hebbian. Needs Node.js 22 or newer on macOS or Linux; the optional FSEvents file-watcher daemon is macOS-only. No accounts, API keys or environment variables are declared. Embeddings are optional and require downloading a model; without it recall falls back to keyword search.
Installation
In SourceWeft
- Open Brainbox in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[BrainBox — muscle memory for coding agents]
[npm version] [GitHub stars] [Node 22+] [MCP: 8 tools] [Zero cost, local, SQLite] [MIT license]
Install · How it works · Results · Research · Integrations · Whitepaper
BrainBox is procedural memory for AI coding agents. It watches what the agent actually does and remembers it:
- which files get read and edited together
- which errors were fixed by which edits
- which tool chains the agent repeats
On the next task it puts the right files in front of the agent before it starts searching.
Not a vector database. Not RAG. Hebbian learning on a local SQLite graph. Zero API cost, no GPU, nothing leaves your machine.
Paper
BrainBox: Local Behavioral Memory for Coding Agents (Bhavesh B, 2026). The DOI above covers all versions and resolves to the latest. Latest version: v0.2, doi:10.5281/zenodo.23250505.
Install
That's it. The postinstall script:
- Adds a
PostToolUsehook to~/.claude/settings.json. It learns from every file read, edit, search and command. - Adds a
UserPromptSubmithook. It injects compact recall into prompts, or stays silent once it has learned you ignore it. - Adds a
SessionEndhook. It scores which recalled files you actually opened or edited and compiles procedures. - Registers the MCP server via
claude mcp add, with 8 tools:record,recall,explain,error,resolve,predict_next,stats,decay. - Creates
~/.brainbox/and starts a background download of the embedding model.
Hooks never download models. Until the model is cached (brainbox models pull), recall runs lexical-only. Embeddings come from the optional @huggingface/transformers dependency; if its native modules can't install on your machine (for example, sharp with a system libvips and no build tools), BrainBox still installs and runs with keyword search. brainbox models status shows which mode you are in.
Kill the cold start by seeding from git history and the code graph:
Uninstall: brainbox uninstall removes the hooks and the MCP server and keeps your database.
How it works
[BrainBox pipeline: tool calls → learn → recall → policy → inject, with a feedback loop]
Every tool call is a neuron firing. Files, tools and errors become neurons, and things accessed close together become synapses. A prompt triggers recall, which fuses several ranking channels. A learned policy decides whether injecting is worth the tokens. Feedback on what you actually opened or edited flows back into the graph.
Fire together, wire together
[Hebbian learning: co-accessed files strengthen their synapse across sessions]
Access auth.ts then session.ts across sessions and their synapse strengthens. SNAP plasticity makes strong synapses grow more slowly, so no single connection takes over. Links are directional (STDP): what you open next matters more than what came before.
Spreading activation
[Spreading activation from a seed file over three hops with fan-effect damping]
Recalling one file activates its neighbours for up to 3 hops. Each hop is damped by 1/√degree, so hub files don't flood the results. Each result carries the channel and the edge that produced it. brainbox_explain shows you exactly why a file was recalled.
Superhighways and decay
[Frequently used paths myelinate into superhighways while unused edges decay]
Paths you use often are myelinated into instant-recall superhighways. Recency and frequency follow the ACT-R base-level equation, B = ln Σ tⱼ^-0.5, and unused connections fade. Files recalled but ignored weaken only the edge that surfaced them.
Error → fix immune system
[An error fingerprint is linked to the edits that fixed it and recalled the next time]
When a failed command is followed by edits and a passing rerun, BrainBox stores an error→fix procedure. The procedure is keyed by the error's fingerprint and tracks helpful/harmful outcomes. The next time that error appears, the fix files are recalled at once. Procedures are shown to the agent as quoted observations, never as instructions.
Results
[v0.2 vs v0.1 vs best baseline on real agent trajectories]
brainbox eval replays real coding-agent trajectories in time order. Each task is scored on a fresh in-memory DB trained only on earlier tasks from the same repo, and every system ranks the same candidate set.
v0.1 lost to plain recency on next-file prediction. On the held-out SWE tasks the gap was −.207, 95% CI −.312…−.118. v0.2 is statistically tied with recency there. Next-tool prediction now beats every baseline significantly, and files-read recall leads on both data sources.
Known gap: on local sessions, ranking by edit frequency alone still beats BrainBox for edited files (Δ −.089, CI −.185…0).
Fitting the lexical and Hebbian channel weights to zero scored higher on dev, but recall then ignored the query, so the shipped weights keep them.
Full table, protocol and commands
Probes:
- P1: files edited or read for the task (query = task text)
- P2: next file, step by step
- P3: next tool (top 3)
Baselines: recency, frequency, BM25, EdgeBank and random. Confidence intervals are paired bootstrap 95% CIs, resampled by trajectory.
Datasets:
- Ranking weights were fit only on the dev repos (sqlglot, dvc, streamlink).
- SWE test is 40 held-out tasks from Pillow and conan.
- Local is 97 agent sessions across 5 projects, never used for fitting.
Scores are MRR (P3: MRR@3), with embeddings off.
Code search: on a 30-query code-search set, the default jina-embeddings-v2-base-code reaches Recall@5 0.867, against 0.667 for the previous MiniLM.
Built on research
[Recent papers mapped to the BrainBox subsystems they shaped]
Each v0.2 change maps to a recent paper and was measured with the replay eval:
Also in 0.2:
- Builds on Node 22–26 (better-sqlite3 v13).
- Hooks are written in Claude Code's nested settings format.
- The hook DB lock wait is capped at 100 ms.
- Procedure compilation is 470× faster on large histories.
Integrations
MCP server (any agent)
Kilo / OpenCode (native plugin)
Add to ~/.config/kilo/config.json:
OpenClaw (NeuroVault)
BrainBox can run as an OpenClaw memory slot plugin. See NeuroVault for the reference implementation.
macOS daemon (opt-in)
A system-wide FSEvents file watcher that learns from VS Code, Xcode, vim and the shell, not just agents. It installs a LaunchAgent, so it requires an explicit opt-in:
CLI
Configuration
Gemma profiles are subject to the Gemma Terms of Use.
Algorithm details
The paper's source (v0.2, doi:10.5281/zenodo.23250505) describes the implementation and coverage-conditioned replay results, including uncertainty and provenance limitations. See paper build and evidence notes for the bibliography, aggregate evidence, LaTeX and PDF build.
Architecture
Development
Requirements: Node.js 22+, on macOS or Linux. The FSEvents daemon is macOS-only; everything else is cross-platform.
If BrainBox saved your agent some searching, give it a ⭐ so others can find it.
Built by @thebasedcapital · MIT License
Source: README.md at commit 2585acb
Tools
0Version history
1- v0.1.6LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts