Durable execution

Durable execution records work associated with a conversation or project. A run retains its identity, status, events, and result after the request that started it ends.

Agent runs can be attached to a conversation or owned by a project without conversation messages. Task and workflow runs execute project work.

Run records

A run records its kind, owner, parent and root runs, lifecycle status, waiting condition, and final output or error. Run events preserve progress and execution history.

Saving a conversation message does not start execution. A client stores the message, then submits a separate run request. See Architecture and flow.

Run types

New runs use one of these execution kinds:

Run kindOwnerRepresents
agentConversation or projectAgent execution, with conversation messages when attached to a conversation.
workflowProjectExecution of a workflow and its coordinated steps.
taskProjectExecution of a task target.

A task or workflow definition describes the work. Each run records one execution. A schedule can start an agent, task, or workflow target. The run keeps that target's kind: a schedule is a trigger, and a job runtime is an execution environment.

Waiting and resuming

A waiting run records the condition needed to continue. Resume signals depend on its kind and current wait: a tool result, approval, event or release of a confirmed manual pause. Input requests have their own response operation.

A supported resume continues the existing run with the same run ID. Replaying stored events or reconnecting to an event stream only reads progress. It does not resume execution. The resume operation describes accepted signals and conditions.

Durability and external actions

Durable history survives the client connection. Recovery and retries depend on the target. External actions are not guaranteed to happen exactly once. Email, payments and other side effects need appropriate idempotency or duplicate handling.

See Events and streaming for reading progress, and Run background work for tasks, workflows, and schedules.