Continue a thread with a user message
Appends a user message to an existing thread to continue it. The effect depends on the current thread state: a completed/failed/waiting thread is re-queued and re-run with the message appended; a still-running or queued thread receives the message on its next turn (right after the pending tool response). Threads waiting for approval, handed off to a subagent, or still being created cannot be continued this way.
Authorizations
Use JWT token for authentication
Headers
Free-text label recorded with the call, to tell apart the integrations that use the same key.
Path Parameters
The ID of the thread to continue
Body
The user message to append to the thread to continue it (string or object). Behaviour depends on the current thread state: a running/queued thread receives it on its next turn (after the pending tool response); a completed/failed/waiting thread is re-queued to run again with the message appended.
"Also include a summary of the previous steps"
Response
Message added to the thread
Enhanced token usage with cost breakdown
Thread metadata containing prompt template parameters and tenant token
Tenant ID for multi-tenant environments
"tenant-123"
Whether this thread is a subthread created by a parent handoff
false
ID of the parent thread (if this is a subthread)
"64f5a5b8c123456789abcdef"
ID of the parent agent (if this is a subthread)
"64f5a5b8c123456789abcdef"
Tool call ID in the parent thread that triggered this subthread
"call_abc123"
IDs of subthreads still executing (for parent threads)
All subthread IDs ever created during handoffs (for parent threads)
List of task for the thread execution
Pending async tool calls awaiting an external response. Each entry exposes the callbackUrl the external system must POST the response to.
Reason the thread is paused (e.g. waiting for an async tool response).
Epoch milliseconds when a paused thread is scheduled to resume. Only set while the thread is paused with a scheduled resume.
1721551200000
Epoch milliseconds when the thread was paused.
1721550000000
Audit trail of the core-memory blocks this thread saw: one snapshot (render revision + the injected entries as structured JSON) per distinct revision, including mid-run edits. Present only for agents with core memory enabled.
Structured recall events of this thread: the automatic long-term-memory recall at run start plus every memory-tool lookup, each with the query and the facts/entities it surfaced. Present only for agents with long-term memory enabled.