Where tokens went
See what a run's tokens were spent on (setup, files, handoffs, the plan window) and what to change to use less.
Where tokens went explains a run's usage as causes you can act on. It shows how much of every agent's start was setup it did not need, which files agents printed into their own context, how many agents worked at once, and how much of your plan window the run used against its budget.
It is made by MAIS, an open-source reader of Claude Code and Codex session files, on the computer that ran the team. Only the report leaves that computer.
Open it
- While a team runsOn the Run board, open More → Where tokens went. The report is refreshed every minute while the run goes, and once more after it ends.
- For an earlier runOpen More → History, choose the run, then Where tokens went. Agents goes back to the run's agents.
What it shows
| Section | What it tells you |
|---|---|
| What stands out | A few plain sentences, such as "Your own CLI setup was 41% of the starting context". Each rests on a section below. |
| Plan window | Your Claude or Codex window before the run, at its highest, and the points the run added, with the budget's wrap-up and stop marked. |
| Over time | Tokens every few seconds and how many agents were making model calls, with the moments many agents started together. |
| By cause | Every token of the run: the starting context each agent re-read on every call, what agents added as they worked (files printed, tool results, messages), and what they wrote. |
| By agent | Each agent's calls, tokens, starting and final context, and how long it spent in model calls and waiting. A name links to the agent's page. |
| Costliest in context | The command outputs and files whose re-reading cost the most, files several agents each read for themselves, the part of every agent's start that was identical, and tools agents were given but never called. |
| Time | How long model calls took, and how agents' time divided between model calls, tools and waiting for work. |
Every agent re-reads its whole context on every model call, so something added early costs again on each later call. The report counts that: an item's re-read is its size times the calls that re-sent it.
How sure each number is
A CLI reports what each model call read in total, not what was in it. The report labels every figure:
- Measured: the CLI reported it (tokens per call, the plan window, its own cost).
- Derived: arithmetic on measured figures, such as a call's rise in context split among what was added just before it.
- Estimated: a split by share of characters, such as the first call's context divided among its setup, tool definitions and job.
- Unknown: the files do not say. It is shown as unknown, never as zero.
Use less next time
| If the report says | Try |
|---|---|
| Your own CLI setup is a large share of the start | Leave Claude Code setup for agents off (team Advanced). It is off unless you turned it on. |
| Files printed are the largest cause of growth | Ask agents in their job to read only the parts of files they need, or give one agent the reading and have it hand out summaries. |
| Many agents started together | Set Most agents working at once in the run budget. |
| Several agents read the same file | Put the shared facts in the team's context once, or have one agent read it and hand it over. |
| The run used much of your plan window | Set a run budget so the run wraps up and stops where you choose. |
Privacy
MAIS reads the session files on the computer that ran the team. The report carries sizes, causes, the command lines agents ran and the names of the files they read or changed. It does not carry the files' contents or the agents' messages. Passwords, tokens and keys that appear in command lines are masked, and a patch is named by its files, never its text; masking catches common forms only, so a command that printed a secret in an unusual form can still show it in the Costliest in context table. On a computer you connected, turn reports off with sculptured connect --disable usage-reports.
A computer whose runner was installed before reports existed says so; reinstall the runner from Computers to see them.