Rensei docs
API ReferenceInteractive sessions

Get exact installed-restart acceptance authority for one session.

Dedicated no-store acceptance projection for the rensei-smokes tenant. Requires a human organization admin and project/session access. Returns the exact claim, latest durable fence correlations, lifecycle counters, and heartbeat quarantine rows. Local doctor equality is proved separately by the target-owned observer.

GET
/api/interactive-sessions/{id}/restart-authority

Authorization

headerAuthorizationBearer <WorkOS user access token>

WorkOS user access token created by the Rensei CLI. The authenticated organization is resolved from membership and may be narrowed with X-Rensei-Org.

Path Parameters

id*string
Length1 <= length

Response Body

Exact restart acceptance authority.

application/json
  1. response
schemaVersion*number
orgId*string
Length1 <= length
sessionId*string
Length1 <= length
claim*
fence*
heartbeatQuarantinedSessions*array<>
Example Request
curl -X GET 'https://app.rensei.ai/api/interactive-sessions/string/restart-authority'
Example Response
{  "schemaVersion": 1,  "orgId": "string",  "sessionId": "string",  "claim": {    "claimId": "string",    "assignmentId": "string",    "state": "string",    "releaseCount": 0,    "requeueCount": 0,    "duplicateRuns": 0  },  "fence": {    "fenceId": "string",    "state": "string",    "revision": "string",    "controllerGeneration": 0,    "sessions": [      {        "sessionId": "string",        "shimId": "string",        "processEpoch": 0,        "lastForwardedSeq": 0      }    ]  },  "heartbeatQuarantinedSessions": [    {      "sessionId": "string",      "shimId": "string",      "processEpoch": 0,      "controllerGeneration": 0,      "reason": "string",      "consumesCapacity": true    }  ]}

Re-bind a paused-but-alive interactive session back to active.

Manual counterpart to the relay host_connected CAS: flips a paused/unknown row back to active on evidence other than a live relay handshake (the caller - rensei session rebind - has already verified the local session-shim registry record and harness pid are alive). Idempotent: rebinding an already-active session returns rebound:false with status active and no write. Refuses (409) a terminal row (ended/failed) or one with recorded terminal evidence for this session's shim lineage - a resolved recovery obligation, OR a restart-fence-linked terminal observation, whichever exists - never resurrects either. Single-session granularity only.

Cooperatively stop an interactive session.

Authentication accepts a browser session or a WorkOS user token only; an rsk API key or a BYOA OAuth-agent token is rejected 403. Idempotent-ish: stopping an already-ended session still returns 200 (the underlying Redis/SQL writes are themselves idempotent). 404 - never 403 - for a session belonging to a different org or one the caller has no project access for (no-existence-leak). Teardown drives the cooperative Redis/lock-refresh rail and, belt-and-braces, emits a fire-and-forget relay kill (reason: stopped) when the relay control env is configured. A session that is live on an ADOPTED session-shim lineage (its host daemon restarted and re-owned the harness) cannot be terminalized by the caller - the common release predicate holds its claim until the lineage's own terminal proof. For that case the stop is DELIVERED (relay kill toward the active carrier + the cooperative rail) and the route answers 202 with `stopped:false, delivered:true, pending:"terminal_evidence"`; the row flips to `ended` when the daemon posts the group-reaped tombstone. 409 is reserved for a hold nothing can deliver to (a restart hold window, or an unreconciled lineage): retry. A delivery the relay could not hand to a bound carrier is RE-SENT (on carrier re-attach, on the pty-nudge cycle, and on an interval from the reaper sweep) instead of being frozen behind the permanent stop stamp, and is bounded: the reaper terminalizes the row once the stop has stayed undelivered past its grace. `delivery.deliveryAttempts` / `delivery.lastDeliveryAt` report that progress. A machine principal presenting a x-interactive-spawn-credential header is routed to a separate machine-principal stop path instead of the 403 above, restricted to descendants in that credential's own spawn subtree. Unknown and cross-org targets return 404; a known same-org target outside the subtree is refused by Cedar. A refusal from credential/Cedar attestation returns the typed delegation envelope { code, class, message, axis?, limit?, current?, bindingLevel, bindingScopeId, retryAt?, remedy }.