Local debugging memory / Open source

FIX IT ONCE.
REMEMBER
WHAT WORKED.

Give your next coding session a better starting point. Keep verified fixes on your machine.

Get started
01 / Knowledge that stays with youExplore Burr ↓

02 / The workflow

LESS REPEATING.
MORE RESOLVING.

Search what worked before. Verify what works now. Save the lesson for next time.

  1. 01NoticeStart with the error.
  2. 02SearchLook for a past fix.
  3. 03InvestigateCapture useful evidence.
  4. 04FixMake the change.
  5. 05VerifyRun the real checks.
  6. 06SaveKeep a reusable lesson.
Your agent does the debugging. Burr helps it find and keep useful lessons.
01

Memory, on your terms.

Markdown playbooks and runtime lessons live in ~/.burr/memory/. No account, API key, or hosted memory.

02

Guidance where you work.

Skills and rules guide your agent. Loaded Codex, OpenCode, and Pi adapters also observe tool outcomes.

03

Evidence before advice.

Save a fix after checking it. Treat every retrieved lesson as historical evidence to verify against your current code.

Explore the architecture ↗

03 / Get started

INSTALL BURR.

Node.js 22.12 or newer. Install once, then connect your coding agent.

Find your agent’s setup ↗
$ npm install -g burr-memory@latest && burr global

Package: burr-memory · Command: burr
Review new Codex hooks in /hooks. Pi needs its extension installed.

04 / Under the hood

INSPECT THE WORK.

Inspect the regression tests and storage boundaries before adding Burr to your workflow.