FULL STORY

Antigravity Swarm: From Leak to Launch

After TestingCatalog leaked and tested Google's in-development Agent Swarm mode, Antigravity officially launched /swarm alongside Gemini 4 Carbon, letting users orchestrate multiple agents through a coordinator.

2026-11-10 ~ 2026-11-11 · 2 episodes · 7 posts

Episode 1 · Google Reportedly Building Agent Swarm Mode for Antigravity (2026-11-10, 2 posts)

TestingCatalog reports Google is building an Agent Swarm mode for Antigravity, a /swarm slash command that launches multiple agents collaborating on a shared message board, possibly replacing Chief of Staff.

Episode 2 · Google Antigravity launches /swarm multi-agent orchestration (2026-11-11, 5 posts)

Alongside the release of Gemini 4 Carbon, Google Antigravity has launched /swarm, a multi-agent swarm feature. Users talk to a single coordinator agent, which distributes tasks to multiple workers—each represented by a bee avatar—running in isolated, parallel workspaces. In clmt's view, the paradigm is shifting from "watching a single coding agent think in a terminal" toward orchestrating teams of specialized agents.

Confirmed

  • /swarm is Antigravity's multi-agent orchestration feature, launched alongside Gemini 4 Carbon; a single high-level instruction can spin up a collaborating agent team
  • Workers have named roles, operate in multiple isolated parallel workspaces, and go through a dedicated verification step
  • Carbon serves as chief architect and security auditor on the team: handling system design, cross-agent coordination, and deep invariant checks, while acting as Lead

Why it matters

  • clmt argues that single-agent workflows have hit a ceiling on complex repo changes: one context window must juggle architecture design, touching 30 files, writing tests, and self-reviewing—and self-review is exactly where subtle bugs slip through
  • Dividing labor across agents (design, implementation, and verification each handled separately) promises to close the blind spots of single-context self-review, distributing quality responsibility for complex repo-level changes across dedicated roles