Antigravity Track
Module 38
Antigravity Track ā€” Module 38
Directing the Orchestra: ThreadCo's developer has four agents running. One finishes and surfaces a design question ā€” should the returns API accept partial returns or whole-order only? She answers in the Manager Surface, the agent continues. She never opens the file manually. She is directing, not coding.

The Manager Surface

The Manager Surface is Antigravity's control centre for multi-agent work. It is a dedicated panel ā€” separate from the code editor ā€” where you observe, steer, and review all running and completed agents.

Agent Timeline

Each agent has a live timeline showing every action taken: files read, files edited, terminal commands run, test results. You can replay any step to understand exactly what the agent did and why.

Steering & Clarification

When an agent hits ambiguity, it pauses and surfaces a question in the Manager Surface. You answer in plain text and the agent continues. You never need to re-run the whole task.

Diff Queue

Completed agents queue their diffs for your review. Accept, reject, or partially accept individual hunks. Accepted changes are applied to your working tree ā€” rejected changes are discarded without affecting your codebase.

Verifiable Artifacts

Agents generate artifacts alongside code: implementation plans, task breakdowns, screenshots of UI changes, and test reports. These live in the Manager Surface as a record of what was done and why.

Manager Surface ā€” Agent Awaiting Input

shopmate ā€” Antigravity ā€” Manager Surface
Agents
Agent 2 ā€” WAITING
Returns API
Agent 1 ā€” RUNNING
Checkout fix
Agent 3 ā€” DONE āœ“
Test fixes
Agent 2 ā€” Returns API WAITING FOR INPUT
Timeline
āœ“ Read api/checkout.py, schemas.py
āœ“ Created shopmate/returns.py
āœ“ Added ReturnRequest schema
? Paused ā€” design question
Agent needs clarification
Should POST /returns/initiate support partial returns (individual items from an order) or whole-order returns only? This affects the request schema and the order lookup logic.
Whole-order only for now. We can add item-level later. Send ā†’

Reviewing the Diff Queue

1

Agent completes ā†’ diff queued

When an agent finishes, its changes appear in the Diff Queue tab of the Manager Surface. Status changes from RUNNING to REVIEW.

2

Review file by file

The diff viewer shows each changed file with standard green/red highlighting. Click any file in the left panel to review it. Artifacts (test reports, screenshots) are shown in a separate tab alongside the diff.

3

Accept, reject, or partially accept

Accept the whole diff, reject it entirely, or use hunk-level selection to accept individual changes. You are not locked into all-or-nothing.

4

Changes applied to working tree

Accepted changes are written to your files immediately. Antigravity does not commit automatically ā€” you commit when you are ready, giving you full control over your git history.

← Multi-Agent Orchestration Next: Browser Integration →