Agent Runtime Overview

Preview

The execution engine that turns plans into durable, observable, resumable work.

The runtime owns everything that happens between "objective accepted" and "outcome delivered": scheduling, state, budgets, failure handling, approvals and orchestration.

Runtime components

           ┌────────────────────────────────────────┐
  task ──▶ │ admission · policy · budget allocation │
           └───────────────┬────────────────────────┘
                           ▼
           ┌────────────────────────────────────────┐
           │ planner  ◀────── replan signals        │
           └───────────────┬────────────────────────┘
                           ▼
           ┌────────────────────────────────────────┐
           │ scheduler → step workers (parallel)    │
           └───────┬─────────────────┬──────────────┘
                   ▼                 ▼
             tool runtime     sub-agent pool
                   │                 │
                   └────────┬────────┘
                            ▼
           ┌────────────────────────────────────────┐
           │ state store · checkpoints · event log  │
           └────────────────────────────────────────┘

Guarantees#

Property	Guarantee
Durability	Task and step state survive process restarts; a run resumes from its last checkpoint
Observability	Every step, tool call and decision emits an event to an append-only log
Boundedness	Steps, wall clock, tool calls and spend are capped per task
Idempotency	Effectful tool calls carry idempotency keys; retries do not duplicate effects
Containment	Effects are evaluated by the policy engine before dispatch, every time
Cancellability	A run can be cancelled at any step boundary with state preserved

Execution objects#

TasksThe durable unit of work created from an objective.RunsA single execution attempt of a task.StepsThe atomic action inside a run.StateWhat persists and where it lives.CheckpointsResumption and rollback points.ApprovalsWhere humans enter the loop.

Last updated 2026-09-12