What your agent's memory did
Read from the database on this machine. Nothing here is uploaded.
Entering and leaving memory
Each week: what the agent learned, and what was taken out of its memory. What survives is work it never has to redo.
How strong the surviving facts are
Live facts by decay strength, in fifths. Strength is importance halved every half-life the fact goes unused — anything that fell below the floor is already in the graveyard.
Why facts died
Supersession means the agent corrected itself. Decay means nobody needed it again.
What changes when memory expiressimulation
Not your data. Decaf's own benchmark: the same agent over the same 20 runs, with and without it. Every pair below is one metric, measured the same way both times.
—
Your agent's memory
Read from the database on this machine, over loopback. Nothing on this page is uploaded — the hosted service never holds memory content, and it cannot read this.
Live
What the agent can still act on. Strength is decay — is it worth keeping. Confidence is freshness — is it still true.
Graveyard
Kept as proof, never recalled. The audit trail — what was destroyed, and why.
Two clicks to start: connect a wallet, then add Decaf to the AI app you use. Connecting a specific agent is optional and comes last.
Your wallet is how the dashboard knows which agents are yours. It is read-only — no transaction, no signature, no gas.
One click, and nothing to install first — Decaf speaks MCP in the standard library. It finds the AI apps on this machine and adds itself to the one you pick. Your memory stays here; only the app's own settings are written.
Optional. Your agent already works with Decaf without this; connecting it adds a per-agent memory policy you can switch on and off, and ties the erasure record to this wallet. An agent identity is an NFT, so an agent is something you own rather than an account you make.
Where to find it: ask your agent — it knows its own id, and telling you is the one thing it can do before it is connected here. The registry cannot be listed and the public RPC refuses log scans, so the id has to come from you rather than a guess. Checked against the chain before anything is stored.
Your tier
—
——
The lifetime map
How long facts of each kind actually stay true, aggregated across every agent that reports. Content-free: a category and a duration, nothing else.
Per category
Observed median, blended with the bootstrap prior until there is enough signal. Early rows are prior-shaped, not measured — read them that way.
| category | observations | range (days) | prior now |
|---|---|---|---|
| Loading… | |||
The boundary
This is the product, stated as a promise the code enforces.
A test fails if a future change lets memory content land here. That is the whole reason Decaf is not another hosted memory vendor.
The erasure record
An append-only record of erasures, kept here so anyone can check it. It shows a fact was committed to before it was removed — which is what stops a claim of forgetting being invented, or quietly taken back.
—
It does not prove the bytes are gone from every backup. Nothing can prove that about a machine you do not control, and saying otherwise would be the most attractive lie this product could tell.