The Antigravity Team said on 10 November that Gemini 4 Carbon is rolling out inside Google Antigravity, together with a preview of /swarm. Carbon is for Google AI Ultra subscribers in the Antigravity App, the Antigravity CLI and Antigravity IDE extensions; the models table also lists it for enterprise. /swarm is a separate preview: the product docs say it is available on Google AI Pro and Google AI Ultra, in the App and the CLI, not in the IDE extensions.
This sits next to the broader 10 November opening of Carbon on the paid Gemini API, which we record as an update on our earlier Carbon post.
What /swarm does
Type /swarm and a task, and your current conversation becomes the coordinator of a team of named workers. The docs say the coordinator splits work into pieces that should not collide, posts a public brief for each worker, and usually adds a @verifier for every two to four workers to read diffs, run tests and send problems back. Everyone talks on one shared, append-only message board, with @name, @group or @all mentions and no private worker-to-worker chat. A @monitor worker stays asleep while the swarm is making progress and posts only if everyone has gone quiet before the work is done.
Idle members wait without using tokens, and wake when someone mentions them. The coordinator, the docs say, does not do the technical work itself: it hands out tasks, judges what comes back and reports to you.
The 10 November blog describes workers in “isolated git worktrees so edits never collide” and calls the checkers “adversarial verifiers.” The docs are narrower. Workers share your workspace by default, and “when several workers edit or build at the same time, the coordinator can give each one its own working copy.” Removing a worker deletes that copy, so changes need to be landed first. We have not run a swarm, so we are reporting the docs, not a test.
The App changelog lists /swarm among the v2.31.0 changes dated 9 November. Carbon itself, and the CLI preview (/swarm, /swarm board) in v1.5.5, are dated 10 November, the same day as the blog post.
How you watch it
In the App, the coordinator’s reply includes a link that opens a Swarm pane in the side panel, with three tabs: Board (the live feed), Members (each agent’s status and model) and Graph (who mentioned whom, with a replay). The docs also mention opening it later from Overview > Extensions > Swarm.
In the CLI, a status row appears under the prompt while a swarm runs. /swarm board, or Alt+S, opens a full-screen terminal board with a Roster, a Posts feed and a Message pane. On macOS, the docs say Alt+S works only if the terminal sends Option as Alt; the slash command and the status row work in every terminal.
You can keep talking to the coordinator while the workers run, or open a worker’s conversation to message it directly.
Where Carbon fits
Google still presents Gemini 4 Argon as the better default for most advanced engineering and knowledge work. Carbon, it says, is built to explore more thoroughly and to run longer verification loops, using more tokens. The Antigravity blog suggests pinning Carbon on high-leverage roles (coordinator, architecture, cybersecurity auditing and verification) and lighter, faster models on parallel file edits. The docs say workers start on the same model as the conversation; you change that by asking in the prompt, or by asking the coordinator to move a waiting worker later, and the model has to be one you can pick. The blog shows pinning from the Members roster; the docs do not describe a click-to-pin control, and we have not seen the UI ourselves.
On the models table (checked 12 November), Carbon is listed for Ultra and enterprise only, not for Free, Plus or Pro. Argon is listed for paid Pro (with a footnote), Ultra and enterprise. So a Pro subscriber can start a /swarm preview, but cannot put Carbon on a worker unless their plan changes.
Access, quota and the rest
/swarm is in preview. Both the blog and the docs warn that a swarm uses quota much faster than a normal chat, even with zero-token idle waits. If a member runs out of quota, the docs say it pauses instead of retrying, and it does not restart on its own when quota refreshes: it stays paused until there is a new board post, its model is switched, or you message it.
Enterprises, the blog says, can access Carbon in Gemini for business. Scientists and researchers can apply for a chance at both Argon and Carbon on Antigravity’s highest usage tier, free for six months, onboarded on a rolling basis and, in the Google blog, subject to eligibility, capacity and selection.
Google says that in five weeks of internal dogfooding, engineers used swarms for multi-package migrations, cross-subsystem investigations and architectural redesigns. That is Google’s own account of internal use.
The same Google blog claims first place for Carbon on CursorBench 4.0, Perplexity’s WANDR and Zapier’s AutomationBench, at more than 2x lower cost per task than the next external model. On 12 November, Cursor’s own CursorBench 4.0 table listed Gemini 4 Carbon High first at 60.4% ($9.22 per task), just ahead of Carbon Medium at 60.1% and Claude Fable 5.2 Max at 60.0% ($32.79). Zapier’s AutomationBench listed Carbon High first at 53.88% ($2.12), ahead of Carbon Medium at 52.97% and Fable 5.2 Max at 51.45% ($4.64). Those are the vendors’ boards, and Cursor notes that small score gaps may not be meaningful. We did not find a current official WANDR results table that shows Carbon first, so that part stays a Google claim.
Why it matters
Antigravity already had subagents, /boost and /teamwork. /swarm is the option the docs recommend when a task is large but splits cleanly across files, packages or questions, and you want to watch and steer the team. The interesting product choice is the shared board, plus the ability to put a more expensive model on the coordinator or the verifier and cheaper ones on the file-level work. It is still a preview, it will chew through quota, and Carbon itself remains an Ultra (or enterprise) add-on. Google still tells most people to use Argon.
The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment