Session Detail
Activity stream and health diagnostics.
The Session Detail view wraps the OSS runtime's core SessionPage component with platform-specific health diagnostics and remediation history. For session internals (the activity ring buffer, session state machine, worker protocol), see the runner docs at donmai.dev/docs.
The Session Detail page is your first stop when reviewing or troubleshooting an individual agent run. It combines the real-time activity stream from the runner with Rensei's health diagnostics and remediation history in a single view.
Navigation
/[orgSlug]/[projectSlug]/sessions/[id]
/sessions/[id]The [id] segment is the 16-character public hash visible in the session list. Links from the session list, Linear notifications, and the CLI all point here.
Activity Stream
The main panel is the activity stream rendered by the @donmai/dashboard SessionPage component. Activities appear in chronological order as the agent works:
| Activity type | What it shows |
|---|---|
thought | The agent's reasoning before a tool call or action |
action | A tool invocation with its inputs |
response | A message emitted to the tracker (e.g. Linear comment) |
error | A tool error or runtime exception |
Activities are polled from the Activities API at 15-second intervals while the session is active, and refresh on a live SSE connection when the session is working.
Health Diagnostics
The platform wraps the core session view with a 15-second polling health panel. This panel is what drives the colored dot on the Session List.
The four signals it evaluates:
Remediation History
Below the diagnostics panel, the Remediation History section lists operator actions that have been applied to this session - claim releases, stop signals, and manual status overrides - with timestamps and the source (CLI, UI, or webhook).
Session Status Lifecycle
A session moves through these statuses:
queued → working → completed
→ failed
→ stoppedstopped is the result of a deliberate rensei session stop command or a stop signal from Linear. failed indicates a non-recoverable runtime error. Both terminal states preserve the full activity history for post-mortem review.
Going Deeper
The Session Detail view is designed for quick review. When you need to investigate tool inputs/outputs, memory context, architectural decisions, or raw logs, switch to the Session Inspector - it provides a 7-tab deep-debug view of the same session.
To send a follow-up prompt to a running or paused session, see Interactive Chat.
Related Pages
- Session List - project-scoped list with health dots and filters
- Session Inspector - 7-tab deep debug: tool calls, context, decisions, logs
- Interactive Chat - send prompts or stop sessions from the CLI
- Activities API - cursor-based activity polling API
- Linear Agent Session - how sessions connect to Linear's AgentSession