Burn map

The Burn map shows every file your agents touched, sized by how much it was worked and colored by whether the work reached Git. It answers a question token totals cannot: how much agent effort is sitting in files that never landed. The burn map shows your current backlog rather than a period, so it has no period selector. Choose a Repository — or All repositories — at the top. Work that could not be tied to a repository appears under Unattributed.

​

Landed and unlanded work

Every file an agent touched is in one of four states. A bar shows the split, and a chip for each state filters the map to it: The summary line reads, for example, 214 files touched · 71% landed · $182 unlanded: how much of the spend on touched files has not reached Git yet. In the Tokens view, unlanded work is measured in output tokens.

​

Unlanded spend by age

The Unlanded spend by age strip (Unlanded output by age in the Tokens view) breaks unlanded work down by how long it has been since each file’s last edit, with the files and sessions in each tier:

• Active — edited in the last 24 hours
• Open — last edited 1 to 7 days ago
• Stale — last edited more than 7 days ago
• Abandoned — untouched for longer than that
• Discarded — edits that were thrown away

An At risk callout totals the files that are stale or abandoned and names how old the oldest is. The strip also says how much of the total is backed by Git evidence and how much rests on what the agent reported. Each turn’s cost is split equally across the files it touched, so a file’s spend is its share of the turns that worked on it.

​

Activity by file

The treemap shows one tile per directory. Choose what sizes the tiles with Size tiles by:

• Edits — how much the files were worked
• Unlanded — how much spend has not reached Git
• Sessions — how many sessions touched them

Color shows unlanded burn. A red hatch marks directories whose work was mostly discarded, and a dashed outline marks directories with files in an open pull request. Select a tile for its files. Below the treemap, a ranked list of files can be ordered by Unlanded, Edits, Sessions, or Oldest first, which puts the stalest unlanded work at the top. Files in an open pull request are tagged in PR.

​

A file’s page

Select a file to open its page:

• Edits, Sessions, Unlanded, and session tokens
• Its working state, and a timeline: first edited, last edited, staged, committed, pushed, discarded, or renamed
• Git activity that involved the file
• The Sessions that touched it, with source, spend, and last activity
• Same path elsewhere — the same path in other repositories

The file page refreshes itself every few seconds while you watch.

​

Using the map

• Active and Open work is usually a branch in progress.
• Stale and Abandoned tiers that keep growing are spend with no result yet. Open the files, find the sessions behind them, and decide whether to land or discard the work.
• A directory with a lot of Discarded work is where agents spent effort that was thrown away — often a sign the task or the code there is hard for them.