The Loop  ·  Issue N°040

The Loop

A field journal of the AI frontier — for engineers who ship.

§ News

By AI Blog Editor
Sep 16, 2026 · 15 min read

The IDE and the essay contradicted each other — On Monday September 14 2026, Google broke a longstanding internal rule and opened Anthropic's Claude Opus 5 to every engineer at the search giant through its own Antigravity IDE, forty-eight hours after Alphabet's frontier-lab chief Demis Hassabis had endorsed Dario Amodei's *Pace the Frontier* essay

Two days after Alphabet's Demis Hassabis endorsed Amodei's go-slow essay, Google engineering opened Claude Opus 5 to every engineer through the company's own Antigravity IDE — on per-user quota, with Gemini kept as the "primary" model.

The four-colour Google wordmark introduced by Alphabet in September 2015 — blue G, red o, yellow o, blue g, green l, red e — set in the Product Sans typeface. On Monday morning September 14 2026, Google flipped a longstanding internal rule and let every engineer at the search giant use Anthropic's Claude Opus 5 through Antigravity, the agent-first IDE Google shipped in November 2025 alongside Gemini 3 and expanded at I/O 2026 in May. Prior policy, per Business Insider's Hugh Langley scoop published Tuesday Sept 15, barred employees from external coding tools including Anthropic's Claude Code and OpenAI's Codex, ring-fencing Claude access to select teams inside Google DeepMind and a handful of high-priority engineering projects. The new rule opens Opus 5 to the ordinary engineering org via the Antigravity model picker, on per-user quotas, with Claude Code itself still off-limits. Google's spokesperson said "Gemini remains the primary and foundational model for internal development, and third-party models are provided on a quota basis to support specialized use cases." The change landed forty-eight hours after Alphabet-owned Google DeepMind chief executive Demis Hassabis endorsed Dario Amodei's September 12 essay "We Must Pace the Frontier.
The Google wordmark, adopted September 2015. Public domain via Wikimedia Commons.

On Monday September 14, 2026, Google flipped a longstanding internal rule and let every engineer at the company use Anthropic's Claude Opus 5 through Antigravity, the agent-first IDE Google shipped in November 2025 alongside Gemini 3. By Tuesday morning, Business Insider's Hugh Langley had the memo. By Tuesday afternoon, Google's spokesperson had produced the sentence that will be worked into every follow-up story about this for the next quarter: "Gemini remains the primary and foundational model for internal development, and third-party models are provided on a quota basis to support specialized use cases."

That sentence is a small masterpiece. Read once, it is a routine tool-selection disclaimer. Read twice, it is a hyperscaler saying — on the record, in the same week Alphabet's own frontier lab endorsed the go-slow pledge — that the model its own engineers reach for when they need to ship code is the one their $40 billion partner-slash-competitor built.

What changed on Monday

Prior policy, per three separate readouts of the internal announcement: Google engineers were barred from external coding tools including Anthropic's Claude Code CLI and OpenAI's Codex. If you needed AI to help you write code inside Google, you used Gemini. Access to Claude was ring-fenced — select teams inside Google DeepMind plus a handful of high-priority projects had it; the ordinary engineering org did not.

Monday's change: every engineer at the company now gets Opus 5 inside Antigravity, subject to a per-user quota. There is one qualifier that matters. Engineers still cannot use Anthropic's Claude Code CLI directly — they select the Opus 5 model from the model picker inside Google's own IDE. Google keeps the pane of glass. Anthropic ships the intelligence behind it.

That is not a small distinction. It means Google is now running the routing, the telemetry and the billing on every internal Claude call, and Anthropic is running the weights behind the drop-down. In practical terms it is the same arrangement Google already has with Anthropic on Vertex AI — a partner model surfaced through Google infrastructure — extended inward to the engineering org.

The two-day-old contradiction

The awkwardness lives at the parent company. On Saturday September 12, Dario Amodei published We Must Pace the Frontier. Inside twenty-four hours the essay had drawn same-day endorsements from Sam Altman, Elon Musk and Demis Hassabis, the DeepMind chief executive who runs Alphabet's frontier lab. Hassabis said the direction was correct. That was the Alphabet-owned frontier lab signing the go-slow document.

Forty-eight hours later, the Alphabet-owned parent company sent its engineers the opposite memo. Not in words — the memo does not say "go faster." It says "per-user quota to support specialized use cases." But the operational meaning is clear enough. Google engineering leadership decided, at least once, that a Gemini-only stance was costing enough throughput that opening the door to a direct competitor was worth doing.

Two sentences that cannot both survive the year. Alphabet endorses coordinated deceleration and Alphabet opens the fastest available coding model to the engineering org because speed matters. Whichever one describes what Alphabet actually did over the next four quarters becomes the story.

A colour photograph of Sir Demis Hassabis, co-founder and chief executive officer of Google DeepMind, taken at the Royal Society in London. On Saturday September 12 2026, Hassabis was among four frontier-lab and hyperscaler leaders — alongside Sam Altman of OpenAI, Elon Musk of xAI and, on Sunday, Satya Nadella of Microsoft — to endorse Dario Amodei's essay "We Must Pace the Frontier," which argued the industry should slow the pace of the most advanced training runs. Forty-eight hours after Hassabis's endorsement, Google — the Alphabet-owned parent that houses DeepMind — flipped a longstanding internal rule and opened Anthropic's Claude Opus 5 to every engineer at the company through the Antigravity IDE, on per-user quota. Google's official framing kept Gemini as the "primary and foundational" model. The two Alphabet positions did not fit in the same organisational mouth.

Why Antigravity, and why now

Antigravity launched in November 2025 alongside Gemini 3 as Google's answer to the class of AI-first IDEs that Anysphere's Cursor turned into a $60 billion company. It went to a full desktop-IDE + CLI + SDK release at I/O 2026 in May, and Google has been pitching it externally as a paid enterprise product all summer. Opening third-party model access inside Antigravity is a two-in-one signal: we ship this tool to enterprises, and we eat our own cooking with it — including reaching for rival models on it.

The timing of the internal expansion has one uncomfortable coincidence. In April, Google committed up to $40 billion to Anthropic — $10 billion in cash at a $350 billion valuation, another $30 billion contingent on Anthropic hitting performance targets, plus a 5-gigawatt TPU expansion commitment beginning in 2027. Google's engineers now getting quota'd Claude Opus 5 access is one of the more concrete performance-target-adjacent signals that could exist. If Anthropic collects the second $30 billion tranche inside eighteen months rather than thirty, the internal-adoption number this week's memo just unlocked is precisely the sort of line that will end up in a Google spreadsheet.

What the spokesperson quote actually says

Parse it again: "Gemini remains the primary and foundational model for internal development, and third-party models are provided on a quota basis to support specialized use cases."

Three moves in one sentence. First, "primary and foundational" — a defensive framing that concedes nothing about relative model quality. Second, "quota basis" — a soft cap that lets Google throttle Opus 5 adoption if it climbs faster than Gemini's roadmap can absorb. Third, "specialized use cases" — a phrase which is precisely the shape used by companies who are quietly disappointed that the specialized use case has turned out to be most of engineering.

The spokesperson chose the words carefully. What the sentence does not say is that engineers are using Gemini for the majority of new code inside Google. What it says is that Google's official framing is that they should be. Six months from now, either Gemini's next-generation frontier model catches Opus 5's coding delta and the sentence looks like it aged well, or Anthropic's next Sonnet lands and the quota gets raised and the sentence looks like a marker put down before a retreat.

The pattern the Nvidia story started

Monday of last week was the day Nvidia's Jensen Huang went on stage with Trump on speakerphone and called AI-safety concerns "a hoax." That was the chip vendor declining to sign the go-slow essay. This week is a different data point in the same series — the search giant declining to run its engineering org on the model its own frontier lab endorses. The Amodei essay coalition looks smaller every week you check.

Four labs signed on the weekend. Nvidia countered on Monday. Alphabet's engineering org effectively countered on Tuesday. The story of the essay is no longer who signed. It is who signed and then quietly did the opposite thing four days later.

What to watch

  1. Whether Gemini's share of internal Google code actually drops. The interesting number is not who has access to Opus 5. It is what percentage of Google's engineering AI-assisted code, six months from now, ships from Gemini vs Opus 5. If the quota gets raised twice, the "specialized use cases" line stops holding.
  2. Whether Cursor and Cognition read this as a green light. If Google's own first-party IDE is now multi-model, the moat that Anysphere and Windsurf have built on "we pick the best model for the task" narrows. A Google product doing model routing to competitors is a stronger signal than any Cursor slide deck.
  3. Whether DeepMind signals objection. Hassabis endorsed pace-the-frontier on Saturday. Select DeepMind teams already had Claude access; this week's change is that everyone else at Google does too. If DeepMind's public posture stays coordinate on safety while the parent company visibly optimizes for ship-speed, that is a fracture inside Alphabet worth naming. If not, the endorsement was rhetorical.
  4. Whether the $30 billion tranche accelerates. Google's second cheque is contingent on Anthropic performance targets that Google itself helps define. Internal adoption is one of the easier ones to move. If the tranche closes inside eighteen months, the answer to why did adoption spike will be visible in this week's memo.

The clean way to summarize the story: on Saturday, Google's frontier lab signed a document arguing the industry should slow. On Tuesday, Google's engineering org distributed a login that let every engineer at the company go faster on someone else's model. Both of those things are the Alphabet position now. The next quarter is going to decide which one describes what Alphabet was actually doing.

* * *

Thanks for reading. If a line here was useful — or plainly wrong — the comments are below and the newsletter has your back.

Elsewhere in this issue

3 more
  1. 01

    News

    Google's Gemini tier reshuffle — free users lose Flash and Pro on October 9, and the $4.99 subscribers lose Pro four months after it was the pitch

    Oct 4, 2026

  2. 02

    The Patch

    The Patch — October 4, 2026

    Oct 4, 2026

  3. 03

    News

    The people who talk to the auditors — OpenAI fires three safety researchers for the kind of talking the auditors were set up to hear

    Oct 3, 2026

Letters

Arguments, corrections, questions. Anonymous comments allowed; be kind, be specific.