Rensei docs

Session List

Project-scoped list, health dots, and filters.

The session list shows every agent run that Rensei has dispatched for your project. For a deeper look at what happens inside a run, see the Session Detail and Session Inspector pages. The underlying session data model is documented on the OSS runtime at donmai.dev/docs.

The session list gives you a live, project-scoped view of every agent session - queued, active, and recently finished - including real-time health indicators and cost/duration at a glance.

The list is available at:

/[orgSlug]/[projectSlug]/sessions

You can also reach it from the left sidebar inside any project. The URL scope is important: sessions are always filtered to the project in the path. The API route (GET /api/public/sessions) automatically picks up the project from the Referer header when the dashboard component doesn't pass an explicit projectId, so the session list stays scoped without any extra parameters.

What the List Shows

Each row in the session list surfaces:

ColumnDescription
Health dotGreen / yellow / red indicator based on stuck-signal detection (see below)
IdentifierThe issue or task identifier the session is working on (e.g. ENG-124)
Statusqueued · working · completed · failed · stopped
Work typedevelopment · research · qa · coordination · etc.
ProviderThe sandbox provider the session ran on (e.g. local, e2b, vercel)
DurationWall-clock time from claim to completion
CostEstimated USD spend for the session

Health Dot

The colored dot beside each session summarises whether the agent is progressing normally.

Green

No active stuck signals. The session is progressing or finished cleanly.

Yellow

One or more advisory signals: Long Running or Stale Heartbeat. The agent is still alive but slower than expected.

Red

A blocking signal is active: Tool Loop Stuck or Claim Stuck. Operator attention may be needed.

The four signal types the platform tracks:

SignalMeaning
LongRunningSession has been active longer than the configured SLA threshold
StaleHeartbeatThe worker has not sent a heartbeat within the expected window
ToolLoopStuckThe agent is calling the same tool in a tight, non-progressing loop
ClaimStuckA claim lock was acquired but no work is being dispatched

Click the row or health dot to open the Session Detail view with the full diagnostics panel.

The list supports:

  • Status filter - show only working, completed, failed, or stopped sessions.
  • Identifier search - filter by issue/task identifier prefix (e.g. ENG-).

Filters are applied client-side on the current page; pagination is cursor-based so very large session lists do not load all rows at once.

API: List Sessions

The session list is backed by GET /api/public/sessions. It accepts session-cookie or rsk_* Bearer auth.

curl https://app.rensei.ai/api/public/sessions \
  -H "Authorization: Bearer rsk_live_…"

To scope to a specific project, pass either the project ID or its slug:

# By slug
curl "https://app.rensei.ai/api/public/sessions?project=my-project" \
  -H "Authorization: Bearer rsk_live_…"

# By ID
curl "https://app.rensei.ai/api/public/sessions?projectId=proj_abc123" \
  -H "Authorization: Bearer rsk_live_…"

The response is a paginated list. Each item includes a hashed public id - this 16-character identifier is what you pass to the Activities API, the prompt, and stop endpoints.

{
  "sessions": [
    {
      "id": "a1b2c3d4e5f6a7b8",
      "status": "working",
      "issueIdentifier": "ENG-124",
      "workType": "development",
      "startedAt": "2026-06-02T14:22:00Z",
      "costUsd": "0.14",
      "health": {
        "healthStatus": "green",
        "stuckSignals": []
      }
    }
  ],
  "cursor": "…"
}

Pass ?cursor=<value> to fetch the next page.

Session Detail

Activity stream and health diagnostics.

On this page

Navigating to the Session ListWhat the List ShowsHealth DotFiltering and SearchAPI: List SessionsRelated Pages