API ReferenceWorker Protocol
Read session state
Read session state - Rensei REST API operation reference.
AuthorizationBearer <token>
Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.
In: header
Path Parameters
id*string
Tracker session ID (linearSessionId / trackerSessionId).
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/api/sessions/string/status"{
"linearSessionId": "string",
"trackerSessionId": "string",
"issueId": "string",
"issueIdentifier": "string",
"providerSessionId": "string",
"worktreePath": "string",
"status": "pending",
"createdAt": 0,
"updatedAt": 0,
"workerId": "string",
"queuedAt": 0,
"claimedAt": 0,
"priority": 0,
"promptContext": "string",
"organizationId": "string",
"workType": "research",
"agentId": "string",
"projectName": "string",
"provider": "string",
"totalCostUsd": 0,
"inputTokens": 0,
"outputTokens": 0,
"lastToolName": "string",
"lastToolCalledAt": 0,
"toolCallCount": 0
}{
"error": "Session not found"
}{
"error": "Session not found"
}Post security scan event
Post security scan event - Rensei REST API operation reference.
FSM status transition
Drives the session FSM: `pending → claimed → running → finalizing → completed | failed | stopped` Terminal transitions trigger side effects: cost persistence, fleet quota accounting, Linear `agentActivityCreate`, claim release, inbox archival, issue lock release, and next-pending-work promotion.