Emitted when a partial code snippet is streamed by the code interpreter.
Emitted when the code snippet is finalized by the code interpreter.
Emitted when the code interpreter call is completed.
Emitted when a code interpreter call is in progress.
Emitted when the code interpreter is actively interpreting the code snippet.
Emitted when new summary content is sampled for a compaction trigger. Contains no summary content.
Emitted when a file search call is completed (results found).
Emitted when there is a partial function-call arguments delta.
A streaming event that indicated a shell command was added to a tool call.
A streaming event that indicated a shell command was incrementally updated.
A streaming event that indicated a shell command was completed.
A streaming event that indicated shell call output was incrementally added.
A streaming event that indicated shell call output was completed.
An event that is emitted when a response finishes as incomplete.
Over WebSocket, steering can finish a response with
response.incomplete_details.reason set to steered, followed automatically
by a successor response.created that commits the queued steering input.
Emitted when a delta is added to a reasoning summary text.
Emitted when an image generation tool call has completed and the final image is available.
Emitted when an image generation tool call is actively generating an image (intermediate state).
Emitted when an image generation tool call is in progress.
Emitted when a partial image is available during image generation streaming.
Emitted when there is a delta (partial update) to the arguments of an MCP tool call.
Emitted when the arguments for an MCP tool call are finalized.
Emitted when the list of available MCP tools has been successfully retrieved.
Emitted when the attempt to list available MCP tools has failed.
Emitted when the system is in the process of retrieving the list of available MCP tools.
Emitted when an annotation is added to output text content.
Event representing a delta (partial update) to the input of a custom tool call.
Event indicating that input for a custom tool call is complete.
Emitted when an error occurs while processing a Responses WebSocket request.
Details about the error.
An optional classification; clients must accept additional values.
Emitted when steering input has been validated and queued. Acceptance means
the server owns the input, not that it has been applied. The successor’s
response.created event is the commit point. If accepted input cannot be
committed, response.steer.failed returns it with the same steering ID.
When the response stops for client-owned tool output or approval, the input
remains queued and response.steer.pending is emitted after
response.completed. Fill the pending event’s required_input stubs with
saved results and send one matching explicit response.create per parent.
Do not resend accepted input while it is still queued.
Emitted when accepted steering input remains queued after the target
response completes. The server still owns the input. Do not resend it.
The successor’s response.created event is the commit point.
When reason is waiting_for_required_input, this event follows
response.completed while the response waits for the tool results or
approval decisions identified by required_input. Copy those stubs, fill
their result fields using the ordinary response.create input schemas,
and submit one continuation per parent with the same previous_response_id
and WebSocket lane. Use saved results without rerunning tools. The queued
steering input is prepended in submission order to the continuation’s
input. That explicit request retains its own settings.
This notification is emitted at most once per steering submission. Multiple submissions for the same parent can report the same required inputs; they do not each require a separate continuation.
Emitted when steering input is rejected or cannot be committed to a
successor response. Returns the original, uncommitted input so the client
can carry it into response.create when appropriate. Invalid input must
be corrected before retrying.
Failures after acceptance include the same steering ID. Failures before an
ID is allocated omit steer.id. A lost connection or missing acknowledgement
leaves the outcome unknown; it is not proof that the input was rejected.