Skip to main content
This page is for the code path - the durable runtime underneath, in TypeScript. To build an agent without code, start with Build your first agent. Everything in Duraton - an AI agent, a nightly job, a webhook handler - is a workflow: an ordinary TypeScript function whose units of work are wrapped in steps. Duraton records each step’s result the moment it completes. That one rule is what the rest of the platform is built on: a crash, restart, or deploy resumes the run at the next step instead of starting over; a step that waits on a person or a timer holds no worker while it waits; and the record of what ran, in what order, with what result, exists before anyone asks for it. This tab is that runtime. It reads the same whether or not there is a model call in the handler - the AI-specific steps are in AI, and the agent authoring layer in Agent kit.

The pieces

What the runtime gives a handler

A step id ("triage", "refund") is how its saved result is found on the next pass. Keep ids stable and unique within a handler, or a replay will not match the work it already did. Steps covers the rules, and Production covers changing them safely.

Next steps

Durable execution

What a step guarantees, and the two rules the code between steps has to follow.

Quickstart

Create a project, connect a runner, trigger a run, and restart the runner mid-run.

Recipes

One complete, paste-and-run workflow per task.

Production

Routing, deploying with runs in flight, draining, and blue/green.