Support keyword: antigravity cli wsl oauth fix
When auth fails in WSL or SSH, the problem is often the browser handoff, account selection, or token storage, not the install command itself.
Updated on 2026-05-26. Independent guide. Use official Google links for downloads and account actions.
WSL, SSH, containers, and headless servers often cannot open the same browser session as a local desktop terminal. The CLI may print an authorization URL or code flow instead of opening a browser automatically. If you miss that URL, choose the wrong Google account, or run the flow in the wrong environment, the CLI can look "logged out" even after installation succeeded.
Do not type your Google password into the terminal or a third-party page. Use the official browser authorization flow shown by the CLI and verify the domain before approving access.
| Check | Why |
|---|---|
| Same Linux user | Tokens can be stored under the user account that completed the flow. |
| Correct WSL distro | Ubuntu, Debian, and other distros have separate homes and config files. |
| Clock/time sync | OAuth flows can fail when system time is very wrong. |
| Corporate browser policy | Enterprise accounts can block or restrict app authorization. |
| MCP OAuth separately | MCP servers can have their own OAuth token file and auth provider. |
When the CLI keeps asking you to sign in, stop and capture the environment instead of approving the same browser prompt again and again. Note whether you are in native Windows, WSL, SSH, a dev container, or a remote VM. Then note which browser handled the OAuth approval and which Linux user ran the CLI. In WSL, two terminals can look similar while using different distributions or home directories.
If the account works in one environment but not another, the likely problem is local token storage or browser handoff. If the account fails everywhere, the likely problem is entitlement, plan access, or an organization policy. This distinction helps you decide whether to fix the shell, inspect tokens, or check official account settings before reinstalling the CLI.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
WSL often needs a browser authorization URL or code flow because it cannot always open the desktop browser directly.
No. Use the official browser authorization flow only.
Not always. MCP servers can have separate OAuth token storage and auth provider settings.