Antigravity 2.12.0 Introduces the /boost Command
A deep dive into Antigravity 2.12.0's new /boost command, comparing its focus, workflow, and execution model against /teamwork-preview multi-agent collaboration.
#Antigravity #AI Agent #Boost
Both /boost and /teamwork-preview represent advanced execution paradigms in Antigravity for tackling sophisticated engineering tasks. However, they differ fundamentally in architectural focus, team topology, and upfront alignment:
1. Core Positioning and Target Scenarios
| Dimension | /boost (Deep Hardening / Focused Delegation) | /teamwork-preview (Multi-Agent Teaming / Systems Projects) |
|---|---|---|
| Primary Focus | Vertical Depth: Solves singular, highly complex tasks requiring sustained deep reasoning and exhaustive verification. | Horizontal Scale: Coordinates large, cross-module systems requiring multi-role specialization or massive parallel exploration. |
| Use Cases | • Complex architectural refactoring and non-trivial algorithms • Elusive bug root-cause analysis, deadlock/perf troubleshooting • Single-topic technical investigations and strict trade-off evaluations | • Green-field system builds from 0 to 1 (e.g., compilers, full-stack web applications) • Formal theorem verification and large-scale parallel search • Comprehensive multi-stakeholder technical documentation reviews |
| Agent Topology | Orchestrator delegating to specialized deep agents: • DeepCoder (laser-focused implementation)• DeepInvestigator (root cause & empirical verification) | Dynamic multi-agent team tailored to project archetype: • Review panels / formal verification pipelines • Massive parallel exploration swarms (scaling to dozens/hundreds of agents) • Modular development and adversarial auditing squads |
2. Workflow and Interaction Differences
/boost: Rapid Routing and Autonomous Convergence
- Zero Front-Loaded Bureaucracy: The Orchestrator automatically selects Solo vs. Delegation execution without requiring extensive requirement negotiation.
- High-Fidelity Goal Handoff: Delegates the exact context directly to deep subagents without forcing users into rigid specification templates.
- Iterative Verification Loop: Once the worker completes a draft, the orchestrator acts as a strict adversary—challenging edge cases and driving extra correction turns until requirements are fully satisfied.
/teamwork-preview: Rigorous Specification and Acceptance Contracts
- Two-Phase Methodology: Enforces a strict boundary between (1) Prompt Engineering & Contract Definition and (2) Formal Autonomous Launch.
- Anti-Self-Certification: Interactively drafts objective acceptance criteria and guardrails to prevent agent teams from prematurely declaring success without verification.
- Artifact-Driven State: Actively maintains a structured
prompt_draft.mddraft artifact before commissioning multi-agent swarms.
3. Rule of Thumb
- Choose
/boostwhen you have a single tough nut to crack (a gnarly bug, a delicate refactor, or complex algorithms) and need an expert agent to drill deep and stress-test the solution. - Choose
/teamwork-previewwhen you are kickstarting an expansive system project or parallel exploratory workload where defining explicit acceptance criteria and coordinating diverse sub-agents is crucial.
