AIREITERFifty million lines of Lean 4 for one proof, 800,000 lines of safe Rust in two weeks, TPU kernels 4.09x faster — Google's November 13 research update shows what Antigravity Teamwork can do. Antigravity Teamwork usually pays off only for milestone-based projects that run for hours or days, because a single run can consume a large share of a weekly quota.
What Antigravity Teamwork actually is
Antigravity Teamwork is Google's multi-agent orchestration workflow for large, verification-heavy work inside Antigravity. The /teamwork command launches a coordinated team — Sentinel, Project Orchestrator, Explorers, Workers, Critic, Challenger, Auditor, and Success Auditor — that plans in milestones, works in a dedicated project directory, and gates every milestone with independent verification.
Teamwork runs in two phases. Phase 1 is a scoping interview: the main agent records goals, requirements, verification methods, acceptance criteria, and the project directory (default ~/teamwork_projects/{PROJECT_NAME}). Phase 2 is autonomous execution through structured artifacts — request, project plan, and progress records — with exclusive file ownership per Worker and Critic, Challenger, Auditor, and Success Auditor gates before handoff (Teamwork docs).
Integrity modes set during the interview control strictness:
development(default): rapid iteration; code reuse and frameworks allowed, fabricated outputs and facade implementations rejected.demo: reproducible presentation; copying core logic from open source, delegating core work externally, and reading test sources for answers are prohibited.benchmark: maximum strictness; from-scratch implementation in the language standard library with independent ground-truth evaluation.
Execution paths adjust team shape automatically:
- General distributed coding (default): multi-file engineering and refactoring.
- Iterative coding: one contained fix when the prompt says "keep it small."
- Document Review: multi-angle critique of papers and design docs.
- Math / Proof and Math / Proof Large Team: formal reasoning and large conjecture campaigns.
The typical horizon is hours to days on paid plans in the Antigravity App and CLI (Teamwork docs).
Teamwork vs Swarm vs Boost vs subagents
Antigravity Teamwork is the right choice only when the task needs milestones, audit gates, and a dedicated directory. Most daily work belongs to the lighter options, and picking wrong burns quota for nothing.
| Tool | Best for | How it starts | Workspace | Verification | Typical horizon | Plan |
|---|---|---|---|---|---|---|
| Subagents | Focused side tasks: repo research, browser checks, test runs | Automatic or @subagent | Current workspace | Parent agent checks reply | Seconds to minutes | All plans |
Boost (/boost) | Hard but narrow problems: race conditions, tricky bugs, algorithms | /boost <task>, starts immediately | Current workspace, isolated contexts | Workers challenge and re-verify, orchestrator spot-checks | Seconds to hours | Paid plans |
Swarm (/swarm) | Broad work that splits cleanly: files, packages, test suites | /swarm <task>, starts immediately | Current workspace or per-worker copies | Dedicated @verifier reviews diffs, runs tests | Minutes to hours | Google AI Pro and Ultra |
Teamwork (/teamwork) | Multi-milestone projects: migrations, simulations, formal proofs | /teamwork <goal> + scoping interview | Dedicated ~/teamwork_projects/{PROJECT_NAME} | Critic, Challenger, Auditor, Success Auditor gates | Hours to days | Paid plans |
Use Teamwork for a REST-to-Fastify migration across dozens of files with full test coverage, a cycle-accurate simulator validated against hardware timers, or a formal proof with Lean 4 checking. Use Swarm for adding validation to three independent API handlers with one worker per file plus a verifier running npm test. Use Boost for a single race condition or a coupled refactor where sequential challenge-fix-verify beats parallel workers. Use subagents for background research while the main conversation continues.
The confusion is real. As one Antigravity user put it:
"agy has way too many modes now and honestly it's getting confusing. right now we have ... /teamwork (long milestone projects with audit gates) ... and now dynamic workflows... to be fair, we really don't need all of them. fewer modes = less confusion..."
— @Heamanth_alturi (X)
Rule of thumb: if the task has one definition of done and finishes in one sitting, Teamwork is overkill. If the task needs a plan artifact, a progress artifact, and someone other than the author to sign off each milestone, Teamwork fits.
What the November research update actually proved
The November 13 Google Research update is a results report, not a launch announcement. Teamwork existed earlier as /teamwork-preview for paid plans; the update documents what milestone-based teams achieved with Gemini 4 Argon, Carbon, and Hydrogen. Humans still defined problems, constraints, and evaluation setups while fresh critics reviewed from clean contexts.
| Domain | Example project | Agent scale | Reported outcome |
|---|---|---|---|
| Mathematics | Courtade–Kumar conjecture proof (Google, CUHK, USC, CMU) | Long-proof pattern, Lean 4 formalization | Full proof at ~50M lines of Lean code |
| Chemistry | Molecular structure from NMR data | 30 specialized agents + physics simulator | 95% top-1, 100% top-3 exact match |
| Systems | Zircon C++-to-Rust rewrite | Two-week Argon campaign | ~800K lines safe Rust, booted on arm64 |
| ML hardware | TPU kernel optimization (DuoDiscover) | Proxy evaluators (23s vs 7–32 min) | 4.09x mean speedup on 17 JAXBench kernels |
Google also opened applications for 10,000 academic researchers to receive six months of top-tier access. Some workflows in the post are still rolling out to external users, so treat the table as capability evidence, not a promise that every project reproduces these gains.
The quota bill official pages don't show
Antigravity pricing (pricing page) lists Individual at $0/month with unlimited Tab completions and basic weekly limits, plus Pro and Ultra with higher limits and a flexible AI credit pool; exact request counts are not published. Pro and Ultra quotas refresh every five hours until the weekly ceiling hits, and overage can use purchased credits with a Never or Always setting (plans docs). Teamwork and Boost require paid plans; Swarm requires Pro or Ultra (Swarm docs). Google's own OS post warned that a couple of complex preview tasks could consume an entire weekly quota (Antigravity OS post).
Anecdotal user reports, not a representative sample, range from manageable to severe:
"holy crap that sucked all my quota in about only 5 minutes (3.5 Flash (high))"
— u/Several_Bag_3665 (Reddit)
"very usable on ultra sub actually, had a teamwork preview with gemini flash medium going for 50 minutes straight and it took about 20% of my 5-hour quota and did huge refactorings properly"
— u/ningkaiyang (Reddit)
Two mechanics explain the spread. Antigravity documents for /swarm that every worker is a separate agent, waiting workers consume no tokens, and quota-exhausted workers pause instead of auto-retrying until a new board post, model switch, or direct message (Swarm docs); the Teamwork docs do not publish the same resume statement, so treat this as shared multi-agent behavior to verify on your plan. Teamwork also generates large intermediate artifacts — request, plan, and progress records plus per-agent scratch notes and verification logs (Teamwork docs) — which is expected state, not necessarily progress.
Run your first Teamwork without burning a week of quota
Starting Teamwork takes one command, but the scoping interview decides the bill. In the App, open a project conversation and type /teamwork Migrate our REST API service from Express to Fastify, including full test coverage, TypeScript typing, and benchmark validation. In the CLI, run /teamwork Design and implement a cycle-accurate memory controller with lockstep simulation tests from the project directory. Monitor through the subagent panel or CLI status bar, jump to approvals with Alt+J, and inspect plan and progress artifacts in real time (Teamwork docs).
Treat Phase 1 as the cost control. Specify what, not how: the goal, the audience (demo vs production vs benchmark), hard constraints, and one objective check per requirement such as a test suite or metric script. Choose development for iteration and reserve demo or benchmark for cases where presentable or from-scratch proof matters, since stricter verification implies more agent work. Confirm the dedicated project directory before approving.
During execution, keep steering central. Route scope changes through the coordinator, land worker changes before removing workers, and judge progress by milestone gates and test evidence rather than file count. In Settings, set AI-credit overage to Never for the first run so baseline exhaustion stops work instead of spending credits silently (plans docs). Where plan docs allow it, pair a stronger planner with cheaper implementation — Ultra supports Orchestrator (Carbon) and Orchestrator (Argon), which plan with Gemini 4 Carbon or Argon while Gemini 4 Hydrogen implements (pricing page) — a trade-off also visible in Carbon vs Argon comparisons.
FAQ
What is the difference between /teamwork and /teamwork-preview?
/teamwork-preview was the earlier research-preview name. Current Teamwork docs use /teamwork on paid plans; Google has not published a separate general-availability statement.
Can Teamwork be paused or recovered after quota exhaustion?
Documented /swarm behavior is that quota-exhausted workers pause until a new board post, model switch, or direct message (Swarm docs); Teamwork docs do not confirm the same resume path. Check the plan and progress artifacts in ~/teamwork_projects/{PROJECT_NAME} before restarting, since partial milestones persist as files.
What artifacts will Teamwork generate?
Request, project-plan, and progress artifacts plus per-agent scratch notes, helper scripts, and verification logs (Teamwork docs). Large Markdown output is normal; judge progress by milestone gates and test evidence, not file count.
Is Teamwork safe for production repositories?
Teamwork isolates work in a dedicated directory with exclusive file ownership and audit gates, which reduces collision risk (Teamwork docs). Production use still needs human review of acceptance criteria, test evidence, and the final Success Auditor pass before merging.
Your 30-second checklist before typing /teamwork
Type /teamwork only when all five hold: the work spans multiple milestones, each milestone has an objective check, a dedicated directory helps, independent audit gates matter, and one quota-heavy run is cheaper than weeks of manual work. Otherwise use Swarm for parallelizable breadth, Boost for hard narrow bugs, or subagents for background side tasks — then save Teamwork for the project that actually needs a team.