v4

latestOpenAPI 3.1.02026-08-08278476614.0 KB

chat

Resume Chat Main Agent

Re-attach to a project's in-flight chat run after a mid-stream refresh.

Read-only second reader: tails the existing workflow's durable stream (read_stream replays from offset 0 → the full ordered sequence: the user-message echo, every delta so far, then the terminal) WITHOUT starting a run or claiming a slot. If no run is live the generator yields nothing; the FE then sees no terminal and falls back to reloading persisted history (the empty replay is the signal that the run finished and released its slot before this reattach).

post/api/v1/chat/stream/resume

Request body

project_idstring uuid required

The project whose live chat run to re-attach to.

expected_run_idstring nullable

The run id the chat GET reported as active. The reattach tails this run only; if the pointer has since moved to a newer run, the server yields nothing so the client reloads persisted history. Omit to tail whatever run is currently active.

Response

Successful Response

{"stackTrail":"paths:/api/v1/chat/stream/resume:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}