Based on Google’s official docs, checked October 29, 2026

Google Antigravity on Windows: install, WSL, sandbox and fixes

Google Antigravity runs natively on Windows, both as the desktop app and as the agy command-line tool. A few things work differently than on macOS and Linux: the terminal sandbox needs a recent Windows 11 build, auto mode arrived later, permission rules match PowerShell commands more strictly, and you can point the app at a WSL distribution. This guide collects the Windows-specific steps from Google’s official docs and changelog, checked on October 29, 2026. For general agy usage, see the Antigravity CLI guide.

1. 1. Check your Windows version

   The Antigravity app supports Windows 10 (64-bit) and Windows 11, on x64 or ARM64. The terminal sandbox needs more: Windows 11 24H2 or later with the August 2026 update or later. Run winver to see your build.

   winver

2. 2. Install the desktop app

   Download the x64 or ARM64 .exe from antigravity.google/download, run it and follow the setup wizard. Then launch Antigravity and click Sign in to finish the browser sign-in.

3. 3. Install agy from PowerShell

   The CLI installs to C:\Users\<username>\AppData\Local\agy\bin. Open a new terminal afterwards and check it with agy --version. If you see agy is not recognized, add that folder to your user Path and restart the terminal.

   irm https://antigravity.google/cli/install.ps1 | iex

4. 4. Connect the app to WSL if your code lives there

   On Windows, Application Settings has a Windows Subsystem for Linux section. Pick an installed WSL distribution to work inside it, or switch back to your local Windows environment. While connected, the title bar shows the distribution name.

   wsl --list --verbose

5. 5. Turn on the terminal sandbox

   On a supported build, start agy with --sandbox or set enableTerminalSandbox in ~/.gemini/antigravity-cli/settings.json. On Windows, commands run in an AppContainer: your projects stay writable, folders outside your user profile are readable but not writable, and the rest of your profile stays hidden. Since v1.4.4, if the sandbox is not available these settings have no effect instead of failing.

   {
     "enableTerminalSandbox": true
   }

6. 6. Use auto mode (CLI v1.4.4 or later)

   auto mode needs the terminal sandbox, and on Windows it needs agy v1.4.4 or later (macOS and Linux got it in v1.3.5). Where it is not available, Shift+Tab skips straight from accept-edits to plan. It is not available for business or enterprise accounts.

   agy --mode=auto

Permission rules in PowerShell and CMD

Antigravity normalizes Windows paths before matching rules: it strips the drive letter and turns backslashes into forward slashes, so one path rule works on every OS.

Commands in PowerShell or Command Prompt that cannot be split cleanly into words need an exact match by default. To allow a command and its subcommands, use a regex rule.

command(regex:git .*)

Remote Control on Windows

agy remote-control registers its daemon as a Scheduled Task on Windows. Making it start at boot needs an Administrator PowerShell or Command Prompt. From a normal prompt, start still works, but the daemon only resumes after you log back in. status and stop work from a normal prompt.

agy remote-control status

Known Windows issues Google has fixed

Sandboxed commands failing with "Access is denied" when PowerShell 7 came from the Microsoft Store. The agent now falls back to Windows PowerShell, so update agy if you hit this.

Settings not loading after the file was saved in Notepad or with PowerShell Set-Content, which add a UTF-8 byte order mark. Update, or save the file as UTF-8 without BOM.

Git diffs failing for files in subfolders because of backslash paths, and recurring UAC prompts at startup. Both are fixed in current app releases.

Tips

• If the sandbox will not turn on, check winver first: anything older than Windows 11 24H2 with the August 2026 update cannot use it.
• Prefer WSL when your toolchain is Linux-first. The app connects to the distribution directly, so you do not need a second install inside it.
• Keep settings.json in UTF-8 without BOM if you edit it by hand on an older build.

Next steps

Sources

• https://antigravity.google/docs/getting-started/ · checked 2026-10-29
• https://antigravity.google/docs/sandbox/ · checked 2026-10-29
• https://antigravity.google/docs/cli/modes/ · checked 2026-10-29
• https://antigravity.google/docs/cli/reference/ · checked 2026-10-29
• https://antigravity.google/docs/permissions/ · checked 2026-10-29
• https://antigravity.google/docs/remote-control/ · checked 2026-10-29
• https://antigravity.google/docs/changelog/ · checked 2026-10-29