Google is internally testing a new Gemini 4 checkpoint codenamed Carbon on its Jetski coding platform, with at least one employee describing its coding performance as comparable to Anthropic's Claude Opus 5.5 - though Google has confirmed no benchmarks, release date, or public availability for Carbon.

The entire Carbon story rests on internal Slack-style messages and screenshots relayed to a single Business Insider reporter, not on anything Google has confirmed ^[1]. The checkpoint has no public model ID, no API endpoint, no published price, no model card, and no stated evaluation methodology - it doesn't even appear in the menus for AI Studio, Antigravity, or Vertex AI ^[2]. The much-repeated 'feels like Opus 5.5' comparison is one employee's subjective impression, explicitly hedged with a caveat that more testing is needed ^[3], and online reaction has already needled the reporting itself, questioning whether the outlet understood what a model checkpoint even is ^[1].

Google's naming makes more sense once you see the lineage: the publicly announced Gemini 4 Argon, which began rolling out around September 30, 2026, corresponds internally to a checkpoint called Barium-B, while Carbon is described as a later checkpoint still confined to internal testing ^[1][2]. That pipeline traces back to Google Antigravity, the agentic coding environment launched alongside Gemini 3 in November 2025 and now tied to the internal Jetski platform where Carbon is being run ^[4]. By September 23, 2026, DeepMind's Koray Kavukcuoglu had already said Gemini 4 was in post-training and being tested inside Antigravity, with hopes of an early post-training release before year-end ^[5].

Reports frame Carbon's internal testing as a direct response to Anthropic's Claude Opus 5.5, with Google racing to close or exceed the coding-performance gap just weeks after Argon's launch ^[3]. The urgency shows in how fast the iteration is moving: Carbon surfaced in internal tests before Argon had even finished its staged public rollout, which outlets have read as part of a broader push to win developer mindshare in agentic coding ^[6]. Some employees go further, attributing the jump to Recursive Self-Improvement (RSI) techniques - an unconfirmed internal theory, not an official Google explanation ^[7]. What Google can point to publicly is Argon's own benchmark record: 68% on CWE-bench v1 (tied for first place) and 77.9% on the DeepSWE v1.1 software-engineering benchmark ^[8]- solid numbers, but not the same as a verified Opus 5.5-beating claim for Carbon, which has no published scores at all.

Google has not said whether Carbon becomes a future Argon update, a distinct Gemini 4 release, or stays an internal-only checkpoint that users never see ^[2]. That ambiguity matters because Argon itself was first released narrowly, through the Fairwind Program for trusted cyber-defenders, rather than to the public at large ^[8]. Wall Street has noticed Google's broader release pattern: JPMorgan analysts argue Google has 'struggled to translate ongoing product velocity into splashy releases that resonate with consumers, capture sustained mindshare, and meaningfully drive sentiment around AI leadership' ^[9], which is exactly the risk a leak like Carbon's runs into - impressive in private, invisible in the market until (or unless) it actually ships.

The reaction to Carbon splits cleanly by platform. On X and YouTube, AI-news accounts treated the leak with excited, speculative energy, lining Carbon up alongside other concurrent frontier-model rumors and framing it as a serious rival to Opus 5.5 and even GPT-6. One recurring detail from that side of the conversation: Google itself appears to have slipped Barium-B - the internal checkpoint that became the public Argon release - into the LMSYS Chatbot Arena disguised under a decoy model name to gauge real-world performance before any official reveal, a practice that shows Google was already testing checkpoints incognito well before the Carbon leak surfaced. Reddit's response ran in the opposite direction. The Gemini community there treated the leak as the latest entry in a tiring pattern of 'next checkpoint beats everything' stories, with one post bluntly titled to mock Google for teasing newer models before Argon itself was even broadly available to paying users. The most upvoted skeptical take argued Carbon is probably not a distinct model tier at all, just an internal build feeding into the existing Argon release - a far less exciting story than the Opus 5.5 comparisons circulating elsewhere. That gap between hype and skepticism is itself revealing: it shows an audience that has been burned before by leak cycles that never translate into a shipped product, sitting right alongside a louder crowd eager to anoint the next frontier model before Google has said a word.