You try to sign in to Google Antigravity and get the message There was an unexpected issue setting up your account. Please try again later. This often follows an agent loop in Planning mode and clearing auth cache, after which login is blocked.

Antigravity login blocked after agent loop and cache clear

You were using Planning mode when the agent stalled and then stopped responding. Multiple retries showed We can’t process this right now. Start a new chat or try again. After starting a new chat and clearing Google auth caches, sign in now fails with There was an unexpected issue setting up your account. Please try again later. Users reported this can be triggered by transient backend issues and by IP or geo rate limiting. The incident was later acknowledged as a technical issue and resolved, but you can often fix it immediately by changing your network and forcing a clean reauth. If your agent also gets stuck loading rather than erroring, see our stuck loading agent guide for additional recovery steps.

Solution Overview

Aspect	Detail
Root Cause	Temporary backend outage combined with IP or geo based throttling and stale auth session data
Primary Fix	Change network to refresh your public IP then force a clean sign in session
Complexity	Easy
Estimated Time	5 to 15 minutes

Fix login lockout now

Step-by-Step Solution

1. Change your network to refresh your public IP This is the fastest working fix reported by affected users. Switch networks so Antigravity sees a new IP and region.

• Connect to another WiFi or tether to mobile data.
• Restart your router to obtain a new IP from your ISP.
• As a temporary workaround, try a reputable VPN endpoint near your location, then try sign in again.
• Verify your IP changed:

curl https://ifconfig.me

On macOS you can also renew the DHCP lease and flush DNS to clean up stale resolution.

networksetup -listallhardwareports
Identify your WiFi device name, for example en0

sudo ipconfig set en0 BOOTP
sudo ipconfig set en0 DHCP

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

2. Force a clean Google auth session for Antigravity Clear site data for Antigravity and Google Accounts so the next visit performs a fresh OAuth flow. Chrome steps:

• Open Chrome
• Visit chrome://settings/siteData
• Search for antigravity and remove stored data
• Search for accounts.google.com and remove cookies and storage
• Close all Chrome windows
• Reopen Chrome and try signing in again

Alternatively start an Incognito window or a brand new Chrome profile and sign in there. You can also revoke the app’s access so Google prompts a fresh grant:

• Visit the Google permissions page: Manage third party access
• Remove Antigravity or related entries
• Return to Antigravity and sign in to reauthorize

If your login errors mention Workspace or server errors, see our guide to debug 500 errors in Workspace which often surface during OAuth handshakes. 3. Confirm Google auth endpoints are reachable from your network Run these checks to rule out local blocking or TLS issues.

curl -I https://accounts.google.com
curl -I https://oauth2.googleapis.com/token
openssl s_client -connect accounts.google.com:443 -servername accounts.google.com -brief

You should see HTTP 200 or 3xx from curl and a successful TLS handshake from openssl. 4. Try again after the known incident window The issue was acknowledged as a technical problem and later resolved. If the above steps do not help, wait a short while then retry with a clean session. Outages can cause authentication setup to fail even with a good network. If you are working with Gemini models and see model selection errors during login or first run, review our notes on Gemini Pro errors in Antigravity that can block initialization.

Alternative Fixes and Workarounds

Use a different account temporarily If you have a second Google account, try signing in with it to finish urgent tasks. Later migrate back once the primary account succeeds. Disable corporate proxy or content filters Enterprise proxies and SSL inspection can block OAuth redirects. Test on a clean network without proxy. Try a different browser or a fresh profile Firefox or Safari with a clean profile often bypasses stale cookies or extensions that interfere with auth. Remove problematic extensions Disable privacy or ad blocking extensions that modify cookies or cross site requests, then retry.

Troubleshooting Tips

• Ensure system time and timezone are correct. Auth fails if clock skew is large.
• Check that third party cookies are allowed for accounts.google.com during sign in.
• Confirm no hosts file overrides for google domains.
• From Turkey or other restricted regions, test multiple ISPs or a mobile hotspot to avoid regional throttling.
• If you repeatedly hit the error, stop rapid retries for a few minutes to avoid rate limits.

Best Practices

• Keep a secondary browser profile for recovery logins.
• Avoid clearing tokens mid conversation if the agent is only slow. First try a page refresh or a new tab.
• Document the exact error and timestamp. If you need support, this helps teams correlate with backend logs.
• For team environments, track service status and plan for account level failsafe access.

Final Thought

In most cases this lockout is resolved by a simple network change followed by a clean sign in. If a backend incident is in play, the problem usually clears after a short wait, and the above steps ensure your session is ready to authenticate on the next attempt.