Sessions
Sessions are the unit of work in InfraScout. A session is one playbook run against one host (or a group of hosts), with a defined start, a transcript, a set of executions, and the insights it produced. The Sessions page lists every session your identity is allowed to see, newest first.

Layout
The page header has the title, a one-line description, and a Refresh button. Two filters live above the table: a status dropdown (All, Pending Review, Completed, Running, Failed, Cancelled) and a free-text search that matches on hostname or session definition.
Each row shows:
- Agent / Host — the hostname the session ran against.
- Definition — a one-line summary of what the session was about (the playbook title or the user-supplied description).
- Status — colored chip; the most common values are Completed, Pending Review, and Failed.
- Executions — how many remote commands ran during the session.
- Insights — how many findings the session produced (open and resolved combined).
- Started — relative timestamp.
Click a row to open the session detail page, where you can read the full transcript, every executed command with its output, and the insights generated.
Status workflow
Sessions move through a small set of states:
- Pending Review — the assessment finished and produced findings, but a human has not yet confirmed them.
- Completed — reviewed and closed; results are final.
- Running — the playbook is still mid-flight.
- Failed — the agent or the playbook hit an unrecoverable error.
- Cancelled — a user stopped the run before completion.
The default sort puts the newest sessions first. Use the status filter to focus on whichever state you triage from — most teams come here looking for Pending Review.
Real-time updates
The list subscribes to the same SSE channel as the dashboard's "Recent sessions" panel. When a new session starts, finishes, or transitions to a new state, the row updates in place — no manual refresh required.
Visibility
Each session inherits its visibility from the playbook and the agent group it ran against. You only see sessions whose visibility list includes your identity (directly or via group membership). If you need to debug a session you cannot see, an admin can grant visibility from the admin Sessions area.