Architecture and flow

A conversation run starts with a stored user message. Events stream while the runtime works, then the final result returns to the thread.

Flow

Step	What happens
1	A user message is stored in the conversation.
2	A run starts to produce the assistant response.
3	Events record streaming output, tool calls, state, and terminal status.
4	The final answer is stored as an assistant message.

What persists

Object	Stores
Conversation	Thread metadata, project scope, active branch, and message count.
Message	User prompts, assistant answers, tool output, files, citations, and typed parts.
Run	Execution identity, owner, status, lineage, and terminal state.
Agent run	Conversation-specific execution state and assistant message link.
Run event	Ordered execution history for streaming output, tool calls, state, errors, and completion.
Input request	Structured input needed while a run is waiting.

Why events matter

Run events connect live execution to durable state. They let the API stream, replay, resume, finalize, and explain a run. See AG-UI event reference for event types.

Runs and events Run lineage

Getting Started

Concepts

Conversations API

Guides

Integrations

API Reference

REST API

GraphQL API

MCP API

Architecture and flow

Flow

What persists

Why events matter

​Flow

​What persists

​Why events matter

Flow

What persists

Why events matter