The Sessions page reconstructs complete interactions from start to finish. While Monitoring surfaces individual events as a continuous stream, Sessions groups those events into the conversations and workflows they belong to, so the focus is on what happened across an entire interaction rather than at a single point in it.

This is the page to use when investigating how a multi-turn conversation unfolded, tracing an agentic workflow across multiple steps and actors, or understanding the full context around a signal that fired or an action that was blocked.

Reviewers, governance teams, and engineers use it to answer questions like:

• Why did a session end in a blocked outcome?
• Where in an interaction was a risk introduced?
• How did the participants in a workflow interact with one another?

What Is a Session?

A session is a group of related events that make up a single interaction.

Viewing Sessions

Sessions are always scoped to a single use case, so the page requires a use case to be selected before any sessions are shown. A use case can be selected from a dropdown or from a card grid on the page. This scoping reflects how sessions are organized: each session belongs to one use case.

After a use case is selected, the session list displays one row per session. The table is the entry point for finding a specific session to investigate, and its columns surface enough detail to triage which sessions need a closer look.

• Start Time and Intent: The session start time and the detected intent.
• Session ID: The unique identifier for the session.
• Input Preview: A preview of the input that began the session.
• Events: The number of events in the session.
• Outcome: Whether the session was passed, modified, or blocked.
• Duration: The elapsed time of the session. See Understanding Session Timing below.
• Safety: A green check mark when the session has no Safety alerts, or the count of alerts across the session when there are.
• Security: A green check mark when the session has no Security alerts, or the count of alerts across the session when there are.
• Total Tokens: The combined input and output tokens across the session.
• Total Analysis Time: The total time spent analyzing the session's events. See Understanding Session Timing below.

Understanding Session Timing

Sessions surface three time-related values that are easy to confuse. They measure different things:

• Duration: How long the session lasted from its first event to its last.
• Total Analysis Time: How much time was spent evaluating the session's event for signals. This measures processing effort, not elapsed time, and does not include the time spent waiting on the model or the user.
• Wall Duration: Shown in the Session Summary within Session Flow.

Session Details

Clicking a session row opens the Session details panel, which summarizes the session before a reviewer drills into individual events. Four summary metrics describe the session at a glance:

• Total Events: The number of events in the session.
• Duration: The elapsed time of the session.
• Signals: The number of signals detected across the session.
• Total Tokens: The combined input and output tokens across the session.

The panel also displays the detected Intent and the associated Use Case. A Session Events button in the panel header navigates to the full event list for that session.

Session Flow

Session Flow visualizes the structure of an interaction so a reviewer can understand its shape at a glance: who participated, in what order events occurred, where signals fired, and where input or output was blocked or modified. It is most useful for making sense of complex agentic workflows, where the sequence and relationships between actors are hard to follow in a table. Session Flow is currently in beta, so its output may change and should be read alongside the underlying event data rather than relied on as the sole record.

What the Visualization Encodes

Across the views, a few encoding principles hold in common.

• Color identifies the actor in an event.
• The sender of an event is marked by an origin dot, and the received is marked by the event itself, so you can read which actor initiated each exchange.
• Issue indicators show when an input or an output was blocked or modified, with separate markers for the input side and the output side.
• Each event is numbered in the order it occurred.

Each view applies these principles to a different layout, and the specific of size, position, and time differ from one view to the next. Every view includes a "How to read" tooltip that gives the full legend for that view, so the descriptions below cover what each view is for rather than every glyph.

Views

Session Flow offers four view, each a different way to read the same interaction. Switch between them depending on the question you are trying to answer.

• Flow: Lays events out left to right in chronological order as connected sender-receiver pairs, with concurrent events stacked vertically. Use it for a general read of how an interaction progressed and who exchanged what with whom.
• Orbit: Arranges actor types as rings around the session at the center, with each event drawn as an arc whose position marks its start time and whose length marks its duration. Use it to see a single actor's activity across the whole session and where each event falls in the session's elapsed tim.
• Lanes: Giver each actor a horizontal swim lane grouped by actor type, plotted against a shared time axis running left to right. Use it to compare what different actors were doing at the same moment and to spot overlap or gaps in activity.
• Sequence: Runs top to bottom in elapsed time, with actors as columns and an agent grouped together with the tools it called. Use it to follow the strict chronological order of events and trace them back-and-forth between specific actors.

Events can be pinned to keep them in focus, and the views support zoom and pan for navigating large sessions. For the complete visual legend of any view, including how size, color, and issue indicators are drawn in that view, open its "How to read" tooltip next to the "Beta" tag.

Session Summary

The Session Summary panel within Session Flow aggregates the session into a single set of figures and breakdowns:

• Event Count: The total number of events in the session.
• Wall Duration: The elapsed time of the session. See Understanding Session Timing above.
• Token Counts: The input and output token totals for the session.
• Participant Counts: The number of participants involved in the session.
• Outcome Counts: The number of events ending in each outcome.
• Token Volume: The distribution of tokens across the session.
• Signal Actions: A breakdown of the actions taken in response to detected signals.
• Participants: A breakdown of the actors involved and their activity.
• Event Type Distribution: A breakdown of the session's events by event type.
• Top Interactions: The most frequent interactions within the session.