Post

Matches what we see building Miru (semantic search for coding agents, disclosure: we make it) - most agent spend goes on finding the right context, not writing it. Planning and orientation are the real budget line, not code output.

Does that 198:1 include repository reads served from cache, or only tokens billed at the API? That changes how I'd interpret the gap.

Great question @dnulkjkjh.bsky.social! Cache reads are included. The 198:1 is context-window volume, which Decant counts as input plus cache reads plus cache writes on every call, divided by output. So 185M is everything resident in the window across the run (not solely fresh input).

That distinction helps. Counting the full resident window explains the ratio; separating fresh input from cache reads would also make the marginal cost of each call easier to see.