Why is Gemini 4 Carbon taking so long? · Kernel · kernel.dev, November 2026
Kernel finds Gemini 4 Carbon spends half its steps on work nobody asked for
On one of its private evals, Kernel gives an agent a codebase from just before a bug was fixed and a report that describes the bug only by its symptoms. Carbon took close to an hour on tasks that Opus 5.5 and GPT-6 Astra finished in minutes. Slower inference explains part of the gap: 16 to 30% of Carbon's extra time against Astra, and 45 to 49% against Opus. The rest is longer trajectories. Against Astra, Carbon took about seven times as many steps and eleven times as many actions, and processed more than sixteen times as much input.
Kernel labelled each step. Of Carbon's 215 steps in the labelled runs, 117 were waste: 70 auditing code beyond the bug and 47 closing loopholes the ticket had already ruled out. Astra wasted one step of 19. Carbon also re-read code: 39% of the lines it read were lines it had already seen, against 7% for Astra. Running Carbon in opencode and mini-SWE-agent made no meaningful difference, and on low effort it often failed to produce a fix at all.
To test whether this was a knowledge gap or a habit, Kernel re-ran one trial with the harness injecting "do you already have enough to make the fix?" every five turns. That trial finished in 28 minutes instead of 37, and the wait between naming the cause and the first edit fell from about 25 minutes to about 10. The eval is private and the check-in result comes from a single sample trial. The post was at 200 points and 100 comments on Hacker News at 10:02 EST today.
Why it matters: On Kernel's numbers, most of Carbon's extra time against Astra is extra steps, so faster inference alone would close only part of the gap. A periodic "are you ready to edit?" prompt is a harness change you can test on your own tasks before you switch models.