Threads and runs

Every interaction with an agent is recorded so you can see exactly what it did. Two objects carry that record: the thread and the run.

Threads

A thread is a single conversation with an agent. It holds the ordered message history — your messages, the agent's replies, and the tool calls in between. Threads live under the account and are per-agent, so a fact the agent learned in one thread isn't automatically in another (that's what memory is for). Open threads from the project's threads view.

Runs

A run is one agent turn inside a thread — everything the agent does between receiving an input and finishing its reply. A run is created each time the agent is invoked, whether interactively, on a schedule, or from a trigger. Each run produces one or more messages in the thread and records the model calls, tool calls, duration, and cost.

Open a run to see two views:

• Narrative — one step per human-meaningful operation the agent performed (a tool call, a generated reply, a triggered action), with status, duration, and cost. Retries and model fallbacks collapse, so you see the verbs, not the plumbing.
• Trace — the full event stream as an indented tree with raw payloads, for when you need to debug.

Reading a run's outcome

A finished run reports a summary line like succeeded · 5.9s · $0.18. The parts:

• Status — succeeded, failed, or in progress. Individual steps carry their own status; a step that ultimately failed after retries shows an attempt count.
• Duration — wall-clock time for the whole turn.
• Cost — what the run spent, in credits ($0.01 each). Costs roll up from the model and tool calls the run made.

If a run finished but did nothing you expected — for example it succeeded but spent nothing — that usually means no model call happened. Read Why did my run fail? for how to diagnose it.

Where to go next

• Why did my run fail? to debug an unexpected outcome.
• Memory for how facts carry across threads.