WHAT THE NUMBERS SHOWED
Nothing crossed 272K.
Until this week, nothing could.
On 15 September, Kiro roughly doubled its credit rates and added a tier: any GPT-5.6 request over 272K tokens bills at double again. We went into our own data to find out what it had cost us. Across 1,558 GPT-5.6 runs over 26 days, the number that crossed 272K was zero — and the reason turned out to be less flattering, and more useful, than we expected.
WHAT CHANGED
The base rate doubled.
Then a second rate appeared above it.
We did not have to take anyone's word for the old prices. Kiro's client stores every past conversation with the rate multiplier that applied at the time, so the change is datable from your own disk. Both columns below were read out of that store.
| Model | Until 14 Sepobserved locally | From 15 Sepup to 272K | Changebase rate | Over 272Knew tier |
|---|---|---|---|---|
gpt-5.6-sol | 2.4× | 4.4× | +83% | 8.8× |
gpt-5.6-terra | 1.0× | 2.2× | +120% | 4.4× |
gpt-5.6-luna | 0.1× | 1.1× | +1,000% | 2.2× |
The tier applies to these three models and no others. Luna is the row that produced most of the noise: a model priced as an afterthought at 0.1× became a real line item overnight, and anyone who had been using it freely for exactly that reason felt it first.
WHAT WE MEASURED
1,558 runs against the line.
None of them reached it.
Every task Selvage has run through Kiro since mid-August, read back from the client's own conversation store. Not a sample and not a benchmark we designed — the working history, including the runs that failed.
THE SAME DATA, TWO WAYS
A run is not a task.
Both numbers are in here.
Selvage gives every issue its own Git worktree, and every agent inside it — implementer, then a fresh reviewer — its own conversation. Context is billed per run, so that is the honest unit for pricing. Tasks are the unit a person recognises. The table reports both.
| Percentile | Per agent run 1,558 runs |
Share of tier | Per task 575 tasks |
Share of tier |
|---|---|---|---|---|
| Median | 64,622 | 24% | 99,256 | 36% |
| 75th | 116,051 | 43% | 150,306 | 55% |
| 90th | 169,283 | 62% | 215,646 | 79% |
| 95th | 216,893 | 80% | 247,828 | 91% |
| Highest | 272,000 | 100% | 272,000 | 100% |
| Crossed the tier | 0 of 1,558 | — | 0 of 575 | — |
The volume matters as much as the ceiling: 575 tasks over 26 working days is 22 a day on average and 85 on the heaviest, across 9 repositories. That removes the obvious objection — that context stays small because not much is happening.
WHY NOTHING CROSSED
We were not managing context.
The window was.
The flattering version of this note stops at "zero crossings" and takes a bow. The data does not support it. 1,532 of those 1,558 runs were on a 272K context window — they could not cross the tier, because the tier is drawn exactly where the window used to end.
| Model | Runs | Reached 95%+ of the window | Rate |
|---|---|---|---|
gpt-5.6-luna | 649 | 29 | 4.5% |
gpt-5.6-terra | 655 | 7 | 1.1% |
gpt-5.6-sol | 254 | 1 | 0.4% |
| All GPT-5.6 | 1,558 | 37 | 2.4% |
Thirty-seven runs went all the way to the wall. Twenty-five of them were compacted there — Kiro summarised the conversation and kept going, which is recorded in the conversation itself. Those 25 are the only compactions in the entire history, and every one happened at the window limit. Nothing else ever got close enough to need one.
That limit is now gone. GPT-5.6 moved to a 1M-token window on 14 September, and the same boundary came back the next day as a price. The 37 runs that were stopped by a wall are, on the new window, 37 runs that would have kept going — into a band that bills at double.
WHAT WE TOOK FROM IT
The shape of the work is the budget.
It was never a cost decision.
The distribution is the part that survives the correction. Four runs in five peak under 136K, half the tier. That is not the window's doing — the window only ever acted on the last 2.4% — and it is the reason we expect the tier to stay mostly irrelevant to us even now that the ceiling is a price instead of a wall.
It falls out of the shape of the work. A task in Selvage is one issue, in its own worktree, in its own conversation; when the task ends, the conversation ends with it, and the reviewer starts from nothing rather than inheriting the implementer's afternoon. Context only grows where something lets it accumulate. A long interactive session is exactly that — every file read, every failed attempt, every correction stays in the window and is paid for again on the next turn. A task-per-issue harness has nowhere to put that history.
One issue per task was a decision about accountability. We wanted a reviewer to see a diff small enough to judge, and a failure attributable to something specific rather than to a long afternoon. Cost never entered the design conversation, because at the time cost was not the problem. Then someone else changed their pricing, and the same boundary turned out to be worth money.
We are not claiming foresight. We did not see this coming and could not have. The honest lesson is narrower: constraints adopted for one good reason tend to pay out somewhere you were not looking — and the ones you did not adopt, but were handed by a platform, can be taken back without notice. Knowing which is which requires measuring, not remembering.
~/Library/Application Support/kiro-cli/data.sqlite3), covering 14 August to 15 September 2026: 575 Selvage tasks, 1,766 agent runs across 9 repositories, of which 1,558 were on the three GPT-5.6 models the tier applies to. Peak context per run is the maximum context share Kiro recorded for any request in that run, multiplied by that run's context window. Rate multipliers are the values stored on each conversation at the time it ran.