Chain of Thought | AI Agents, Infrastructure & Engineering podcast

The Infrastructure Behind Agents That Run for Months

0:00
53:18
Rewind 15 seconds
Fast Forward 15 seconds

Tony Holdstock-Brown is the CEO and co-founder of Inngest, which built durable workflows for background jobs before the agent wave arrived. He says most Inngest customers no longer log into the UI. Their agents check on what they have built through the API, the CLI and MCP, and people who build with agents activate at about 93 percent, against roughly 40 percent before.

Holdstock-Brown defines a long-running agent as one that lives for months and builds up its own context. Running one means orchestrating sub-agents, sandboxes and state for every customer, and he argues that orchestration layer becomes the product. He and Conor Bronsdon also get into why agent load compounds, how to score an agent from production events, and what Inngest learned from running out of compute.


If your users never open your product themselves, how it behaves for their agents is the whole experience.


We cover:

  • Why durable workflows, a series of steps with checkpoints, mapped cleanly onto agents
  • Holdstock-Brown's definition of a long-running agent: it lives for months and builds its own context
  • Inngest's shift from UI traffic to API, CLI and MCP, and the 93 percent activation rate among people building with agents
  • How agent load compounds when every user's agent makes thousands of API requests a day
  • Tracking events and outcomes for every agent run, a lesson Holdstock-Brown ties to KISSmetrics and A/B testing
  • Explicit step APIs compared with compiler directives, and why a step is close to tracing
  • Running out of compute: bare metal, bandwidth limits and building on FoundationDB

New episodes, the ideas behind them and Conor's essays land in the Chain of Thought newsletter first. Subscribe: https://newsletter.chainofthought.show/

Chapters:
(0:00) Why agents need durable infrastructure
(1:13) How Inngest started before agents
(3:53) Defining a long-running agent
(6:08) Orchestration becomes the product
(8:40) Customers' agents replace the UI
(10:40) Reliability when agent load compounds
(16:40) State, memory and personal agents
(20:50) Personal agents for mainstream users
(28:07) Step APIs vs compiler directives
(31:27) Code review agents and security
(40:38) Running out of compute
(46:55) Building your first long-running agent


Links from the episode:

Connect with Tony Holdstock-Brown:

Connect with Chain of Thought host Conor Bronsdon:

More episodes: https://chainofthought.show

Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long - they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod

More episodes from "Chain of Thought | AI Agents, Infrastructure & Engineering"