Chat

How an interactive Chat thread and its turns relate to dispatched Runs.

A Chat is a long-lived interactive thread that a person starts. Chats are created in the product UI; the Developer API does not provide a route to create a Chat. After a Chat exists, its messages and turn state can be read and managed through the Chat API. See the API overview for the Chat endpoint family.

Chat turns

A chat turn is one user message and the assistant work that it triggers. A turn can answer directly in the conversation, or dispatch a Run when it needs structured work. The conversation continues with the Run's result, so the Chat remains the place where the person and assistant keep their context.

A turn can pause while it waits for an approval. This can be a tool call that the Project policy routes to a person, or an action that the automation policy gates. Answering the approval resumes the turn. See Answer a pending chat approval for the approval flow.

Discussions

A discussion is a thread anchored to a message in a parent Chat. The API identifies the relationship with parentChatId, anchorMessageId, and contextTailSeq, which lets the discussion retain the relevant context from its parent message.

Chats and Runs

See Workflow, Run, and Attempt for the Run lifecycle. Chats optimize for conversational continuity, while Runs are dispatched by the system, such as after an approved Chat tool call, on a schedule, or in response to an API request.