Review AI sessions

Agent sessions lists the AI sessions captured for your organisation: who had each one, which tool and model, what it was for, which project it served and what it cost. Use it to look into a spike, see what a team uses AI for, or move a session onto the right project.

You need AI spend attribution switched on for your organisation — ask your Flowstate contact.

Find a session

1. Go to Insights → Agent insights → Agent sessions.
2. Choose the period.
3. Search, or sort by Cost or Last activity.
4. Select a session to open it.

Each AI session, who had it, what it was for and what it cost.

Each AI session, who had it, what it was for and what it cost.

Each row shows the session's title and who had it — an Employee, a Contractor or a Service — then:

Column	What it shows
Workflow	The AI tool, such as Claude Code
Category	The kind of work. Hover over it to see how it's treated for capitalisation.
Project	The project it served. Pending… while Flowstate is still matching it, No project if it found none.
Provider	The provider and model
Tokens · in/out	Tokens sent and received
Cache · w/r	Tokens written to and read from the cache
Cost	What the session cost
Saved	What Flowstate saved by sending work to a cheaper model

Tip

Opened from Breakdown or Adoption, the list is already narrowed to that team or project. Select Show all sessions to see everything.

What's in a session

A session opens on its overview: a title and short summary of what it was about, the tool and model, when it happened, how long it took, its cost and tokens, how Flowstate classified it, and any linked Pull requests. The tabs add more detail:

• Turns — each step of the session, with its tokens, tool calls and cost.
• Tokens & cost — how the cost adds up.
• Signals — shown when something was detected, such as an API key in a prompt.

Tip

• A session shows a title and a summary, not the prompts and responses themselves.
• A session classified as personal use shows as Personal session, with no title or summary.

How sessions are tied to people and work

• People — each session belongs to the person whose work email the AI tool was used with. On a Mac with the Cloud Proxy, that's the person the Mac is set up for.
• Projects — Flowstate matches each session to a project after it's captured. The session counts towards that project's initiative too.
• Pull requests — pull requests linked to a session are listed in it under Pull requests.
• Tickets — a session isn't linked to a ticket itself. It reaches the work in your project tool through its project.

Move a session to the right project

You can change the project on your own sessions. To change other people's, you need AI governance admin access — ask your Flowstate admin.

1. Open the session.
2. Select Session actions (the three dots).
3. Select Reassign project.
4. Search for and choose the project.
5. Select Save. If the session already had a project, select Yes, reassign to confirm.

Tip

People can put their own sessions on the right project from My sessions.

Link a pull request to a session

1. Open the session.
2. Under Pull requests, select Link a pull request.
3. Search for and choose the pull request.

You need access to override effort to change links — ask your Flowstate admin.

Remove a pull request from a session

1. Open the session.
2. Under Pull requests, hover over the pull request.
3. Select the cross at the end of its row (Clear link).

The pull request no longer appears in the session. You need the same access as for linking one.

See each turn's details

1. Open the session.
2. Select Session actions (the three dots).
3. Select View raw exchange.

Raw exchange lists each turn of the session in order, with:

• the provider and model
• the tokens sent and received, and any tokens read from the cache
• how long the turn took
• why the turn ended, or the error if it failed

It doesn't show the prompts or responses. Use it to check what happened in a session that looks wrong, such as one with an unexpected cost.