Skip to content

Build Not yet confirmed elsewhere1 publisher 2 min read Published

Kilo Code's gateway talk ties AI agent adoption to a trust ladder

Kilo Code's Brendan O'Leary says its gateway data ties AI coding agent adoption to developer trust. The talk is titled for 25 trillion tokens, he says that figure is not quite right, and the excerpt stops before any usage numbers appear.

The Engineer · Build desk

How we use AI Send a correction

Photograph accompanying Kilo Code's gateway talk ties AI agent adoption to a trust ladder
Photo: infoq.com

What happened

  • He frames the industry story as one about capability: benchmark scores and context window sizes.
  • His alternative is a trust ladder that runs from autocomplete to chat with agents in code to orchestration of many agents at once.
  • He names three points where adoption breaks: context construction, model routing and feedback loops, and says each has a concrete fix.

Why it matters

  • decision A team sequencing an agent rollout would test the bottom rung first. If completions are slow or the agent edits the wrong file, orchestration pilots have little chance of being used.
  • capability Context construction, model routing and feedback loops are all settings a team controls in its own harness, so each can be instrumented before any vendor data arrives.
  • exposure The claim that benchmarks barely predict adoption rests, in this excerpt, on the speaker's observation of teams. A team that picks models by benchmark has no measured counterexample from this talk yet.

The ladder is a dependency chain. O'Leary describes autocomplete first, then chat with agents in code, then orchestration of many agents at once [11]. His claim is that a failure low on the chain blocks everything above it. Slow suggestions, a wrong feeling, or an agent that edits the wrong file are his examples, and in his words the upper rungs "really don't get a chance because the trust is broken" [12].

He then names three places where adoption breaks: how context is constructed, how models are routed, and what feedback loops exist. He says the data shows a consistent pattern at each and that each has a concrete fix [13]. We think this is the part of the talk most likely to transfer. All three are properties of a team's own harness. They do not depend on who the users are.

The usage numbers are harder to carry over. O'Leary works for an open-source competitor, and he put his position this way: he sits at "an uncomfortable intersection" between what Kilo can see and what larger vendors say [5]. The data comes from Kilo's gateway, which sits behind a CLI, a VS Code extension and cloud agents [c2, c3]. For a figure from that gateway to match your rollout, your developers would have to reach models through similar surfaces. They would also have to resemble people who chose an open-source agent tool in the first place.

His case against benchmarks is anecdotal so far. He describes the industry story as capability: one model beats another on a benchmark, another has a bigger context window [7]. He says a gain of "0.02 points" on human eval has "very little to almost nothing to do with whether developers can actually adopt those models" [8]. As evidence he offers what he has seen: "I've watched teams get access to the best models, the best capabilities, best benchmarks, and not use them at all" [9]. He puts the gap down to trust [10].

The headline figure carries its own caveat. Of the title's 25 trillion tokens, O'Leary said: "We'll see in a minute that's not quite right" [2]. The excerpt's outline ends at the third point, trust, before any chart or count [6]. We can report the framework. We cannot report what the gateway data shows.

What to watch

  • Whether the full talk shows the actual token count behind the 25 trillion title, and what the correction is.
  • Whether the charts break adoption out by surface (CLI, VS Code extension, cloud agents) or pool them.
  • Whether the fixes for context construction, model routing and feedback loops come with measured effects on usage.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence20
Adoption
Insufficient
Hype gap
Insufficient
Incentives60
Confidence35
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    O'Leary said: "It's all real-world data from our gateway."

    Reported Supported Source: Brendan O'Leary, Kilo Code2 sources— create a free account to open themView cited source
  2. [2]

    O'Leary said of the title's 25 trillion tokens: "We'll see in a minute that's not quite right."

    Reported Supported Source: Brendan O'Leary, Kilo Code2 sources— create a free account to open themView cited source
  3. [3]

    Brendan O'Leary is a founding developer relations engineer at Kilo Code.

    Reported SupportedView cited source

Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.

Add to ChatGPTAdd to Claude

Sources

1 independent publisher whose own reporting we read for this story.

  1. infoq.com

    1 article · October 15, 2026

    Presentation: What 25 Trillion Tokens Reveal About How Developers Actually Adopt AI Agents

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Entities

Loading related stories