Support keyword: antigravity cli oauth
OAuth problems can come from the browser handoff, the selected Google account, token storage, WSL, or an MCP server's own auth flow.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
Antigravity CLI OAuth is broader than a WSL fix. The main CLI sign-in flow, a remote terminal browser handoff, and an MCP server OAuth flow can each fail for different reasons. If you treat all of them as the same problem, you can spend an hour repeating the wrong login step.
Start by identifying what is asking for authorization: the CLI itself, a Google account entitlement, or an MCP server. Then confirm which environment stores the resulting token.
| Symptom | Likely layer | First check |
|---|---|---|
| Browser does not open | Terminal handoff | Copy the printed authorization URL into your browser. |
| Wrong account keeps signing in | Google account selection | Use the account with Antigravity access and sign out of extras if needed. |
| Works locally but not in WSL | Token storage or distro mismatch | Check which user and WSL distribution ran the CLI. |
| MCP server asks for auth | MCP-specific OAuth | Inspect MCP config and token paths separately from CLI sign-in. |
| Looks like a quota problem | Account access or stale token | Confirm auth before assuming rate limits. |
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.
No. A stale token or wrong account can look like access failure, but it is not the same as a true quota limit.
The browser and the Linux environment may not share the same token storage or callback behavior.
It can. Google's MCP docs describe OAuth-related MCP configuration and token storage.