Browse sessions and workflows
Find sessions on the Sessions page and read a session's cost, activity, subagents, and the artifacts it worked on.
A session is one conversation with an AI tool, such as a Claude Code, Codex, or Cursor session. The Sessions page lists them so you can see who used which model, for what, and what it cost.
Who can see this: Everyone. What you see depends on your role:
| Role | Sessions shown |
|---|---|
| Admin | Everyone's, with Top Cost, team, and user filters |
| Everyone else | Your own |
The tabs
- Top Cost shows the 50 most expensive sessions in the range you pick: Last 7 days, Last 30 days, Last 90 days, or Month to date. Admins only. It's the first tab Admins see.
- Recent shows up to 50 sessions from the last 7 days that are no longer active. It's the first tab everyone else sees.
- Active shows sessions with activity in the last 15 minutes.
- Scheduled lists scheduled and recurring tasks, with their runs and cost per run. Admins only. See See scheduled tasks.
- Bots lists your Cursor Grok Bots, with their routines and spend. Admins only. See See Cursor Grok Bots.
Admins can narrow Recent and Active with the All teams and All users filters in the top right.
Each row reads like a sentence: the person, the model they used, and the session title, followed by how long ago the session was last active, its tokens, and its cost. Hover the time to see the full date and time. A session run by a service account, such as a Cursor cloud agent running under a team service account, shows the account's name with a Service account badge in place of a person. A session started with a slash command shows the command as its title, such as /review, followed by any arguments. When the prompt was withheld and the session has no other title, the row leaves the title out and reads like "Brian used Claude Opus 4.6". A Cursor session with no title is named by what it is: "Cursor cloud agent", "Grok Bot sub-agent run", or "Cursor session (prompt not captured)". On Top Cost and Recent, small icons after the title show which tools the session worked in, such as Figma, Linear, Notion, Google Drive, Slack, Salesforce, Claude, or GitHub. Hover an icon to see the tool's name. The icons follow the same rules as the Artifacts panel: files the session edited get no icon, and a tool the session only viewed isn't shown, except Figma. A Worktree badge means the session ran in a git worktree. A badge like +2 parallel means the person had that many other sessions active at the same time as this one. Hover the badge to see the count spelled out. Click the person's name to open their profile, or anywhere else on the row to open the session.
Most costs are Tokenize's estimate or come from a connected bill. See How cost is calculated. Two cases read differently:
- A Codex session Tokenize knows only from OpenAI's Compliance Logs shows what OpenAI billed for it. Hover the cost to see "What OpenAI billed for this session's turns." When OpenAI didn't report a cost for every turn, the row shows "—".
- A service account's session shows "—" when Cursor billed the account without naming the session. The money is still in your totals.
Session details
The main part of a session page shows:
- Suggestions for that session, when Tokenize has any. When a Claude session's context cost sat mostly in its subagents, the suggestion says so, names the costliest subagent, and lists the costliest subagents under it. Click Show subagents to open the Subagents tab. "More subagents ran than are listed here." means the list is cut short.
- Cost By Model, the share of the session's cost by model. A Cursor session with no cost on any model shows Messages by model instead.
- Turns, for Codex sessions. Each turn is a prompt and the model calls after it, with the number of calls and an estimated cost. Open a turn to see its calls, each with Time, Model, In / out, Cache read, and Cost. Calls a sub-agent made carry a Sub-agent badge. A turn that covers several prompts shows a badge such as 2 prompts. Where OpenAI's Compliance Logs have the turn, the amount OpenAI billed is shown too, and a turn Tokenize knows only from those logs carries a Billed by OpenAI badge.
- Skills Used, with Activations, Requests, and Cost for each skill.
- Artifacts, what the session worked on, when reported. See What the Artifacts panel lists.
The panel on the right has these tabs:
- Overview lists facts about the session: User, Duration, Provider, Usage cost, Requests, Avg context, Cache read, and In / out tokens. On a service account's session, User shows the account's name with a Service account badge, and Usage cost reads "Billed to the account" with "Cursor didn't name this session on the bill." when the bill doesn't name the session. On a Codex session known only from OpenAI's Compliance Logs, Usage cost reads like "$4.20 billed by OpenAI", or "—" when OpenAI didn't report a cost for every turn. Claude Code sessions add Branch and Working directory. Codex sessions add Reasoning effort, Reasoning tokens, and, when relevant, Rate-limit peak. Cursor sessions show Mode, Diff, accepted and rejected edits, Acceptance rate, Context, Branch, and Prompts instead.
- Activity is a timeline of prompts, responses, tool calls, and events such as "Tool failure" or "Permission denied". Sort it with Newest first or Oldest first. Shown for Claude Code, Claude Cowork, Claude desktop, Codex, and Cursor sessions. A session Tokenize knows only from a Compliance API key, such as a claude.ai chat, opens on the same page, and its Activity shows the prompts and replies. See Connect Anthropic and Connect OpenAI.
- Subagents lists subagents the session started, costliest first, each with its requests and average context. Shown for Claude and Codex sessions that used them. A Codex sub-agent doesn't get its own row on the Sessions page: its usage and cost count toward the session that started it, and a link to the sub-agent opens that session. "Showing the N costliest subagents. This session has more." means the session started more than the tab lists.
- Related tasks shows how a Codex session connects to other Codex tasks. Shown when Tokenize captured those links.
How personal details appear in session text depends on your organization's privacy settings. See Privacy and redaction.
What the Artifacts panel lists
The Artifacts panel groups what the session worked on by tool. Each card shows the item's title when Tokenize has it, a link when there is one, and a badge for what the session did: Created, Modified, or Commented. Except for source files, items the session only viewed aren't listed.
| Group | What's listed |
|---|---|
| Code | Source files, as a table of paths. |
| Linear and GitHub | Issues and pull requests, named by key, such as TOKEN-434: Migrate the purge job or owner/repo#123. |
| Figma | Figma files. |
| Notion and Google Drive | Pages, databases, and Drive files such as Docs, Sheets, and Slides. An item with no title says what it is, such as "Google Doc". |
| Slack | Messages, thread replies, drafts, and scheduled messages the session sent or changed. Channel messages and drafts link to Slack. Cards don't show message text or channel names. Direct messages are shown only as a count, such as "3 direct messages" or "1 direct message draft". |
| Salesforce | Records the session created, updated, or added a task, event, note, or comment to. Each card shows the object type, such as Account or Opportunity, and the record ID. Record names, field values, and links aren't shown. Records created in one session are counted by type, such as "3 Account records". |
| Claude | claude.ai artifacts (pages) the session published or edited, Claude Design canvases, and Claude Docs, linked when Tokenize has the link. An item with no title says what it is: "Claude artifact", "Design canvas", or "Claude Doc". |
Workflows
The kinds of work your team does with AI, grouped from sessions, live in Work Intelligence → Workflows. See Explore Work Intelligence.
Troubleshooting
"session not found" when you open a session link. The session doesn't exist, or it belongs to someone outside what your role can see.
"No active sessions" on the Active tab. Nothing has had activity in the last 15 minutes. If you expected a session to show, check that the desktop app is running. See Troubleshoot the desktop app.