Designing a Team of Agents: How Google Antigravity Structures Subagents for Autonomous Code Generation

Google Antigravity Breaks Down Its Agent Team Architecture

Google Antigravity has released details on how it organizes a team of autonomous agents for building software. Rather than a single agent handling everything, the system uses seven specialized subagent types, each with focused goals and constraints. This pattern is relevant for OpenClaw as it designs its own subagent system.

Key Details: The Seven Agent Roles

The blog post identifies the following agent types:

• The Sentinel — Acts as the “front-desk manager.” Does not write code, analyze logs, or make technical decisions. Its job: structure user intent, spawn the Orchestrator, and supervise overall task completion.
• The Orchestrator — A dispatch-only manager. Never writes code or executes builds. Focuses on decomposing requirements into milestones, kicking off other specialized subagents, and synthesizing reports.
• The Explorer — Analyzes requirements and previous logs to write formal strategies for the Orchestrator. Never writes code itself.
• The Worker — The actual coder that implements strategies, builds code, and runs tests.
• The Reviewer — Independently reviews the Worker’s changes for design correctness, edge cases, and interface contract compliance.
• The Critic — Stress-tests the solution, runs adversarial tests to find gaps in coverage.
• The Auditor — An independent investigator that verifies the authenticity and robustness of the generated solutions.

This design ensures separation of concerns: each agent has a narrow role, reducing overlap and enabling parallel work. The Orchestrator and Explorer are pure planners; the Worker is execution-only; the Reviewer, Critic, and Auditor provide three distinct layers of validation.

Who This Is For

Developers building multi-agent systems for code generation, particularly teams working on OpenClaw’s subagent framework.