Session Inspector
7-tab deep-debug inspector.
The Session Inspector is a deep-debug panel that exposes every internal signal from an agent run - tool calls with full I/O, derived context keys, architectural decision provenance, stuck-signal health, aggregate tool statistics, and raw logs - organized into seven tabs over a live SSE connection.
Navigation
/[orgSlug]/[projectSlug]/sessions/[id]/inspectThe Inspector is reached by clicking the Inspect button on a Session Detail page, or by navigating directly with a session's 16-character public ID.
Live Connection
The Inspector connects to the session's SSE stream (GET /api/sessions/[id]/stream) via the useSatelliteInspector hook. Connection state is displayed in the header:
| Indicator | Meaning |
|---|---|
| Wifi icon (connected) | Live updates flowing; data is real-time |
| Wifi-off icon (disconnected) | Polling fallback active; data refreshes every ~15s |
For completed sessions the SSE connection closes gracefully after terminal activities are received, and the Inspector switches to the static persisted view.
The Seven Tabs
Activity Stream
A chronological feed of every activity the agent emitted during the session. Each activity has a type (thought, action, response, error) and a timestamp. Activities are the same data the Activities API returns - the Inspector just renders them with full formatting and diff highlighting for multi-turn edits.
Activities are stored in an in-process ring buffer while the session is active, and persisted to session_activities rows in Postgres for completed sessions.
Typical Debugging Workflow
Open the Inspector for the failing session. Check the Health tab first - if a stuck signal is active, that's the proximate cause.
Switch to Calls and filter to failed tool invocations (red badge). Expand the inputs/outputs to find the root failure.
Check Context to confirm the agent had the right working directory and last-edited file at the time of the failure.
If the agent made an incorrect architectural assumption, check Decisions to see what was in the context budget.
For daemon-level failures (crashes, permission errors), check Logs for the raw process output.
Related Pages
- Session Detail - activity stream and health diagnostics
- Session List - project-scoped session list
- Context Derivation - how tool calls become context facets
- Activities API - programmatic access to the activity feed
- Session Topology - fleet-wide session graph