Continue a session that ran out of usage, on another account or model
With account: the work carries over to a new session on that account, in the same folder, seeded with where the old one stopped; the answer names the new session, and a second call for the same limit answers with the same one. runtime (default: the session's own) moves it to another runtime, only when the account advisor offered that runtime's account; that session starts with the other runtime's own model and effort, and never with more permission than the old one had (full autonomy is not carried over). With only model: the same session switches to that model and continues. A session the account advisor claimed (a Flow run) is handed to the advisor, and the answer has no sessionId until the advisor reports the new session; the session's plan shows the handoff meanwhile. A session that did not start here (a room, a schedule, a chat binding) can only wait (409).
Path Parameters
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/sessions/497f6eca-6276-4993-bfeb-53cbbbba6f08/continue" \ -H "Content-Type: application/json" \ -d '{}'{ "sessionId": "string"}