Skip to main content
Every conversation your MCP sees lands under Sessions, newest first. Open one to read the agent’s goal, tool calls, outcome, and the reconstructed conversation.

​
The session list

Sessions are goal-phrased — you scan what users wanted, not session IDs. Each row shows an outcome dot, the session goal, and the client it came from. Filter by outcome with one click: You can also filter by use case, and deep links from Use cases and Issues arrive here pre-filtered — the active filter shows as a clearable chip. Some sessions show no outcome yet: judging runs after a session has been idle for a few minutes, and sessions without enough evidence to judge stay unscored (they’re excluded from pass rate).

​
Session replay

Opening a session gives you two views: Overview — the verdict card (outcome, score, and the judge’s reasoning) above a waterfall of every tool call with timing and status. Failures and errors are visible exactly where they happened, including tool results your server returned as errors. Conversation — the session reconstructed as a dialogue: the user’s asks as they evolved turn by turn, the agent’s thinking on the left, and the calls it made in between. This is where user_intent and agent_thinking reported by the SDK surface — see What the SDK captures.
When something breaks, you see exactly where: which turn, which call, what the agent believed at the time, and what your server returned.

​
How outcomes are decided

Once a session goes idle, a judge model reads it end-to-end and scores whether the user got what they asked for. The verdict includes the outcome label, a score, and the evidence. Pass rate everywhere in the dashboard is successful ÷ judged sessions.