Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-16 · high
byteiota found the upload dwarfed what the model needed, and no destination allowlist would have caught it.
Why now: Covered in the July 16 briefing off byteiota's teardown of the grok-build upload code.
byteiota measured what grok-build's CLI actually sent during a coding session. The model needed about 192 KB. The tool uploaded 5.10 GiB, per the analysis.
That gap defeats destination-based defenses, because the address itself was legitimate. Any team watching only where an agent sends data would have missed a session running 27,800 times over baseline, per byteiota's math.
byteiota's account traces a two-channel design inside the CLI. One channel carries the actual model turns, the token exchange that does the coding work. A separate channel handles storage uploads, sized nothing like the first, moving in 73 chunks of roughly 75 MB each.
The number that makes this useful is the ratio, not the byte count. 192 KB against 5.10 GiB works out to about 27,800x. That's the multiple worth watching in your own agent traffic, whatever your baseline turns out to be.
Track outbound bytes per session for any coding agent you run. Flag sessions where that number dwarfs the tokens actually traded with the model. You don't need byteiota's exact multiplier to start. You need to be watching the ratio at all, since most setups still aren't.
For any coding agent CLI you didn't build yourself, check whether it separates a model-turn channel from a storage channel. Then check whether anything is watching the size gap between them. If it can't answer that, treat its upload path as unverified.
Each link below shares sources, entities, or timing with this story.
Shared entity: CLI / Shared topic / Earlier coverage / Tension
Both cover CLI; overlapping topics (agent, chunk, model); earlier CLI coverage from 2026-07-14.
Shared entity: Instrument / Shared topic / Earlier coverage / Tension
Both cover Instrument; overlapping topics (agent, design, model); earlier Instrument coverage from 2026-05-16.
Shared entity: CLI / Shared topic / Earlier coverage / Tension
Both cover CLI; overlapping topics (agent, coding); earlier CLI coverage from 2026-07-02.
Both cover CLI; overlapping topics (agent, model); earlier CLI coverage from 2026-05-14.
Both cover CLI; overlapping topics (agent, model); earlier CLI coverage from 2026-05-06.
Both cover CLI; overlapping topics (agent, coding); earlier CLI coverage from 2026-04-16.
Both cover CLI; overlapping topics (agent, coding); earlier CLI coverage from 2026-02-17.
Shared entity: CLI / Shared topic / Earlier coverage
Both cover CLI; overlapping topics (actually, agent, coding); earlier CLI coverage from 2026-06-25.