Independent guide. Not affiliated with, endorsed by or sponsored by Google LLC.
Official Antigravity site Official documentationNot case studies and not testimonials — we have no way to verify either. These are the workflows the product's own design points at, with the judgement call each one asks of you.
Open the project in Editor view, describe the wrong behaviour and the expected behaviour, and let the agent produce a plan first. Read the plan. If it has understood the bug, the change is usually uninteresting; if it has not, you have found out before any code moved.
The plan is the artifact that matters here. Everything downstream inherits its misunderstandings.
Describe the change, then let the agent apply it and drive the browser against the affected screens. You get the change and a recording of it being exercised in the same run.
Watch the recording at the point the agent decides it is done — that is where an unexercised edge case shows up.
Use New Worktree Mode so nothing lands in your working tree. Describe the end state rather than the mechanics, and expect the task list to be the thing you review rather than the diff.
Large mechanical changes are where the five-hour meter bites. Start one early in a window, not at the end of it.
Manager view, one workspace per task, and tasks chosen so they cannot touch the same files. Come back to a set of artifacts rather than a set of half-finished branches.
The discipline is in the choosing. Two agents in the same module is how you spend an afternoon on a merge.
Ask for a walkthrough before asking for a change. The knowledge base accumulates what the agent establishes, so the orientation work is not wasted on the next task.
Verify a few claims in the walkthrough by hand. An agent's confident tour of unfamiliar code is exactly where you have no baseline.
Anything behind a login you cannot rotate, touching production data, or where the cost of a plausible-but-wrong change is high. The tool is capable enough that the judgement call is now yours rather than the tool's.
This entry exists because a showcase page with no negative case is a brochure.
Have a workflow that worked, or one that went badly? Write to us. We publish what we can attribute and check.