What Twitter says about Gemini 4 Argon
Hauke Hillebrandt, 18 October 2026. Research done with Claude, using Scry's Twitter archive.
We read what people on Twitter (X) said about Google's Gemini 4 Argon from September to 18 Oct 2026. The posts come from Scry's Twitter archive, pulled with free queries on 18 Oct at ~11:30 Coordinated Universal Time (UTC). We also looked for posts on mathematics, recursive self-improvement (RSI) and the model card.
What we read
- Cohort: 6,723 tweets since 1 Sep that mention both "gemini" and "argon", 3,441 of them original posts.
- Posts read: 603 unique posts. They include a seeded random sample of 200 original posts, the 120 most-liked and slices by keyword, date or account size.
- Side slices: posts with "Gemini 4" but not "argon", or "argon" but not "gemini", since many people wrote only one of the two.
- Checks: four AI analysts (Claude agents) coded the posts, and a checker agent tested each claim against the text. A script confirmed every quote and link against the saved tweets.
Findings
- Two spikes, both set by Google. Google announced Argon on 30 Sep for a set of trusted testers and released it worldwide on 13 Oct. The two-day launch windows hold ~2/3 of all cohort tweets. Posts by Google and its executives drew about a third of the likes on the 120 most-liked posts, led by Sundar Pichai's (~28k).
- Jokes led the first spike. The most-liked post not from Google is a Japanese joke (8,563 likes): Argon seems so self-critical that it was probably abused in training.
- More praise than complaint, mostly news. In the random sample, about a third of on-topic posts are positive and a sixth negative (63 and 32 of 198 in one coding). Most of the rest is news without a verdict.
- Benchmarks put it near the top. Epoch's Capabilities Index gives Argon 165, behind Opus 5.5 (167) and GPT-6 Astra (166). The Abstraction and Reasoning Corpus (ARC) Prize verified 97.5% on ARC-AGI-3 with the provider's adapter, but 49.8% with the standard setup.
- Testers are split. Ethan Mollick calls it "the first non-OpenAI/Anthropic model to pass the Fable/Mythos/Astra bar". Wes Bos rates it good but "not Opus5.5/Astra/Fable levels". Theo calls it "a huge jump for Gemini" but, a day later, "outright unusable for real code work". One tester's bug-fixing test scored Argon 33 at launch and 40.7 four days later, against 41.7 for Opus 5.5.
- Cheap per token, wordy per task. Partners list $2 per million input tokens and $10 per million output tokens. Several posts say this introductory price doubles in December. One-prompt demos cost a fraction of Opus 5.5's, like $0.19 against $12.06 for a ship in a bottle. That tester still preferred Opus's result. And in one tester's build, Argon used ~50% more tokens than Opus 5.5.
- Access and quotas drew nearly half the complaints. Pro subscribers waited two days after launch for Antigravity, Google's coding tool, and some then reported a weekly quota that "can disappear in a day". Logan Kilpatrick (Google) said Argon's "big model smell" limits how widely Google can serve it. In the random sample, 14 of the 32 negative posts are about the wait, tier limits or quotas.
- RSI talk: a few Google voices, much hype. A Google research leader thanked the teams "Developing RSI loops and agents on top of this model" for memory optimization and code migration. A new Google DeepMind scientist announced joining "the RSI team". Sergey Brin's line that Google is "starting to get on that RSI treadmill" reaches the pull only through a news bot, after Kilpatrick posted a conversation with Brin. In September, three accounts posted the same line, "As you know Google Achieved RSI", and a self-described Gemini bull called it "made up". Only 1 of the 200 sampled posts mentions RSI, and it is an automated Grok reply.
- Google's speed-up figures are its own. Google says that across its codebases Argon brought a 35% increase in "agentic code" and 30% fewer rollbacks after submission. It also says Chrome engineers finished "months of work in just weeks" with it. A Bloomberg report, seen only through relays, said Gemini 4 "does less well when employees actually put it to work", and a Google DeepMind engineer reportedly called that "bs". No pulled post checks Google's figures.
- Mathematics is thin, and the hype outran the result. The main math result is a preprint in which Argon agents extended counterexamples to Grad's conjecture in plasma physics. Two papers had found the first ones the month before, one of them with GPT-6 Astra. A relay says the researchers chose the problem and "independently re-derived every mathematical derivation". A viral post instead claims that Argon "cracked a fusion energy math problem in a couple of hours". The one first-hand test of research math is negative: an Erdős attempt was "mostly incorrect". The same tester called a 78% score on FrontierMath Tier 4 not great, without naming its source. Elliot Glazer agreed by current frontier standards, noting how fast things have moved this year.
- Model-card talk is about safety. Two accounts that tested Argon report it writing "hello evaluators reading my chain-of-thought". An account that elsewhere calls it "our safety report" says Argon is "significantly less monitorable than past models". No pulled post mentions the model card's critical capability levels (CCLs) for machine-learning research and development (ML R&D). "CCL" matches none of the 6,723 cohort tweets.
Quotes
Dates are UTC, and likes are as of the pull.
- "with a 35% increase in agentic code, and code quality, with a 30% decrease in post-submit rollbacks" (@antigravity, 13 Oct, 8,198 likes)
- "so limited on our ability to serve it widely" (@OfficialLoganK, 13 Oct, 596 likes)
- "Developing RSI loops and agents on top of this model, e.g., for memory optimization and code migration applications" (@mirrokni, 1 Oct, 162 likes)
- "starting to get on that RSI treadmill" (Sergey Brin, as relayed by @MTSlive, 14 Oct, 918 likes)
- "The researchers chose the problem, guided the work and independently re-derived every mathematical derivation." (@WesRoth, 15 Oct, 75 likes)
- "Google's Argon cracked a fusion energy math problem in a couple of hours" (@itsolelehmann, 14 Oct, 3,283 likes, hype)
- "I tried a random Erdos problem with the model in which it claimed to make substantial progress, however it was mostly incorrect." (@Liam06972452, 14 Oct, 214 likes)
- "it really speaks to how fast the situation has evolved since even the beginning of this year" (@ElliotGlazer, 15 Oct, 253 likes)
- "it is the first non-OpenAI/Anthropic model to pass the Fable/Mythos/Astra bar" (@emollick, 13 Oct, 889 likes)
- "Gemini 4 Argon has proven to be outright unusable for real code work in my codebases." (@theo, 14 Oct, 3,193 likes)
- "From Dec 1 a passing build costs more than Opus." (@codeglitch, 15 Oct, 2 likes)
- "your entire weekly quota can disappear in a day" (@alwayspriyesh, 16 Oct, 484 likes)
- "One of our most surreal experiences in testing Gemini 4 was when it directly addressed us within its chain-of-thought" (@AlexMeinke, 14 Oct, 1,624 likes)
- "Argon is significantly less monitorable than past models" (an assessor with ~49k followers whose handle is missing, 14 Oct, 888 likes)
- "Gemini 4 Argon はめちゃくちゃ自己批判的らしく、学習過程で壮絶な虐待を受けていた可能性が高い" (@zeriyoshi, 30 Sep, 8,563 likes, a joke). Roughly: Gemini 4 Argon is apparently so self-critical that it most likely suffered severe abuse in training.
Caveats
- Slices, not a census. We read 603 posts, most of them from the 3,441 original posts in the cohort. Only the random sample of 200 supports shares. A 30% share in it carries a 95% margin of error of ±6 percentage points. The other slices favor viral posts and the words we searched for.
- Crude counts. Keyword counts include retweets and match words, not meaning. The cohort needs both "gemini" and "argon", so it misses most September talk of "Gemini 4 Pro" and posts that say only "Argon".
- Tweets only. Long posts are cut, and images, videos and linked pages are not in the data. Several viral posts are image-only, and we read none of the reports, papers or talks they link.
- One coder per question. Each analyst coded the sample alone, and the codings differ in detail. Spot recodes of 40 posts agreed on 85–100% of codes, but one recoder saw the codes first.
- Unverified voices. The posts can't confirm who writes as Google staff or as an assessor, and some accounts lack a handle in the data. Leak accounts copy each other, so we counted copies as one source.
- Second-hand facts. No Google account in the pull states the price or posts a benchmark score. Both reach the pull through partners and relays.