> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Runs and conversations

> How agent execution, chat messages, and event history relate.

A conversation stores an interaction. A run records one execution, and events describe what happened during that execution. Keeping these resources separate lets a client display the conversation while inspecting how each response was produced.

## From input to result

When a person asks a support agent a question, the client stores a user message and starts an agent run. The runtime produces events while it works, and the assistant's output is persisted as a message.

```mermaid title="conversation-run.mmd" theme={null}
sequenceDiagram
  participant Client
  participant API as Veryfront Cloud
  participant Runtime as Agent runtime
  Client->>API: Store user message
  Client->>API: Start agent run
  API->>Runtime: Dispatch execution
  Runtime->>API: Report events and result
  API-->>Client: Stream progress
  Client->>API: Read conversation and run
```

The message provides the answer shown in the thread. The run provides its status, tool activity, output, and errors. An incomplete answer can therefore be investigated through its associated run rather than inferred from the message text.

## One conversation, multiple runs

A follow-up question creates another interaction in the same conversation. Regenerated answers can create alternative message paths, and delegated work can create child runs. Each execution retains its own identity and history.

Runs can also exist without a conversation. A scheduled task or an agent invoked for background work still needs execution tracking even when there is no chat thread.

## Reconnection and recovery

Messages rebuild the visible thread after a client reconnects. Persisted events support replay and live progress, while the run record identifies its current or terminal state.

An interrupted connection alone says nothing about the execution outcome. [Run lifecycle](/docs/cloud/conversation-api/durable-execution) explains status and waiting; [events and streaming](/docs/cloud/conversation-api/streaming-events#ag-ui-event-reference) describes the event formats.

## Explore the model

* [Conversations and messages](/docs/cloud/conversation-api/durable-messaging): Message content, branches, participants, and input requests.
* [Run lifecycle](/docs/cloud/conversation-api/durable-execution): Execution state, results, waiting, and cancellation.
* [Child runs](/docs/cloud/conversation-api/datastores-lineage): Relationships between delegated executions.
* [Access control](/docs/cloud/apis/identity-and-access): Permissions for clients and runtimes.

The [Execution API](/docs/cloud/apis/execution) provides the operations for these resources.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.