Gemini 4 Pro Disguised as a Flash Model: The Arena Leak, the Benchmark Numbers, and What Actually Holds Up
A model appeared in the Arena pool under the label Gemini 3.8 Flash and behaved like a far larger system: ten minutes of silent thinking, surgical SVG output, circulating benchmark leads over Astra and Fable 5.1. What the numbers say, why the RSI claim stays unconfirmed, and what agent operators can take away.

Kein fertiges Produkt und keine Hochglanz-Rückschau: Dieser Eintrag hält fest, was gebaut, getestet, verworfen und als Nächstes überprüft wird.
The biggest model story of the week did not come from a keynote. It surfaced in the least glamorous corner of the industry: a blind-test leaderboard, under a name that was already taken. Over the weekend, a model appeared in the Arena pool with the label Gemini 3.8 Flash, and it broke that label in every observable way. Instead of answering a request in seconds with an approximation, it sat silent for roughly ten minutes and then returned thousands of lines of precise code. Within days, that single observation grew into one of the messiest debates of the month: leaked benchmark charts, reverse-engineered backend specs, a context window that exists on no public model, prices that would undercut the competition, and the question that has shadowed Google all year, namely what is actually driving the improvement. This post separates what holds up from what remains rumor, works through the numbers on the table, and marks the limits of every claim along the way.
How the camouflage fell apart
Blind testing on the Arena goes back to a UC Berkeley team in 2023: two anonymous models answer, users vote, labs collect clean data without a brand halo. Anonymous models are routine there. In mid-August, for example, an anonymous candidate called Ox Alpha reached the top three of the leaderboard within 48 hours, and nobody has claimed it to this day. What made this case unusual was therefore not anonymity but disguise: the pool did not show a new name, it reused the name of a model Google had shipped publicly on September 2, live, priced and documented. Behavior that no flash-tier model would ever show under that label is not stealth testing anymore, it is a costume. The trigger was a concrete request: one user asked for a vector render of the PlayStation 5 in raw SVG. The labeled model streamed nothing, produced no partial output, stayed quiet for about ten minutes, and then delivered thousands of lines capturing every curve, every shadow and even the accents of the optical drive. The real Gemini 3.8 Flash answers the same prompt in 10 to 15 seconds, with approximate geometry that gestures at a console rather than showing it.
More evidence followed in series. Users posted voxel pagodas and a BMW M4 render, each side by side with older Gemini checkpoints: in lighting, depth, shading and geometric alignment the difference was categorical, not incremental. The classic pelican riding a bicycle prompt, the industry's unofficial spatial reasoning exam, passed in a single run under a starry sky, with no clipping and no misaligned shapes. A second variant demanded color grading, a day-to-night switch, working headlights, anatomical annotations on the bird and cadence control on the pedaling, again in one pass. The developer Pankaj Kumar, who spent real time with the model, summarizes it like this: it is fast where it counts, the jump in SVG and 3D generation is visible, and it parses complicated multi-part instructions from a single prompt instead of dragging the user through four correction rounds. That pattern, high quality after a long silence, is the signature of test-time compute: the model plans, writes, executes, debugs and polishes internally before a single token reaches the user. The ten-minute wait is accordingly not a bug and not an overload warning, but the visible side of compute spent before the answer arrives.
The circulating charts, compiled and framed by the finance portal Biggo, list four leads. On DeepSWE v1.1, the agent coding benchmark, the model scores around 88 percent, nearly two percentage points ahead of OpenAI Astra. On GDPval-AA v2, which measures real-world knowledge work, it is the only model with an Elo rating of 2064. On Terminal-bench 2.1 it reaches 95.3 percent, first place. On the OSWorld-2.0 computer-use benchmark it scores 86.8 percent, above Astra and above Anthropic's Fable 5.1. Four benchmarks, four leads, plus the claim that the same model showed strong pre-training results while post-training work continues. The frame matters more than the charts: Google has officially confirmed none of these numbers. They circulate as screenshots and collections rather than linked test runs, and the reading that this is an early Gemini 4 Pro checkpoint under an old name comes from developers who tested it hands-on, not from the company.
Pricing and the unconfirmed trap
The money side repeats the same pattern: concrete numbers, provisional status. The circulating figures name 2.25 dollars per million input tokens and 11.25 dollars per million output tokens, well below what comparable flagships charge. A researcher with backend access additionally reports a 10 million token input limit, a 256,000 token output limit, permanent memory across conversations and direct internet access without an API detour. Any one of these properties would be a real event, and none is confirmed so far. That is exactly the trap in this story: the more concrete the numbers sound, the faster they slide into comparison tables and purchase decisions, even though their source is an anonymous Arena label and leaked charts. Whoever cites them today cites a rumor with decimal places. The assessment that the model would be competitive in coding, agent work and computer use, and cheaper than both competitors, is a conditional calculation, not a product announcement.
The RSI question: evidence or marketing
The hottest part of the debate concerns not the model but the method behind it. Jasjeet Sekhon, Chief Strategy Officer at Google DeepMind, said at an event in Berkeley that recursive self-improvement had become a critical component of the logic behind massive AI investments. On September 9, the leak account Lyra posted the sentence huge congRatulationS Indeed, whose capital letters spell exactly the sequence RSI, addressed to Google DeepMind. From these fragments, parts of the community built the claim that Google had achieved RSI and therefore finished Gemini 4 ahead of schedule. The sober check does not support the strong version: an analysis by the Vandata team finds no named source, no benchmark list and not a single published number behind the boldest claims. Google itself has never confirmed RSI as achieved. The official picture is more modest: the company describes long-running agentic loops for Gemini 3.8 Flash that recursively evaluate and refine the underlying models, and a DeepMind researcher called the release one giant leap for RSI. The distance between recursive evaluation inside a training loop and recursive self-improvement in the full sense is exactly the distance that tends to vanish in viral coverage.
What operators of their own setups can take away
Despite the caveats, three practical points remain. First, blind tests on Arena are still the earliest reliable signal, because they remove brand halo and marketing, even though labels, as this case shows, can be deliberately wrong. Second, if even half of the reported specifications hold, the cost calculation for long agent runs shifts again: a 10 million token input limit and permanent cross-conversation memory are precisely the properties that stabilize multi-step jobs over dozens of iterations. Third, the real decision happens at the official release, and no amount of leak optimism moves that date. Until then the old distinction applies: observations from real operation are evidence, screenshots of benchmarks are promises. The distance between the two pays off the moment a model change in your own stack is due and the question is whether to rebuild today or wait.
Frequently asked questions
What happened on the Arena?
A model with the label Gemini 3.8 Flash, which Google shipped publicly on September 2, behaved nothing like a speed model: on a PS5 SVG render it stayed silent for roughly ten minutes and then answered with thousands of lines of precise code, while the real 3.8 Flash solves the same task in 10 to 15 seconds with approximate geometry.
Which benchmark numbers are circulating?
DeepSWE v1.1 around 88 percent, nearly two points ahead of Astra. GDPval-AA v2 Elo 2064, the only model at that level. Terminal-bench 2.1 at 95.3 percent, first place. OSWorld-2.0 at 86.8 percent, ahead of Astra and Fable 5.1. Google has confirmed none of these figures.
What is the reported price?
Circulating: 2.25 dollars per million input tokens and 11.25 dollars per million output tokens, which would undercut the competing flagships. Unconfirmed.
Which specifications are reported?
A 10 million token input limit, a 256,000 token output limit, permanent memory across conversations and direct internet access without an API. All of it comes from a researcher's backend report, not from Google.
Did Google achieve recursive self-improvement?
Not confirmed. Officially, Google describes agentic loops for Gemini 3.8 Flash that recursively evaluate and refine the underlying models. The RSI claim rests on a leak-account artifact from September 9 and a Sekhon assessment, not on official evidence. The Vandata team finds no named source and no published number behind it.
What does this mean for agent operators?
Arena blind tests remain the earliest signal, even when labels are wrong. Do not build infrastructure on unconfirmed specifications, wait for the official release, and adjust your own cost math only once the numbers are confirmed.
Sources
Vandata Team: Gemini 4 Pro leaks, what is verified and what is hype, retrieved September 19, 2026 ↗
Own editorial judgment from daily agent operation, as of September 19, 2026
Nachgebaut oder getestet?
Teile deine Erfahrung mit genau diesem Build-Log. Reviews werden vor der Veröffentlichung moderiert.
Noch keine Reviews für diesen Eintrag.
Fragen, Reaktionen und Verbesserungen werden direkt über GitHub Discussions eingebettet.
GitHub-Bereich öffnen ↗