antigravity-cli

Context burn is reduced by delegating large multi-file refactors to Antigravity CLI running as an isolated subagent. This offloads long-horizon repository execution into a dedicated session, preserving the main thread's context and reducing token cost.

Context handoff discipline requires providing the isolated session with the original goal, prior decisions, scope, and constraints. This explicit shared-state handoff ensures the delegated subagent stays aligned with the orchestrator's intent throughout the task.

Run a security audit across multiple files by offloading the task to a specialist subagent like @gemini-cli-security. This executes the deep security pass in an isolated context, returning only the final results to the orchestrator.

Yes, you can use prompt steering to match subtasks to specialist subagents such as @codebase_investigator, @generalist, and @code-review. This ensures complex code work is handled by the most suitable isolated context.

No, delegating web research and documentation sweeps requires programmatic, non-interactive execution. The subagent runs a single long-horizon prompt in headless mode with a mandatory verification step and controlled output format.

The limitation of using isolated subagents is the strict requirement for explicit shared-state handoff. Without passing the full goal, prior decisions, scope, constraints, and verification commands, the isolated session may drift from the orchestrator's intent.