signal-streamStreaming

Subscribe to GET /v1/runs/{runId}/sse to observe behavior in real time.

Include optional query parameter includeToolCalls if you want to have detailed request/response to be included for step event types.

Event Format

id: <sequential_int>
event: <event_name>
data: <json>

Special heartbeat:

event: keepalive
data: null

A keepalive is emitted every 20 s while at least one client is connected.

Data Events

Event
Description

start

The run begins execution.

step

A step inside the run finishes. Can be used for giving updates to end user about how run is progressing.

authentication

The run needs user authentication (status transitions to AUTH_REQUIRED) or reports its outcome.

run_approval

The run requires manual approval before proceeding (Emitted if Create Run request has approval strategy set).

run_action

Records the approval decision made by the user (approved or denied).

status

Any other status change (e.g. QUEUED, PAUSED).

end

The run finishes (SUCCESS, FAILED, or CANCELED).

Every data event contains:

Payload reference

start

step

authentication

run_approval

run_action

status (queued / paused)

end

Last updated