brainbox_recordLABSCO SUMMARY
Procedural memory, not retrieval over documents.
It does not index your code — it records what you touched together and makes those paths cheap to reach, which is why the git-history bootstrap matters: a cold network knows nothing. The system-wide daemon that watches other editors is deliberately not installed for you, because it registers a LaunchAgent and monitors your project directories.
What it is
A memory layer for coding agents built on Hebbian learning: files, tools and errors are neurons, accessing them together forms synapses, frequently used paths strengthen, and unused connections decay.
What you get
- 7 MCP tools — brainbox_record, brainbox_recall, brainbox_error, brainbox_resolve, brainbox_predict_next, brainbox_stats and brainbox_decay
- Passive learning through Claude Code hooks: a PostToolUse hook learns from every file read, edit and search, a UserPromptSubmit hook injects recall into prompts
- An error-fix memory — which files fixed which error, offered again the next time a similar one appears
- Tool-sequence prediction: after enough Grep-Read-Edit chains it predicts what comes next and pre-loads the likely files
- The same operations on the command line —
brainbox recall,brainbox record,brainbox stats,brainbox hubs,brainbox highways,brainbox graph brainbox bootstrap --repo <YOUR_PATH_TO_PROJECT> --importsseeds the network from git co-changes and the import graph, so it doesn't start from nothing
Requirements
npm install brainbox-hebbian. The postinstall step registers the MCP server, adds both Claude Code hooks and creates ~/.brainbox/. For other agents, run the server standalone with node node_modules/brainbox-hebbian/dist/mcp.js from the folder you installed it in — the published package ships only the compiled dist/ files, not the src/ path the README shows. The macOS file-watching daemon is separate and opt-in via brainbox daemon install; brainbox uninstall removes the hooks and server while keeping the database.
Setup effort
One command — npm install brainbox-hebbian
USE CASES
Skipping the search you already did last week
Files that keep being opened together get recalled directly instead of grepped for again.
Fixing an error you have seen before
Ask about the error text and get back the files that resolved it last time.
Starting on a repo with history but no memory
Seed the network from git commit co-changes and the import graph before the first session.
Seeing what the network has actually learned
List the most connected files, the paths that have become superhighways, and the ones decaying from disuse.
7 tools
Listed in project code.
brainbox_recallbrainbox_statsbrainbox_decaybrainbox_errorbrainbox_resolvebrainbox_predict_nextBEFORE YOU INSTALL
What to know first
Tools you get
7 tools registered in the project's code.
Requires
Node.js 18+
INSTALLATION
Connect your client
Server setup
Claude Code
npm install brainbox-hebbianMCP Clients
Any MCP client
node node_modules/brainbox-hebbian/dist/mcp.jsRun it from the folder where you ran npm install brainbox-hebbian. The published package ships only the compiled dist/ files, so the src/mcp.ts path in the README does not exist after an npm install.
Kilo — plugin
Plugin: node_modules/brainbox-hebbian/dist/kilo-plugin.js