Rensei docs
API ReferenceWorker Protocol

Read session state

Read session state - Rensei REST API operation reference.

GET
/api/sessions/{id}/status

Authorization

headerAuthorizationBearer <JWT>

Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.

Path Parameters

id*string

Tracker session ID (linearSessionId / trackerSessionId).

Response Body

Full session state.

application/json
  1. response

Full session state object stored in Redis.

linearSessionId*string

Canonical tracker session ID (provider-agnostic; aliases trackerSessionId).

trackerSessionId?string

Provider-agnostic session ID (preferred; linearSessionId is a legacy alias).

issueId*string
issueIdentifier?string

Human-readable issue identifier (e.g. "ENG-123").

providerSessionId?string|null
worktreePath*string
status*AgentSessionStatus

FSM states for an agent session:

  • pending - queued, waiting for a worker
  • claimed - worker has claimed but not yet started
  • running - agent actively processing
  • finalizing - cleanup in progress
  • completed - finished successfully (terminal)
  • failed - encountered an error (terminal)
  • stopped - stopped by user (terminal)
Value in"pending""claimed""running""finalizing""completed""failed""stopped"
createdAt*integer

Unix timestamp (seconds).

updatedAt*integer

Unix timestamp (seconds).

workerId?string|null
queuedAt?integer|null
claimedAt?integer|null
priority?integer

1-5; lower value = higher priority.

promptContext?string
organizationId?string
workType?AgentWorkType
Value in"research""backlog-creation""development""inflight""inflight-coordination""qa""acceptance""refinement""refinement-coordination""coordination""qa-coordination""acceptance-coordination""merge""security"
agentId?string
projectName?string
provider?string

Provider slug (e.g. "claude", "codex").

totalCostUsd?number
inputTokens?integer
outputTokens?integer
lastToolName?string
lastToolCalledAt?integer
toolCallCount?integer
Example Request
curl -X GET 'https://app.rensei.ai/api/sessions/string/status'
Example Response
{  "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}

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.