Docs: Procedural Memory For Agents | Memorable

· Memorable

2 min read Original article ↗

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.

Pick your route

Four ways in. Each one ends with this machine signed in and recording. Nothing below asks an agent to open a browser.

A coding agent on a repo

Claude Code, Codex, Cursor, Devin, Antigravity.

npx memorable-cli

Picks the agent, asks whether to make a page for this project, opens one tab, you press Approve. Hooks and consent are written for you.

Your own agent

Browser, voice, smart home, research, ops.

memorable.sh/dash, Environments, Connect

Pick the card, Save, Copy prompt. The key is already in it. Paste it into the agent that builds your project; it adds recall, replay and record.

No terminal

claude.ai, Cowork, Claude desktop.

memorable.sh/dash, Connect, Create a connector

Add the link under Connectors in Claude. It searches memorables before it plans and records when it finishes.

A server with no Node

A backend that runs agents.

memorable.sh/dash, Account, New key for an agent

POST /v1/extract with the key. Store the draft on your side.

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.

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.

Measured

Against the same tasks run without memory, on two independent runs.