Memorable
An agent finishes a task; Memorable stores how it was done and replays it when a similar task returns. Storage stays on your side and consent is fail-closed.
Store your first procedure
Sign in, give consent, recall. Three commands.
Wire up your harness
Claude Code, Codex, gbrain, QM, or yours. The harness field is any string.
How recall finds it
Exact, then lexical, then a vector. A reworded ask still lands.
One endpoint
POST the tool calls, get a procedure back. Same trace, same steps.
Keep the store yours
This machine, your gbrain database, or QM Postgres.
What it saves
19% fewer agent turns, across two n=25 runs.
Quickstart
Two minutes. Signing in links this machine to your workspace; the default backend is a standalone local store, and on a machine running gbrain you can point it at your own database with memorable init gbrain afterwards.
npx memorable-cli@latest login # opens a browser, approves this machine memorable enable # explicit write consent, nothing is stored before this
curl -fsSL https://memorable.sh/install.sh | sh # then: memorable login
memorable ingest trace.json memorable recall "rotate the TLS cert" memorable show <slug> # guarded, injection-safe rendering memorable list # everything stored, newest first
For agents
Telling a coding agent "use memorable" is enough, every step is a plain CLI call it can run itself. The drop-in file lives on AGENTS.md.
memorable agents-md >> AGENTS.md