What happened in the task, and who did it [read]
Changed onOne time-ordered list assembled from what the task's sessions, files, artifacts and connector calls already recorded and from the task's work graph events: each message with who sent it (a person, an agent, a workspace key or a share-link guest), each tool call an agent's message carries (tool, a short summary of its arguments, ok or error), the sessions it started, requests and their answers, decisions and outcomes, mentions and assignments, task file versions, artifact publications and comments, connector calls (app, method, host, status, and the person whose turn made the call), recorded meetings, every other event of the task by its own kind (connector and context results with links to their stored bodies, stored files, handoffs, GitHub pull requests and checks linked to a session), and each session's cost. An event that describes a row already listed appears once. Nothing is stored. Each part follows its own read rule: a session the caller may only view contributes its messages' text and nothing else; an artifact appears only when the caller may open it; events come from the task's workspace log and the caller's own private log only, so a teammate's connector replies are never shown. The story has no size limit: page through it with cursor. With by=session, a helper or handoff session's id names its task. 400 invalid_request for a cursor this route did not return or an order that differs from the cursor's.
Request
- Base URLhttps://api.agentsky.dev/v1
- URLhttps://api.agentsky.dev/v1/tasks/{id}/story
- AuthHTTP bearer
Path parameters
The task id: the id of its root session (sess_…)
Query parameters
Entries per page
asc reads from the task's start forward, desc from now back. Without it (and without cursor) the page is the newest entries, oldest first
A page's next_cursor; the next page keeps that page's order
Resolve this session to its existing task root.
Response
OK
Changes
- info
endpoint added
- info