Get Agent Session State
GET /agent/sessions/{session_id}/state
Everything needed to render one session from cold.
THREE sources in one answer, and the difference between them matters:
messages are the chat bubbles, steps are what the agent actually did
(tool calls, reasoning summaries) and work_item_status is whether it is
still going. A session driven by a work item has richer steps than
messages, and a plain chat has only messages - so a client that renders
only one of them will show an empty conversation for half the sessions.
404s on a session the caller cannot see, rather than 403 - existence is not leaked by distinguishing the two.
Authorizations
Parameters
Path Parameters
Session id (UUID).
Session id (UUID).
Header Parameters
Responses
200
Successful Response
object
An open envelope for a hydration or voice answer.
Open because session hydration returns the agent’s STEPS as well as its
messages, and a step’s detail is whatever the tool that produced it
reported. That set grows with every tool the platform gains, and a pinned
mirror would drop the detail of exactly the newest ones - which on a
transcript surface reads as the agent having done less than it did.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error