ACCOUNT ACCESS · ANTIGRAVITY TOOLS
Antigravity Manager: Fix Login & OAuth Errors
Start a fresh OAuth attempt for a failed browser return, and authorize the same account again when its refresh token is rejected. For verification or access messages, check that account in Google Antigravity first. After sign-in, confirm the saved email and repeat the task that failed.
For version 5.0.0 · Updated
Check which sign-in failed
This page covers Google account authorization. For a client rejected by Manager with a local 401 or 403, check its Manager credential and IP access rules. For storage_json_not_found after switching, use the IDE storage checks.
Keep the exact message, Manager version and any beta suffix. If Google reports an account restriction, compare the same account in the official Antigravity app. This tells you whether to follow Google’s access instructions or investigate the failing Manager step.
BROWSER RETURN
localhost refused to connect
Restart the sign-in attempt while Manager stays open on the computer that will receive the browser callback. For desktop sign-in, Manager prepares a temporary local address; use the link from the current attempt.
- Open Accounts → Add Account → OAuth and choose Start OAuth. Use Cancel first if an earlier attempt is still waiting.
- Finish Google sign-in in the browser. Keep the OAuth tab inside Manager’s Add Account dialog selected. Changing tabs in that dialog cancels the prepared attempt; you can switch browser tabs normally.
- Return to Accounts and check for the intended email. If you opened a copied authorization link and the dialog is idle after consent, choose I already authorized to finish.
If the local connection still fails, note the callback hostname and port and check the local network/proxy configuration. Keep the original settings so you can restore them after a comparison. Start a new attempt to change the callback address.
Recover with the callback URL or authorization code
Use this when Google has redirected to a URL containing code=, but the browser cannot reach Manager.
- Keep the current OAuth attempt open. On desktop, leave Start OAuth waiting; if you used Copy Auth Link without starting it, choose I already authorized to begin waiting before submitting the code.
- Copy the full callback URL from the browser address bar. Use the URL from this attempt and keep it private.
- Paste it into Paste callback URL or code... in the same dialog and choose Submit once.
- Check Accounts for the correct email. If it remains absent, follow the token-exchange checks below and inspect the error in Manager.
For No active OAuth flow found or OAuth state mismatch, cancel the abandoned attempt, start again and use the newly generated link. If the callback contains an error instead of a code, follow that error before retrying.
Manager runs in Docker or on another computer
The browser sends a localhost callback to its own computer. Use the Docker/server OAuth procedure to forward that connection to Manager, or use its manual callback procedure.
In the Web UI, choose Start OAuth before following the current link. If you see Popup blocked, allow the sign-in window for the Manager page or open its current authorization link yourself. After manual Submit, wait for processing and reopen Accounts to confirm the saved email. For a refused local callback containing code=, paste that URL back into the same Web UI dialog.
If Google shows redirect_uri_mismatch, keep the app-generated URL unchanged and check the callback setup for your deployment. Include the callback’s scheme, hostname, port and path in a report; remove its query string.
SAVE THE ACCOUNT
Token exchange fails or no refresh token is returned
Read Manager’s error after the browser returns. A network failure while contacting Google and a missing refresh token need different next steps.
Manager cannot contact the token service
Check the network and proxy settings used by the computer or container running Manager. The browser and Manager can use different network paths. Record the failing service hostname and the DNS, TLS, timeout or connection error, then use the connection checks.
After correcting the connection, cancel the old attempt and start OAuth again. If the browser shows a successful return but no account appears, look for the subsequent error in Manager’s logs.
Manager receives no refresh token
Start one fresh sign-in, select the intended Google account and complete the consent screen. If Manager again reports a missing refresh token and asks you to revoke access, review the matching app permission before authorizing again.
- Note the app name shown during consent. Open Google’s linked-app access instructions and inspect the matching entry.
- Remove that app’s access only when you intend to replace its authorization. This can interrupt other sessions sharing that authorization.
- Return to Manager, start a new OAuth attempt and complete consent. Confirm the email in Accounts and refresh its information.
If the same error persists, keep the account entry and collect the error from this fresh attempt. Finish by testing the original IDE or API task once the account information refreshes successfully.
REJECTED TOKEN
invalid_grant and a Disabled account
For an existing account, invalid_grant during token refresh means the saved authorization was rejected. Reauthorize the same Google account to replace the credentials.
- Check the account’s current status in Accounts and the corresponding log entry. Confirm that the error names
invalid_grant. - Use Add Account → OAuth → Start OAuth and select the same Google email. Manager updates the existing entry when that email matches.
- Check that the email is correct and the Disabled status clears. Version 5.0.0 clears this status when the saved access or refresh token changes.
- Use Refresh when available, then repeat the action that failed. If the account also shows Proxy Disabled, review its separate proxy availability setting.
Version 5.0.0 retries a refresh failure before its proxy disables the account. Use the current status and repeated error to decide what to repair. If fresh authorization still fails or the account stays disabled, keep its error and timestamp for a report.
invalid_grant while finishing a new sign-in
Start a fresh attempt and submit its code once, using the callback URL generated for that attempt. Google also uses this error for invalid or expired authorization codes and redirect mismatches; its OAuth error reference describes these cases. Use the callback procedure when the error occurs before an account is saved.
GOOGLE ANTIGRAVITY ACCESS
“This account is ineligible to use Antigravity”
Sign in with the same account in the official Antigravity product, then check the requirements in Google’s sign-in FAQ.
- Personal account: check that its associated country is supported and that the account meets the minimum age of 18. Follow Google’s age-verification path if needed.
- Work or school account: ask the administrator to confirm Antigravity access and which product supports the organization’s sign-in setup.
Use the access or support instructions shown by Google when direct sign-in is denied. Once direct access works, return to Manager and try a fresh authorization. If only Manager fails, report that comparison with the exact error and both application versions.
ACCOUNT VERIFICATION
Further Actions, verification required, or Google 403
Read the complete response and open the verification or appeal flow offered for your account. For a 403 generated by Manager’s own credentials or IP controls, use the connection and access checks.
- Check the same account in the official Antigravity product. If Manager provides a verification link, inspect its destination before opening it.
- Complete the method Google offers on that page. If the method is unavailable, use another option or the help/recovery link offered there.
- Return to Manager and use Refresh for the affected account when available. For a Disabled entry, follow the reauthorization steps. Check the new status, then retry the original task once.
Keep verification links, QR codes and account identifiers private. If the challenge repeats or the service denies access, retain the exact message and use its support or appeal route. For a 403 with no explanatory text, collect the matching request and log entry before changing account settings.
LOCATION MESSAGE
User location is not supported
Check the account’s associated country against Google’s availability list. If the recorded country is wrong, use the correction request linked from that FAQ.
Keep the affected model and full error, including FAILED_PRECONDITION when present. Try one short text-only request with the same model and connection settings. If the same location message returns, continue with service-access checks.
Compare the same account in the official product. Follow Google’s access guidance if it is also denied there; if direct access works but Manager still fails, include that difference and the model in a report.
PROJECT ACCESS
USER_PROJECT_DENIED / project not found
Check which Google account handled the failed request and whether it can use the official Antigravity product. Save the reason and service name from the error, keeping the project identifier private.
For an organization-managed account, ask the administrator to check its project and service access. If direct access works, authorize the same account again in Manager and repeat one small request. Manager requests the account’s project information during authorization.
If the error persists, stop repeating authorization and report the failed request with versions, the affected model and the direct-access result. Leave project and billing settings unchanged while the access problem is being identified.
When to stop retrying and report
Report the problem when a fresh attempt repeats the same error, or when the account works in the official product but fails through Manager. Include the failing stage, exact error, time and time zone, versions, and whether the email appeared in Accounts.
Use Cancel for an unfinished OAuth attempt and restore temporary network settings after testing. Keep account data while investigating. Remove authorization URLs, callback codes, tokens, keys, emails, QR codes and identifying paths from anything you share.