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.
User-wide CLI Inbox
rensei inbox lists sessions across the organizations and projects your user
login can access. Saved org and project defaults do not filter this list.
Use a user login; organization API keys and launched-agent sessions cannot open
this operator view.
rensei auth add --user
rensei inbox
rensei inbox --json --no-interactive
rensei inbox --filter-org acme --state active
rensei inbox --project-id <project-id>Explicit --org narrows the list. Pair --project with an explicit --org,
or use --project-id to filter across organizations. Other filters are
--type (typed_dispatch, workflow_run, interactive) and --state
(blocked, active, review, completed, closed). The JSON response includes
the next opaque cursor, total, and partial organization failures; pass the cursor
with --cursor to continue. Handled rows are hidden in the visible list unless
you use --show-handled; JSON retains the loaded projection.
Select a row to inspect its shared session details and recent output. Missing
model or harness metadata stays unknown. This is a user-wide view; use
rensei host watch for the separate local-host dashboard.
Inbox currently provides a session list and detail view. Enter on a live interactive session gives its terminal the full screen. Press Ctrl-\ followed by d to detach and return to Inbox. Retained terminal panes and replay are not available in this version. Ctrl-C is forwarded to the attached session; it is not the detach shortcut.
Inbox keeps the selected user identity for its lifetime. Changing or removing that saved login requires reopening Inbox; authentication refusal clears cached rows and selected output. A temporary fetch or storage failure instead marks the retained view stale.
Navigating to the Session List
The list is available at:
/[orgSlug]/[projectSlug]/sessionsYou 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:
| Column | Description |
|---|---|
| Health dot | Green / yellow / red indicator based on stuck-signal detection (see below) |
| Identifier | The issue or task identifier the session is working on (e.g. ENG-124) |
| Status | queued · working · completed · failed · stopped |
| Work type | development · research · qa · coordination · etc. |
| Provider | The provider the session ran on (e.g. local, e2b, vercel) |
| Duration | Wall-clock time from claim to completion |
| Cost | Estimated 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:
| Signal | Meaning |
|---|---|
LongRunning | Session has been active longer than the configured SLA threshold |
StaleHeartbeat | The worker has not sent a heartbeat within the expected window |
ToolLoopStuck | The agent is calling the same tool in a tight, non-progressing loop |
ClaimStuck | A 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.
Filtering and Search
The list supports:
- Status filter - show only
working,completed,failed, orstoppedsessions. - 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.
Related Pages
- Session Detail - activity stream and health diagnostics for a single run
- Session Inspector - 7-tab deep-debug view (tool calls, context, decisions, logs)
- Interactive Chat - prompt or stop a session from the CLI
- Activities API - stream activities programmatically
- Session Topology - live graph of all active sessions across a project