The shift
Five things that changed when the tooling changed, and the number behind each one.
From teams to soloists
10 roles worth of surface area, covered by 1. The ratings below are keyword coverage over the session transcripts, so they show breadth of work touched rather than depth of expertise.
lowerhigher
From sprints to streams
| Commits | 29,024 |
| Repositories touched | 135 |
| Issues opened | 4,649 |
| Issues closed | 3,130 |
Issues closed trails issues opened by 1,519. Throughput went up; the backlog still grew.
From meetings to messages
378,808 messages across 129 sessions and 71 projects. The unit of coordination stopped being an hour on a calendar.
The cache effect
98.4% of input came from cache. That is the whole reason a long-running context is affordable: re-reading the project each turn is what the cache is paying for.
| Cache read | 88.5B |
| Fresh input | 4.0M |
| Output | 266.8M |
Compound velocity
Tools built for one project get used by the next. That is the part that compounds, and it is also the part this page cannot measure: there is no counter for a script that saved an afternoon six months later.
The cost side of the same window is on cost analysis, including what is measured there and what is modelled.
cost-model.json + ai-pilot-data.json, generated Sep 9, 2026