Skip to main content
The Sessions page lists every agent session in the team with what it used and cost. Open a session to replay it: every prompt, response, and tool call in order, alongside its token timeline, files, and git activity.

​
The sessions list

At the top, four cards summarize the period: Active now (sessions reporting in the last 10 minutes), Model calls, Tokens burned, and Spend (or Net spend, or Output tokens, depending on the usage view). Totals count whole sessions.

​
Finding sessions

  • Search across session ids and titles, users, models, providers, clients, and repositories.
  • Harness chips — All harnesses, or one per source — appear when more than one source reported.
  • Filters for model, provider, effort, client, or person appear as removable chips when you arrive from a link on another page, such as a model or person.
  • Sort with By time (the default, newest activity first) or By cost (By tokens in the Tokens view), or select the Active, Turns, Tokens, or Cost column header.
The table shows 20 sessions a page, and its count covers every session that matches.

​
Columns

Rows blink when new activity arrives, and the header counts the sessions working now. Select the chevron at the start of a row to expand it in place; several rows can be open at once. The detail shows the session’s recap, its timing (duration, started, last active), git activity (commits, pushes, pull requests opened and merged, branches, repositories), its work (tool calls, model calls, subagent runs, share of cached tokens, files touched, effort, who billed it, client version), and a chart of its tokens over time by model.

​
Session detail

Open a session to see its full record. The header shows the session’s title, when the agent named it, and its latest recap. Copy session ID copies the id used in commit trailers.

​
Summary

  • Session cost — a breakdown of the session’s cost by how it was funded: Subscription, Prepaid credits, Metered, or Funding unknown. An Estimated or Partly estimated badge means Terma priced, at list price, tokens the source did not price itself. In the Tokens view this becomes Session tokens.
  • Who ran it, with which agent and client version, and chips for its model, provider, effort, and who billed it.
  • Its activity span, turns, and tokens (with the share read from cache), and counts of files, commits, pull requests, models, and subagents.

​
Token timeline

The token timeline charts the session’s token usage over time by type — cache read, input, cache write, output — with markers where subagents were spawned and where git actions happened.
  • Click a point to peek at what happened there, and step to the previous or next event.
  • Drag to select a range; the replay below narrows to it.
A long session scrolls sideways, about 90 minutes to a screen, with an overview strip below the chart that shows the whole session and pans it. Subagents run inside their session. When a session has subagent runs, each run is tinted in the chart and the transcript, and an Agent execution panel below the token timeline shows the main thread and each run as lanes on one clock. It starts collapsed: select Show runs to open it, switch between Timeline and Token usage, and drag to zoom.

​
Session replay

The replay shows the session’s events in order. Filter it to All, Conversation, Tools, or Errors, search messages, tools, and files, and Expand tools or Collapse tools. Navigation buttons jump to the start or end of the session and between your prompts, and Expand reader widens the transcript. Compactions — where the agent summarized earlier context to make room — appear as a short note in the transcript. Content appears only if the agent was configured to export it; see Privacy and security.