Skip to main content
Released in TrueForge 0.185.0 — November 2026. This is a breaking change for clients that answer tool approvals, agent questions, or MCP sign-ins.
Before 0.185.0, a turn that needed something from the user (a tool approval, an answer to a question, or an MCP sign-in) ended. The stream closed with turn.done, and you answered by creating a new turn whose input carried the answer. From 0.185.0, that turn pauses instead. It emits turn.update with state.status: "paused", stays open, and waits. You send the answer to the same turn, and the same turn continues to turn.done. One user message is now one turn, however many times the agent stops to ask.

Who is affected

What changed

Migrate with the SDK

Upgrade to the latest SDK:
The snippets below assume a client and a session:

Read the stream and keep an event id

Iterate the stream directly and keep the id of the last event as your cursor. There is no sequence number any more. In Python, open streams with a with block so the connection closes when you stop reading.

Answer tool approvals on the same turn

Stop reading at the paused turn.update. Then subscribe from the last event id, send the approvals to the same turn with createTurnEvents, and read the subscription to see what the answer produced. Subscribe before you send so nothing the answer produces is missed.

Answer agent questions on the same turn

Questions (tool.response_required, for example ask_user_question) follow the same pattern. Collect them exactly as before, stop at the paused turn.update, and send user.tool_response events to the same turn instead of creating a new one.

Continue after MCP sign-in

Resuming with an empty turn is no longer allowed. Once the user has signed in at each server’s authUrl, send user.mcp_auth_continue to the paused turn.

Resume a dropped stream

Resume from an event id instead of a sequence number, and resume paused turns as well as running ones. fromEventId replays starting at that event, so a reply that was mid-stream is rebuilt from its first delta; afterEventId replays only what comes after it.

Poll a turn without streaming

A polled turn that waits on the user now reports paused instead of done with required_actions. Stop polling on paused too, then answer it as above.
A turn can wait on several things at once, for example when parallel subagents each hit an approval. If you come back to a paused turn later, rebuild what is still open from listTurnEvents before you answer. Use an agent has the full SDK recipes, including that bookkeeping.