· ai-devtools

AI agents need to be replaceable – without losing your work

An agent receives approval to process a partial refund.


It sends the request to a payment API, and the process crashes. Maybe the payment service completed the refund.

Maybe the request never went through. A replacement agent spins up and finds an operation record marked dispatched with no outcome written.

This kind of ambiguity isn't unique to agents. Any distributed worker crashing mid-mutation faces the same problem.

But a conventional worker resumes a predetermined workflow from the last checkpoint. An agent does something more dangerous: it reasons on its own.

Given the same customer request and no outcome record, it might come up with a different plan, pick different parameters, or decide to issue a new refund instead of continuing the one already approved. "An agent does something more dangerous: it reasons on its own."

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.35 released
  2. next.js 16.5.0-canary.33 released
  3. angular 22.2.4 released
  4. LibreOffice's 'no AI' stance meets LLM-assisted code
  5. “Urgency is an inherently subjective call”: Anthropic tells TNS how it grades Claude Duet