The multiple in circulation is a growth curve; the multiple in the data is a ratio. None of the material at hand carries a 14x figure for agent token growth since February [17]. It carries OpenRouter's per-request measurement, which tells you how much an agentic call consumes relative to a human one [2], and a crossover date, which tells you when agents became the majority consumer of tokens on the platform [1]. Those are different objects, and only the ratio explains a backlog.
It explains one because tokens arrive as diffs and diffs arrive at a person. At Augment, where agents write all the code [10], the engineer at the front of the queue had six pull requests ahead, each around 400 lines written by nobody on the team [11]. That is 2,400 lines of reading standing between a two-line change and its first human comment [13].
The Faros numbers, reported by Luca Rossi at Refactoring, put the same shape across 4,000-plus teams and 22,000-plus developers [4]. Divide the increase in PRs touched per day by the decline in weekly deployments and you get roughly 90 percent more work in flight per unit actually shipped [14], which is the mechanical reason lead time landed at plus 480 percent with an extra 80 percent of waiting inserted between every pipeline step [7].
Nothing in the price signal argues for slowing the generator. DeepSeek V4 Flash output costs $0.18 per million tokens against GPT-5.5's $30 [3], about 167 times cheaper [15], and OpenRouter's segmentation shows agentic traffic moving onto V4 Flash within a month of release while human usage stayed on V3.2 [18]. Generation gets cheaper on a release schedule. Reading does not.
Augment's response was to stop sending everything to a human: a risk classifier auto-approved 10 percent of PRs to start [12]. Against a 1,400-PR queue, that still leaves 1,260 for people [16].