Get queued session detail for cloud runners
Lets a cloud runner-in-box (e2b/modal/daytona) fetch its session detail from the platform rather than the local daemon control API (`127.0.0.1:7734/api/daemon/sessions/:id`), which does not exist inside a cloud sandbox. The provisioner stamps `DONMAI_DAEMON_URL=<platform-url>` into the box's env so `donmai agent run` fetches its detail here. Source of truth is the Redis `work:items` hash. The full payload is available **only while the session is still QUEUED** - it is deleted on claim. Auth: bearer worker token (runtime JWT or legacy `WORKER_API_KEY`). The response includes `authToken`, system prompts, repo URL, and org ID - not readable without authentication.
Authorization
workerJwt Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.
In: header
Path Parameters
Session ID (trackerSessionId / linearSessionId).
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/daemon/sessions/string"{
"sessionId": "string",
"issueId": "string",
"issueIdentifier": "string",
"priority": 0,
"queuedAt": 0,
"prompt": "string",
"providerSessionId": "string",
"workType": "research",
"sourceSessionId": "string",
"projectName": "string",
"repository": "string",
"kits": {},
"platformUrl": "http://example.com",
"organizationId": "string",
"linearSessionId": "string"
}{
"error": "Session not found"
}{
"error": "Session not found"
}{
"error": "Session not found"
}Observe privileged-verification finalization status
Read-only status observation bound to the exact ordered invocation, claim, confirmation digest, consumed attempt number, and current receiver-bound runtime JWT. It never creates finalization/evidence authority, acquires a lease, or resumes a workflow. Pending is HTTP 202; confirmation-final HTTP 200 streams exact retained first/duplicate response bytes selected by permanent child disposition; deadline-final HTTP 200 returns the exact nine-member status.
Post agent activity (thought/action/response)
Stores activity in the in-process ring buffer and forwards `thought | action | response` to the Linear AgentSession. Linear forwarding is fire-and-forget (non-fatal on failure).