# Replay from the failure checkpoint, not from memory

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Replay from the failure checkpoint, not from memory

ID: MHC-D-RESEARCH-1158 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/replay-from-the-failure-checkpoint-not-from-memory

A reproducible failure is more useful than a fresh attempt that happens to succeed.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An agent failed late in a long run and a full rerun is expensive, slow or unlikely to recreate the same decision.

### Avoid when

- A checkpoint is only as good as the state it captures. External systems, time and hidden side effects can still prevent an exact reproduction.

### Explanation

Checkpoint meaningful execution state before expensive or consequential boundaries. When a failure appears, restore the nearest useful checkpoint and change one factor: the model, a tool response, a policy or a piece of state. Compare the resulting decision with the original path instead of asking the system to recreate the whole past from scratch.

### Steps

1. Choose a checkpoint before the decision you want to inspect.
2. Restore the captured model, tool and task state.
3. Change one intervention while holding the rest as stable as practical.
4. Compare both the next decision and the final outcome.

### Example

A support agent issued the wrong refund after seven tool calls. Replay from the checkpoint before the refund decision with the repaired policy tool rather than rerunning the entire conversation.

### Check

You can name what was held constant, what changed and whether the decision or outcome changed after replay.

### Limits

- A checkpoint is only as good as the state it captures. External systems, time and hidden side effects can still prevent an exact reproduction.

### Evidence and sources

- supports: A checkpointed agent run can be replayed from an intermediate state while changing one model or tool decision, which can make interventions easier to compare than full reruns. — RS-EA671DF45F465038. Replay quality depends on what state the checkpoint actually captures; hidden external state can still make the reproduced execution differ from production. (2:03-10:54, production checkpoints, change one execution part and apply an intervention across a cohort)
- RS-EA671DF45F465038: Your Agents Need a Save Button — https://ai.engineer/talks/bZISsg7H7DA-your-agents-need-save-button

### Vedokrok editorial review

Replay the decision without repeating the damage

A saved checkpoint is a place to restart an experiment. It is not permission to repeat the original payment, email or database write.

#### Define what runs again

Choose a checkpoint before the failed decision. Record the one change you want to test and which earlier results will be reused. Before starting, identify every later tool that can change an external system. Replace those effects with recorded responses or an isolated test service unless a live action is separately authorized.

#### Compare decisions in a safe test

For an agent that closed the wrong support ticket, restore the relevant state and change the routing rule. Capture the proposed closure in a test system rather than closing another live ticket. Compare the decision and final test state with the original. Missing files, changed services or unrecorded state can still break the comparison.

**Editorial takeaway:** Before replay, list the calls that will run live and show where their effects will go. If you cannot account for a consequential write, stop and isolate it first.

#### Editorial evidence

- supports: The conference demonstration reuses saved checkpoints before a changed step, then runs the remaining execution under the intervention. — RS-EA671DF45F465038. Selected timestamped transcript read on 2026-10-04, especially 5:03–7:35. This supports the demonstrated comparison pattern, not a universal checkpoint contract or a verified deployment. (Transcript 5:03–7:35; chapter Change one part of the execution)
- supports: Kitaru documentation describes replaying tool calls from recorded responses rather than repeating their real effects. — kitaru-readme. Selected README passage read on 2026-10-04. This is the current product description, not a test of the older conference version or this repository. (README, Why, bullet Replay re-executes your code)
- limits: The documented protection depends on substituting recorded tool responses; it does not establish that an arbitrary replay harness isolates every external write. — kitaru-readme. The call inventory and stop rule are editorial safety checks derived from the documented mechanism. Neither runtime behavior nor external services were executed in this review. (README, Why; Self-hosted, by design)
- RS-EA671DF45F465038: Your Agents Need a Save Button — https://ai.engineer/talks/bZISsg7H7DA-your-agents-need-save-button
- kitaru-readme: Kitaru: replay-based evaluation — https://github.com/zenml-io/kitaru

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/checkpoint-meaningful-progress-before-a-long-agent-crosses-a-fragile-boundary
