/workforce/agents/sessions) lists agent sessions across every channel and surface: direct, team, project, personal and group chats, factory workers and managers, workflow steps and system work. Each row is one session, with its tokens and cost. Open a session to read its conversation, its turn-by-turn timeline and its token use over time.
What you can do
- See how many sessions were active in the last 60 seconds, from the live badge beside the title.
- See the number of sessions listed and, when there is spend, today’s session cost, which links to Cost.
- Search sessions, agents and intents, and filter by Agent, Channel, Surface, Status and Model.
- Choose the Range: 5m, 15m, 1h, 24h (the default), 7d, 30d or All.
- Open a session in a drawer, and go from it to Open in Run History.
Filters
Filters are kept in the URL, so a filtered view can be shared or bookmarked. When nothing matches, the page offers Clear filters.
The sessions table
Columns: Session (with a status dot), Surface, Channel, Model, Tokens, Cost and Last activity. Rows load in pages; Load more fetches the next one. With no sessions at all, the table says agents appear once they have conversations: start a chat or run a workflow. Today’s cost in the header is prefixed with~ when some sessions’ totals were summed from only their most recent 200 token events, so the full cost may be higher.
Session detail
Selecting a row opens a drawer and adds#session=<id> to the URL. A link to /workforce/agents/sessions/<sessionId> opens the same drawer.
- Stats — Messages, Tokens (in / out), Cost, Model, Context and Compactions.
- Conversation — the session’s messages, read-only, with a Threads picker when more than one agent thread took part.
- Timeline — the agent’s turns on the session’s primary thread, newest first, with a status pill on any turn that failed.
- Telemetry — total input tokens, output tokens and cost, a chart of cumulative tokens over the session’s lifetime, the models used, and a per-turn table.
Key state to watch
- The live badge — sessions active in the last 60 seconds. It is a recent-activity signal, not proof that a session is still running.
- Stopping and Paused sessions — work that has not finished.
- Failed turns on the Timeline tab — open the related run in Run History for the cause.
- Cost per session — a session whose cost keeps growing is an agent that keeps calling the model.
Related surfaces
- Agents — the agent registry.
- Conversations — chat conversations from the people’s side.
- Run History — runs linked to a session.
- Cost — spend across agents and models.

