Skip to main content
A thread is a durable conversation — every agent run writes into one, and the same thread is shared across clients (a run started from the dashboard, CLI, SDK, or a device all land in the same place). Most runs create threads for you (Agents); rt.threads is how you read that history, manage it, and stream it live.

Read history

get() reports view: 'owner' | 'metadata_only' — a non-owner with metadata access gets the summary without event bodies.

Manage

Live updates

Both subscriptions return an unsubscribe function. Use subscribe for durable frames — user/assistant messages, tool calls, run lifecycle — which is what you want for a history view or thread list:
Use subscribeStreaming when you’re rendering a live run and want token-by-token deltas:
Token, reasoning, source, and tool-output deltas are live-only — they stream over the WebSocket but aren’t written to durable history. Final messages, tool calls, and tool results are durable and replay through getEvents().

Methods

For the underlying REST + WebSocket surface, see the Threads API.