memorable
$ memorable recall "run the checkout flow"
0.847 procedures/7d3f2ac9-checkout-flow [lexical,semantic]
$ memorable show procedures/7d3f2ac9-checkout-flow
Decisive steps last time:
1. [execute] Filter: price, low to high
A Browser Agent Re-Learns
The Same Site Every Session.
Recall, Replay, Fall back.
Memorable keeps the path that worked and hands it back before the next run.
The site comes back. Memorable hands the agent the path it took last time, page state by page state.
Segments the agent has crossed before run from the procedure. The model is called only where the page differs.
A changed layout fails the precondition. The agent reasons through that segment and the run is stored as a revision.
memorable
$ memorable recall "book the SFO to AUS flight"
0.84 procedures/2c91e0aa-book-flight
How It Works For Browser Agents.
Browser traces arrive as one JSON trace. Page states become preconditions. Known segments replay without a model call.
{ 01 }
Page state, not URL
A state is what is on the page. A layout change is detected and the agent falls back to reasoning.
What Memorable Reads.
3 CONFIGURED
browser-use traces
Session traces from the browser-use agent, one JSON trace per run
The browser-use fork on GitHub
Capture hook that ships the trace at session end
Any browser harness
POST the tool calls to /v1/extract and get the procedure back
