13 Nov 2026 Why Stripe Cut 500,000 Internal Docs Down to 5,000?
Documentation must evolve to serve both agents and humans, requiring strict accountability and rigorous quality to prevent operational risks and maintain trust in AI-driven workflows.

Published 15 May 2026
Duration: 00:41:11
Managing long-running agents requires state checkpointing and rehydration for fault tolerance, balancing durability with scalability via modular architectures, orchestration frameworks like Temporal, open standards, and simplified agent designs that separate concerns and leverage existing infrastructure.
Hamza Tahir, co-founder of ZenML, joins the show to cut through the hype around long-running agents arguing that at the end of the day, an agent is ju...
The podcast explores challenges in managing long-running agents, emphasizing the critical need for checkpointing state within extended while loops to enable recovery from failures and resume execution from precise interruption points. It defines "long running" as context-dependent, ranging from seconds to years, and stresses infrastructure planning for scalability. A central theme is the evolution of harness architectures, distinguishing between basic "inner harnesses" (simple loops interacting with models and tools) and more complex "outer harnesses" that decompose systems into modular components like decision-making "brains" and sandboxed "hands" for tool execution, with examples from Anthropics scalable approach. The discussion also highlights durability mechanisms, such as file system snapshots and memory states, to ensure fault tolerance and avoid redundant work, while using analogies like the Game of Life to illustrate how nested loops form hierarchical agent systems.
The content delves into open standards and infrastructure, advocating for interoperable, open-run harnesses to prevent vendor lock-in and enable broader accessibility, while acknowledging the trade-offs between managed platforms and self-hosted solutions. It critiques current tools for interoperability gaps and calls for horizontally scalable, open-runtime environments that separate models from harnesses to avoid monopolization. Key concepts include durable execution frameworks like Temporal and ZenML, which manage long-running workflows through reliability and replayability, alongside challenges in managing external state persistence (e.g., databases) and reconciling agent workloads (e.g., coding agents) with durability needs like sandboxing and artifact storage. The discussion also contrasts distributed systems (focused on reliability for extended workflows) with bursty container-based workloads, emphasizing differing philosophies in scalability and latency management.
Finally, the podcast examines deployment paradigms and developer experience, critiquing overly complex abstractions in SDKs and advocating for simplicity in agent architecture design. It highlights the importance of state management via artifact stores and dynamic workflows over static DAGs, while addressing challenges in integrating with existing tools and balancing durability with usability. The need for replayability, error recovery, and human-in-the-loop scenarios is underscored, alongside the role of community-driven open-source projects like Kitaru in advancing resilient, durable execution systems. Philosophical reflections on reducing complexity and avoiding over-engineering agent systems are interwoven with practical critiques of existing tools and the limitations of current orchestration approaches.
What if you implemented a state checkpointing system using file system dumps every 10 iterations in your long-running agent?
What if you designed your harness as an open, modular component separate from your core business logic?
agent_harness.py) that handles tool calling, state management, and logging, while keeping your business logic in a separate core_business.py file.What if you adopted a durable execution framework like Temporal to manage your agent's workflow orchestration?
13 Nov 2026 Why Stripe Cut 500,000 Internal Docs Down to 5,000?
Documentation must evolve to serve both agents and humans, requiring strict accountability and rigorous quality to prevent operational risks and maintain trust in AI-driven workflows.
9 Nov 2026 My AI Agent Bought Me A Car
Hermes agent uses reinforcement learning and trace-to-environment synthesis to enable continual self-improvement, balancing token efficiency with inference-time steering for better agentic performance.
2 Nov 2026 How Stanford Teaches AI Coding Now
AI agent development, verification loops, and go-to-market automation are reshaping software engineering and sales strategies.
29 Oct 2026 From Slop Code to Software Factories
"Tandem biking in Amsterdam's chaotic cycling culture led to a critique of AI-assisted coding's flaws, particularly its tendency to produce unmaintainable, poorly structured code, raising concerns about long-term software reliability."
22 Oct 2026 Token Maxxing Is Over and Here Is What Comes Next
"AI in software development offers benefits but faces challenges like nonsensical outputs and over-reliance; smaller, controlled models like Sonnet improve adoption, while measuring ROI and human-AI collaboration are key to success."