Runs
Create, inspect, steer, pause, resume, and recover durable Agent executions.
A Run is one durable execution accepted for an Agent and session. Acceptance pins the Agent deployment, Resource bindings, Credential resolutions, aggregate Policy, pricing, limits, principal authority, and customer context. Controls change future execution at explicit safe boundaries; they do not rewrite committed history.
Choose a path
| Goal | Guide |
|---|---|
| Invoke an Agent from the Console | Start a Run |
| Pause, resume, interrupt, cancel, rebind, or rewind | Operate Runs |
| Understand the deployed behavior | Agents |
| Route external input | Channels |
Durable identity
The short Run id is not the full address. A stable API address includes namespace, Agent, session, and Run id. Copying the address from the Console preserves enough context to retrieve or control the same execution without guessing its owner.
Next steps
Start a Run with a stable session, inspect its journal, and use controls only after reading their confirmation text and recovery consequences.