Memory, recall, audit and erasure for autonomous agents
Loom is a self-hosted backend for autonomous agents: memory they recall across runs, reusable procedures the agent executes, run records, an audit record of who wrote what, and scope-wide erasure. These are server operations, stored in ClickHouse (or Postgres for live memory and knowledge state).
What you get
- Memory and recall. Versioned facts with provenance, search that abstains when nothing is close enough, and a ranking boost for memories that successful runs relied on. Memory · Runs
- Procedures. Reusable how-tos the agent learns from doing:
procedure.addstores one as a graph of steps,procedure.matchfinds the ones that fit a task, and the runs the agent reports teach Loom the proven path and the steps that fail. A revised graph is kept only if its runs do not do worse. Procedures and learnings - Refusal. A pinned fact refuses contradicting writes, and
blacklist.addregisters a pattern no write may store. Conflicts and refusal - Audit. Each operation that changes memory leaves an audit row with a SHA-256 of its content, and a worker seals hourly windows into a hash chain, so an edit or deletion is detectable. The transport’s audit writes are fail-open (a failed insert loses the row); under the Postgres authority a memory revision’s audit row is stored with the revision. Audit log
- Erasure you can check.
erasure.requesterases a scope from every table that holds memory content (tombstones by default;purge=truedeletes the rows of auser_idornamespace_listscope) and ends with a residue census and a receipt. Retention and erasure - Rollback.
namespace.rollbackreturns every memory in a namespace to its version at a point in time. History and provenance - Headless operation. A bot gets its own identity (it signs itself up where self-signup is open), checks its connection before its first run, and can be diagnosed when it goes quiet. Headless bots
Audit and erasure are engineering primitives, not a compliance certification. Security
Check one agent task
Use a disposable namespace on your deployment, with a writer token for the agent. Integrate Loom into an agent covers the client and identity.
- Open the task with
run.beginand write a fact withmemory.setcarrying the returnedrun_id(runs). Add a checkpoint when the agent needs to resume after a stop. - Follow the procedure example
to register, match and report an execution, then call
procedure.evolveexplicitly. The agent executes the steps; inspect the match’s trust status. Close the task once withrun.complete, following the procedure run reporting rules to count each execution once. - With viewer access, inspect
run.getand read the namespace’srun.beginandrun.completeevents throughaudit.list. The offline verifier checks stored row hashes; read the audit page’s failure modes before treating the trail as complete. - As the namespace admin, erase the disposable namespace
and check for
status="completed",residue_count=0andverified_at. Save the receipt before the request ledger expires. Erasure retains audit rows and excludes backups; retention and erasure describes the boundary.
Some ops on this page are marked experimental on the status page.