Rensei docs
API ReferenceSessions ( Public)

Get Sentry issues linked to a session

Returns up to 25 Sentry issues correlated with this session via the session's time range and associated project. Returns `{ configured: false, issues: [] }` when the org has no Sentry connection rather than erroring. The session must belong to the authenticated org.

GET
/api/public/sessions/{id}/sentry-errors

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Path Parameters

id*string

Session ID (raw trackerSessionId or 16-char public hash).

Response Body

Sentry error result.

application/json
  1. response
configured*boolean
issues*array<>
Example Request
curl -X GET 'https://app.rensei.ai/api/public/sessions/string/sentry-errors'
Example Response
{  "configured": true,  "issues": [    {}  ]}

Send a prompt to a running session

Resolves a canonical session id or its public/tracker alias to one tenant-scoped session. Non-terminal input is durably queued on the session heartbeat rail; terminal retries use a durable admission receipt before reset/re-dispatch. A terminal generation is re-dispatched only when its original work type and provider-session resume identity are established from live or durable evidence; missing continuity returns a typed held 409 and creates no queue item. A caller-supplied idempotency key returns the exact current queued/in_flight/applied/dead_lettered active disposition or the original terminal receipt and conflicts on changed input. `in_flight` means claimed by the daemon but not acknowledged as applied; `delivered:true`/`deliveryTier:live` appears only after an exact applied ACK.

Stop a running session

Sends a stop signal to the session: flips Redis status to `stopped`, releases queue/claim/lock, and emits a "Stop signal received" activity to the tracker. A session 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 that lineage's own terminal proof arrives. For that case the stop is DELIVERED (relay kill toward the active carrier plus the cooperative Redis rail) and the route answers 202 with `stopped:false, delivered:true, pending:"terminal_evidence"`; the session goes terminal when the daemon posts the group-reaped tombstone. 409 is reserved for a hold nothing can be delivered through (a quarantined or still-preparing lineage, or a restart hold window): retry.