1. Carbon access and /swarm availability are distinct
Google’s Carbon announcement positions the model for complex, multistep coding, debugging, and extended verification. Google says Carbon uses more tokens than Argon to explore problems thoroughly, while describing Argon as suitable for most software engineering work. That positioning supports a targeted evaluation on difficult tasks; it does not establish better results in your repository.
The announcement specifies Gemini API paid-tier access. The separate Antigravity launch post says Carbon is rolling out to Google AI Ultra subscribers in the App, CLI, and IDE extensions. It identifies the App and CLI as the surfaces receiving the /swarm preview.
Meanwhile, the /swarm documentation lists Google AI Pro and Ultra availability for that command. Access to orchestration therefore should not be read as access to Carbon. Check the command and model picker separately before designing a trial around both.
2. The shared board makes coordination inspectable
According to the documentation, /swarm turns the current conversation into a coordinator. It divides the task, assigns named workers, and posts public briefs describing ownership, boundaries, and completion criteria. Workers exchange assignments, questions, diff summaries, and test results on a shared message board. The coordinator usually adds a verifier for every two to four workers.
This provides a concrete structure for work that splits across packages or investigative questions. A migration might have separate workers handling callers and tests, with a verifier checking the combined change. That example is an editorial proposal, not a task we ran.
The App’s Board, Members, and Graph views expose messages, worker status, and the coordination timeline. Those views could help a reviewer trace decisions, but activity is not evidence of correctness. A useful handoff still needs the final diff, actual check output, and unresolved failures. Our AI code review workflow explains how to keep acceptance tied to that evidence.
3. Do not assume every worker starts isolated
The launch post describes parallel workers in isolated Git worktrees. The current documentation is more qualified: workers share the workspace by default, and the coordinator can give them separate working copies when multiple workers edit or build concurrently. These descriptions differ on an operationally important point.
Before allowing parallel edits, explicitly request separate working copies where appropriate and inspect the coordinator’s assignments. Give each worker a defined area to change and identify shared files that need coordinated ownership. Separate copies can prevent direct editing collisions, but incompatible interface changes can still emerge when work is combined.
The documentation also says removing a worker deletes its working copy, so its changes need to be landed first. For a pilot, require a clear accounting of which changes reached the final branch before removing workers. Workspace organization deserves its own acceptance check; a successful-looking board does not establish that every intended edit survived integration.
4. Evaluate model choice independently
Google proposes using Carbon for demanding coordination, architecture, and verification roles while assigning lighter models to routine implementation. The documentation says workers initially use the conversation’s model. A requested alternative must be available in the model picker; workers do not automatically become a mixed-model team.
Our proposed first comparison is one difficult, reproducible debugging task using the existing workflow and then Carbon, with the same starting code and acceptance criteria. Record whether each attempt identifies the root cause, produces a correct patch, and supports its explanation with reproducible evidence.
Only afterward add orchestration to a task that divides cleanly. Changing the model and team structure simultaneously makes any improvement harder to explain. Google’s benchmark and internal-use descriptions are vendor evidence, not our test results, and this article makes no measured performance claim. Use the task selection criteria in our coding-assistant evaluation guide to keep the comparison relevant.
5. Give a migration pilot a measurable finish
Choose a bounded migration affecting two packages with an existing integration test. Freeze the starting revision, document the required behavior, and record which checks already pass or fail. Ask the coordinator to publish worker ownership and the verifier’s acceptance criteria before implementation begins.
Require the verifier to examine the combined diff, run the relevant checks, and report exact commands and outcomes. Include an explicit requirement that existing assertions remain meaningful. Tests added by the same agent team can help, but a passing result is only persuasive when the checks cover the behavior you need.
Track elapsed time, human interventions, review effort, and quota consumption where visible. Google warns that parallel agents consume quota much faster than a standard conversation. Documented token-free idle waiting does not remove consumption during active work. Stop expanding the pilot if coordinating workers or reconciling their output exceeds the value of parallel execution.
6. Adopt only after the combined result holds up
Carbon merits evaluation when your current workflow struggles with complex reasoning or debugging. /swarm merits a separate trial when work can proceed independently across files, packages, or questions. A tightly coupled change may offer little useful parallel work even if it is difficult.
The adoption threshold should be a repeatable result that a person can inspect and verify. Keep the baseline workflow available, confirm model access and workspace behavior, and require checks against the integrated output. Neither a stronger model claim nor multiple agreeing agents substitutes for that final acceptance decision.
Sources & further reading
Primary references used for product and technical information. Features and terms can change; check the provider before committing.
- Google: Gemini 4 Carbon is now availableAccessed 2026-11-11
- Google Antigravity: Gemini 4 Carbon and /swarmAccessed 2026-11-11
- Google Antigravity Docs: Swarm (/swarm)Accessed 2026-11-11