Skip to main content

Antigravity Setup Guide

Antigravity Setup Guide

guide

Free

Antigravity Setup Guide

This browser will not display the PDF inline. Open the PDF.

Explore a practice codebase before asking an agent to change it.

BEGINNER / GOOGLE DEVELOPMENT TOOL

1. Set the stage

Use the official desktop installer and a small Git project. Start with one workspace and inspect the agent's access settings.

1. Install the official app

Open antigravity.google/download, choose the correct operating system and processor, and run the installer. Launch the app.

2. Sign in & open a workspace

Complete the supported sign-in flow. Open a practice repository rather than a production checkout. Confirm the displayed working folder.

3. Review agent settings

Inspect terminal, browser, and file-action permissions. Choose a review-oriented starting configuration before granting wider access.

4. Run & inspect a first task

Ask it to explain the project without edits. Then request a small change on a branch, run the relevant check, and review the diff.

2. Lean working stack

| Stage | Role | | --- | --- | | Antigravity | Inspect & edit | | Git | Create checkpoints | | Local preview | Exercise the change | | Human review | Approve the diff |

Arrows in the visual sheet show the order of work. External connections require separate setup. Optional tools may be replaced with ones you already use. This is a suggested stack for this task, not a universal optimum.

State the finish line

Define the expected behavior and the test that demonstrates it. Ask for actual results rather than a statement that a listener exists.

Keep extensions minimal

Install only what the project needs. Add tool connections after the core workflow works and their access is understood.

3. First practice task

Inspect this practice repository without changing it. Confirm the folder and branch, explain its entry point, and propose one small UI improvement with a specific way to verify it.

Your setup is working when

The agent identifies the intended repository, the proposed change is bounded, and any later edit is visible in Git and tested in a preview.

Troubleshooting

Wrong folder? Reopen the workspace. Tool blocked? Review the stated permission. Failed check? Diagnose it rather than disabling it.

Series 12 / 40

Back to Quill UniversityDownload MDDownload PDFDownload PNG