Conversations API
Durable messaging
Conversations
Messages
Durable execution
Runs
Events
Core model
| Layer | Stores | Use it for |
|---|---|---|
| Durable messaging | Conversations, messages, branches, read state, and input requests. | What the user sees. |
| Durable execution | Runs, events, checkpoints, resume, and completion state. | What the system did. |
Why both exist
A message stores visible chat state. A run stores the work that produced, streamed, resumed, cancelled, or failed that response.Contents
| Page | Use it to understand |
|---|---|
| Durable messaging | Conversation state and message structure. |
| Durable execution | Runs, jobs, workflows, events, and resume behavior. |
| Architecture and flow | How a message becomes a run and final answer. |
| Run lineage | How conversations, messages, runs, and child work connect. |
| Events and streaming | SSE, AG-UI events, durable events, and notifications. |
| Authorization | Access boundaries for conversations and runs. |
| Connect an agent | Runtime contract for developer-provided agents. |