Sessions

A session groups related traces into one thread, usually a multi-turn conversation. Instead of reading requests one by one, you follow the whole exchange in order and see totals for the session.

The sessions table

Each row shows:

• ID, Created At and Duration (first to last trace)
• Environment and User IDs in the session
• Traces: how many traces the session contains
• Total Cost and Usage (tokens)
• One column per score on the session

Input and output cost, token breakdowns and trace tags can be turned on from the column menu.

Narrow the list with the date range, Env selector and filters, and save the result as a table view. Select rows to Add to Annotation Queue. The sessions table has no search box and no export; use the trace table and filter by session ID for those.

Session detail

Open a session to see:

• Badges: the user IDs in the session, the trace count, the total cost and the session scores.
• Traces: one card per trace in time order, with its input and output, its scores and comments, and a link to open the full trace. Long sessions load in pages.

From the header you can bookmark the session, share it publicly, comment on it, annotate it and add it to an annotation queue.

When to use sessions

• Debugging conversations: follow how a chat evolved across turns to find where it went wrong.
• Conversation-level cost: see what a full conversation cost, not just one turn.
• Conversation-level evaluation: score an entire exchange (see Scores).

Next steps

• Traces & Observations: drill into any trace in a session.
• Users: activity per person.