GOOGLE'S SMARTER AI TAKES LONGER TO BE WRONG

Google released Gemini 4 Argon generally on October 13 as its most capable model for complex coding and agentic tasks. Within a day, real-codebase complaints began colliding with launch benchmarks. The argument is not whether a model can write code: it is whether a developer gets verified progress after the checking, waiting and rework.

On October 14, developer Theo Browne said Argon was unusable for coding in his own repositories because it confidently invented explanations of how existing systems worked. In almost every test he ran, he said more than half of the model's factual claims were wrong. That is one developer's reported test result, not an independently replicated population-wide error rate.

A different developer's October 15 r/GeminiAI post described four hours of Argon High coding work that allegedly introduced 115 regressions caught by deterministic tests, followed by another four hours repairing the damage. The author also reported Argon took roughly four times as long as Opus 5.5 High on the compared work. The full tasks, logs, test denominators and matched conditions are not public in the post; the numbers remain the reporter's claims.

The price of the experiment became another source of anger. An October 14 student Pro user reported hitting an hourly Argon allowance after roughly ten messages; an October 16 coding comparison claimed dramatically less Argon capacity on Pro than with Opus 5.5 or Astra on other subscriptions. Those are user observations, not controlled billing measurements. The latter tester explicitly updated the post on October 17 to report that Google had doubled Argon's Pro weekly allowance after a reset.

The opposite evidence is real, too. Google's own October 13 write-up describes an 11-hour unattended run on an approximately 205,000-line Python repository, with 16,892 tests and six proposed performance optimizations. Reviewers accepted two of them; Google reports around 40% faster in-memory session preparation in long sessions and 21% faster cold imports. Four rejected suggestions are not four fabricated claims, and this successful, supervised exercise is not a controlled rebuttal of Theo's different tasks.

The missing comparison is net engineering work, not generated tokens or a leaderboard score: how often did the agent describe existing code correctly, how many changes survived tests and review, and how much human time did the full task consume? The public reports establish a significant developer backlash and conflicting experiences; they do not yet establish Argon's average coding quality versus Flash 3.8, Astra or Opus under matched conditions.