auctorai/durable_agents — explained in plain English
Analysis updated 2026-05-18
Learn how to make AI agent tool calls resilient to crashes by running them as Temporal activities.
Explore spawning subagents as child workflows for bounded subtasks.
Prototype programmatic tool calling where the model writes a script that orchestrates multiple tools.
| auctorai/durable_agents | 0petru/sentimo | alingalingling/akasha-wechat | |
|---|---|---|---|
| Stars | 17 | 17 | 17 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 5/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires the Temporal CLI on PATH to start a local dev server, no LLM API key needed for the default scripted mode.
Durable Agents is a runnable demo project that accompanies a blog post exploring how AI agents can be built as self writing workflows. It shows how to connect Pydantic AI, a Python framework for building AI powered applications, with Temporal, a workflow orchestration system that makes long running processes resilient and restartable, so that every step an AI agent takes becomes a durable, retryable unit of work. The core idea is that when an AI model decides to use a tool, that tool call is automatically converted into a Temporal activity, which is a tracked unit of work that Temporal can retry on failure and resume after a crash. The project also supports spawning subagents, where the model starts a child workflow for a subtask, and programmatic tool calling, where the model writes a short script that orchestrates multiple tools in parallel or in sequence. The demo runs without any AI API key by default. A scripted model replaces a real language model and emits pre defined tool calls, making it easy to explore workflow behavior deterministically. You can switch to a live model by providing an OpenAI or Anthropic API key instead. A built in REPL lets you type prompts and watch the resulting Temporal workflow graph, and it leaves any file side effects in a local sandbox folder for inspection. Error handling is deliberate. Validation errors are fed back to the model as correctable feedback, known execution failures come back as terminal errors, retryable infrastructure failures are retried according to Temporal's policy, and parent cancellation stops all child work in progress without triggering another model turn. The test suite covers all these scenarios using Temporal's in-process test environment, checking that tool calls, subagent spawning, and programmatic tool calling all produce the expected workflow shape.
A runnable demo showing how to make AI agent tool calls durable and retryable by running them as Temporal workflow activities.
Mainly Python. The stack also includes Python, Pydantic AI, Temporal.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.