Create Run, Stream Output
Create a run and stream the output.
Query Parameters
A conversation to stream: a |-joined namespace, empty for the main agent (the root graph) or a subagent's, such as tools:<task_id>. The stream keeps that conversation's events without those of the subagents it starts (subgraphs that the tools node runs), but with the lifecycle events of every subagent below it. Repeat it to stream several conversations. Events about the whole run, such as metadata and error, always pass. Events of the events and messages modes (not messages-tuple) carry no namespace, so they stream with the main agent's conversation. Subagent events exist only on runs created with stream_subgraphs, except lifecycle events, which come either way. If not provided, all of the run's events are returned.
32Body
Payload for creating a run.
The stream mode(s) to use. lifecycle sends lifecycle|<namespace> events when a subagent (a subgraph) starts and ends: {"event": "started" | "completed" | "failed" | "interrupted", "namespace", "tool_call_id"?, "error"?}, with the id of the tool call that started it, with or without stream_subgraphs. tools sends on_tool_start, on_tool_event, on_tool_end and on_tool_error events with toolCallId and name (from langgraph 1.2.19 and @langchain/langgraph 1.6.0; a tool error's text is never sent).
values, messages, messages-tuple, tasks, checkpoints, updates, events, debug, custom, tools, lifecycle Generate pre-signed URLs for assigning feedback keys to the run.
For each key specified, a unique URL will be generated that can be called to assign the feedback key to the run. See LangSmith Feedback for more details.
Durability level for the run. Must be one of sync, async, or exit. See durability modes for more details.
sync, async, exit Response
Success
The server will send a stream of events in SSE format. The last event is end, with data {"run_id": ..., "status": ...} giving the run's final status: success (also when the run stops at an interrupt), error, timeout, interrupted (the run was cancelled) or, for a stateless run, rollback. A run that was deleted, or rolled back on a thread, has no status left, so its stream ends with its error event instead. If a stream closes with neither, get the run to see how it ended.
Example event:
id: 1
event: message
data: {}

