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

Flow

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

What persists

ObjectStores
ConversationThread metadata, project scope, active branch, and message count.
MessageUser prompts, assistant answers, tool output, files, citations, and typed parts.
RunExecution identity, owner, status, lineage, and terminal state.
Agent runConversation-specific execution state and assistant message link.
Run eventOrdered execution history for streaming output, tool calls, state, errors, and completion.
Input requestStructured 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.