Session Groups: Every Conversation Owns Its Work
May 11, 2026 · InfraScout Team
When you run an assessment through chat, InfraScout opens sessions against the agents it needs to inspect. Until now those sessions lived on their own, loosely tied to the conversation that spawned them. Ending a chat left its sessions running, audit reviewers had no single place to see everything a conversation touched, and nothing stopped two overlapping runs from racing against the same agent. With this update, every conversation now owns its work through a session group — a container that ties a conversation to the agent sessions it started and gives them a shared, predictable lifecycle.
The result is cleaner accounting from start to finish. A conversation creates its group automatically, the group tracks every session underneath it, and when the conversation ends, its sessions end with it. Nothing is left running in the background, and reviewers get one record per conversation to audit.
One conversation, one group
Each chat conversation gets a session group the moment it begins — including assessments you launch from a finding through Get Help. You do not create or manage the group yourself; it is provisioned for you and follows the conversation for its entire life. Every session the conversation opens against an agent is recorded under that group, so the relationship between "this conversation" and "the work it did" is always explicit.
This grouping is what makes the rest of the lifecycle possible. Because the group knows exactly which sessions belong to a conversation, InfraScout can reason about them as a set — closing them together, counting them, and showing them in one place — instead of chasing loose sessions scattered across your tenant.
Sessions close with their conversation
When a conversation ends — whether you end it yourself or it wraps up on its own after the work is complete — its session group closes, and every session underneath it closes too. There are no orphaned runs left lingering after the chat is over. The conversation, its group, and its child sessions all move to a settled state together, so the audit trail reflects reality the moment the work stops.
This cascade is the headline change for anyone who reviews activity after the fact. Previously, a finished conversation could still show running sessions, which muddied the picture of what was actually in flight. Now an ended conversation is unambiguously done, and a running session always means active work.
A clear signal when a chat has ended
Once a conversation has closed, the chat makes that obvious. In place of the message box you see a banner explaining that the conversation has ended, why it ended, and when — with quick actions to review the session group behind it or start a fresh chat that carries your context forward. The conversation's tab and sidebar entry reflect the ended state too, so you are never typing into a chat that can no longer act.
Ending a conversation is available to its owner and to administrators while the chat is active, behind a confirmation so you do not close work by accident. Once a conversation is ended, it stops accepting new messages — there is no ambiguity about whether a closed chat might still run a tool.
One running session per agent, per group
Within a single group, an agent can have only one running session at a time. If a conversation tries to open a session against an agent it is already working with, InfraScout reuses the existing one rather than starting a competing run. Stale sessions left idle from earlier in the conversation are retired automatically the next time the group is touched, so a group never accumulates a backlog of half-finished runs against the same machine.
This guarantee removes a whole class of confusing outcomes — two runs writing findings against the same host in the same breath, or a command landing on a session you thought had moved on. Each agent in a group has exactly one live session, and that is the one your assessment is using.
A first-class view for audit and review
Session groups are now a surface you can browse, not just plumbing. As an administrator you get a list of every session group across the platform with its kind, status, child-session count, and duration at a glance, and a detail view that lays out a conversation's full lifecycle on a timeline alongside the sessions it ran and the conversation it belongs to. From the detail view an administrator can end an active group directly when a review calls for it.
Every user also gets a session-groups view scoped to their own work, mirroring the same layout. It replaces the old flat list of sessions with a conversation-first picture: open a group to see its timeline, the runs underneath it, and the conversation that drove them. Individual session detail is still a click away when you need to drill into one specific run.
For security teams, this is the practical payoff of the whole change. One conversation maps to one auditable record that shows what was reviewed, which agents were touched, when each session ran, and how the whole thing concluded.
What you may have seen during the rollout
To put existing conversations on the new model, InfraScout grouped each prior conversation under its own session group when this update landed. Any sessions that were still marked running at that moment were recorded as interrupted rather than carried forward, so the historical record stays honest about what was actually active. New conversations created after the rollout get a group from the start with no action on your part.
Try it
Start a new assessment conversation and watch it behave as a single unit: the work it does against each agent stays grouped, ending the chat closes everything cleanly, and the session-groups view gives you one record to review afterward. Administrators can open the platform-wide session-groups list to audit activity across every conversation.
Questions or feedback? Reach us at info@infrascout.cloud.