Agent checkpointing is far from production-grade resiliency
Summary
A blog post argues that current agent checkpointing is insufficient for production-grade resiliency, highlighting gaps like failure detection, automatic retries, and high availability, and suggests building agents on a highly-available orchestration layer.
Similar Articles
Production agent evals should test incident replay not just task success
Discusses that production agent evaluations should include failure replay and resume capabilities, not just happy-path task success, emphasizing the need for observability that enables recovery.
Your agent's retry logic dies when the agent does
The author shares lessons from putting an AI agent with write access into production, explaining that retry logic inside the agent loop fails when the process dies. They advocate for treating side-effectful tool calls as durable background jobs with idempotency keys.
72% of teams are running coding agents in production. Most of them can't say which agent they'd trust with a critical path change at 11pm, or why.
While 72% of teams use coding agents in production, most lack formal governance or empirical data on agent reliability. The article argues for session-level tracking over policy frameworks to ensure trust in critical deployments.
I analyzed how 50+ AI teams debug production agent failures and got surprised
Based on interviews with 50+ AI teams, the author highlights that production agent failures often stem from minor prompt or configuration issues rather than deep model problems. The article advocates for adopting software engineering practices like versioning, A/B testing, and experiment tracking to improve reliability.
Just had to rewrite my entire agent infrastructure for reliability, anyone else doing the same?
The author describes rewriting their AI agent infrastructure for reliability using DBOS durable execution after facing cascading failures, and asks the community about similar experiences, tool choices, and build-vs-buy decisions.