Antigravity Unable to Sign In: "Awaiting Authentication", Login Loop and "Unexpected Issue" Fixes

Updated October 30, 2026. Re-checked against the Antigravity FAQ, changelog, Google AI Developers Forum staff replies and the Gemini CLI issue tracker.

Antigravity sign-in fails in several different ways, and the fix depends on which message you see. If the message says your account is "ineligible" or "not eligible" (including the "Further action is required" and "Eligibility check failed" screens), that is an account decision rather than a login bug: use the Account Not Eligible guide. Everything else is below.

Find Your Exact Message

Quick Fix (Start Here)

Most sign-in problems on the desktop app respond to this order of steps. None of them are guaranteed, so move on to the section for your exact message if they do not help.

1. Update to the latest Antigravity release (Help, then Check for Updates, or reinstall from antigravity.google/download). Google staff answered several sign-in reports by asking users to update, and the changelog shows frequent releases (App v2.26.0 on October 22, 2026 was the latest entry when checked).
2. Fully quit Antigravity (Cmd+Q on Mac, File then Exit on Windows) and relaunch. Closing the window is not enough.
3. Sign out of every other Google account in your default browser, so only the account you want is active.
4. Click Sign in again and finish the flow in the browser that opens.

"Antigravity awaiting authentication" (Stuck, No Redirect)

What it means: after you click Continue with Google, the app shows this state while it waits for the browser sign-in to hand a result back. If nothing happens, either no browser opened, or the browser finished but the result never reached the app.

Causes reported on the forum: an older build with a sign-in bug (on a thread about version 2.8.1 on macOS, a Google staff reply said the latest build opened the browser and completed sign-in correctly and asked the user to update), a corrupted onboarding or cache state after an update, a default browser that is not set or not a normal browser, and security software or a proxy that blocks localhost callbacks. A separate Windows thread reports the same freeze; the user got past it by running Antigravity: Reset Onboarding and renaming the cache folders (see step 4).

Fix:

1. Update to the latest version, fully quit and relaunch (see Quick Fix).
2. Make sure a normal browser (Chrome, Edge, Firefox or Safari) is set as your system default. Users on macOS report the screen spinning forever with no browser tab opening, including one whose default browser was Firefox (thread 144283), so test with a mainstream browser as default.
3. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run Antigravity: Reset Onboarding, then try Continue with Google again.
4. If it still hangs, quit the app and rename (do not delete) the Antigravity data folders so the app recreates them. A user on Windows reported this cleared the freeze: %APPDATA%\Antigravity, %USERPROFILE%\.gemini\antigravity, %USERPROFILE%\.gemini\antigravity-ide and %USERPROFILE%\.gemini\antigravity-browser-profile. Google has not published an official folder list, and the same user then hit "unexpected issue" (next section), so treat this as a user-reported workaround.
5. Temporarily turn off any VPN, proxy or HTTPS-inspecting security tool while you sign in, then turn it back on after you are signed in. On a corporate network, see the proxy and firewall guide.
6. Try the CLI instead: run agy in a terminal. It prints a sign-in link you open in any browser and then asks for a code, which avoids the desktop redirect entirely. See the CLI sign-in steps.

Sources: forum threads 178878 (includes the staff reply), 172137 and 144283.

Browser Says "You Have Successfully Authenticated" but the App Stays Signed Out

What it means: Google accepted the sign-in, but the redirect to the app's local callback did not complete. A user on macOS saw the localhost page say "Bad Request: Missing code or state parameters" and logs showing a "state syncing error", which is the app failing to match the callback to its own sign-in request.

Fix:

1. Sign out of all Google accounts in the browser, clear cookies for accounts.google.com, and try again with one account.
2. Revoke Antigravity at myaccount.google.com/connections, then sign in fresh.
3. Finish sign-in once, in the first browser tab that opens. Starting a second sign-in while the first is open makes the callback state mismatch.
4. Behind a corporate proxy, launch the app with your proxy variables set (macOS example below) so the OAuth call can leave your network.
5. If you moved the install to a custom drive or path and the app does not register as the handler, reinstall to the default location. This is a user-reported workaround, not an official requirement.

"There was an unexpected issue setting up your account"

What it means: sign-in itself worked, but the follow-up setup call failed. It is a generic message, and the sub-message under it matters. Forum reports show these variants:

• "context deadline exceeded" (timeout): seen right after resetting the app cache on Windows (thread 172137).
• "Failed to fetch": seen after a long "Awaiting Authentication" hang on macOS (thread 178878), resolved for that user by updating.
• No sub-message, and it happens only on one account: can be a Terms of Service flag on that account (see Terms of Service Flag).

Fix:

1. Update to the latest version, quit fully, relaunch, and sign in again.
2. Run Antigravity: Reset Onboarding from the Command Palette and sign in again.
3. Revoke Antigravity at myaccount.google.com/connections and sign in again with a single account in the browser.
4. Turn off proxy and VPN software for the attempt and make sure your network can reach Google sign-in. A "context deadline exceeded" or "Failed to fetch" sub-message suggests a timeout between the app and Google's servers rather than a problem with your account, though Google has not documented this.
5. Test the same account in agy (CLI). If it returns a specific eligibility message, follow the Account Not Eligible guide. If the CLI signs in fine, the problem is the desktop app, not your account.
6. If only this account fails everywhere and you have used it with third-party tools, go to Terms of Service Flag.

"Failed to sign in. Message: This client is no longer supported for Gemini Code Assist for individuals"

What it means: you are using Gemini CLI (or the Gemini Code Assist extension) with a personal Google login, and that route has been shut off. Reports in the Gemini CLI repo (issue 28229) show this error on Google AI Pro accounts even after clean reinstalls, and the maintainers' replies point to Antigravity CLI. Google's deprecation page for Gemini Code Assist for individuals is the official source; check it for the current dates. Third-party tests dated October 2026 report the personal-account cutoff was June 18, 2026 and that it covers free, Google AI Pro and Google AI Ultra personal logins, while paid Gemini API keys and existing Gemini Code Assist Standard or Enterprise licenses were outside that cutoff.

Cause: a server-side policy, not a bug on your machine. In the Gemini CLI issues the same text also appears with the code UNSUPPORTED_CLIENT. Reinstalling Gemini CLI, deleting ~/.gemini or trying another personal account does not change it.

Fix (pick one):

1. Move to Antigravity CLI: install it from antigravity.google/download. The installer command reported in third-party tests is curl -fsSL https://antigravity.google/cli/install.sh | bash on macOS and Linux and irm https://antigravity.google/cli/install.ps1 | iex in Windows PowerShell; check the download page for the current command before running a pipe-to-shell installer.
2. Run agy, open the sign-in URL it prints, choose your personal account, copy the authorization code the browser shows, and paste it back into the terminal. One tester reported the code prompt times out after about 60 seconds, so have the browser ready; if it expires, start again and use the new link.
3. Check it works with agy -p "Reply with the single word OK".
4. Remove the old CLI if you only used it with a personal login: npm uninstall -g @google/gemini-cli. Do not delete the whole ~/.gemini folder, because Antigravity CLI also stores data under it.
5. Or keep Gemini CLI with a paid Gemini API key: run /auth inside Gemini CLI and choose the API key option, and set GEMINI_API_KEY in your environment. A previously saved Google login can keep being used until you switch the auth type.

For the full walkthrough see Gemini CLI to Antigravity CLI migration. If agy then shows "Eligibility check failed", that is a different problem: see Eligibility check failed.

"Authentication Required" While Already Signed In

What it means: a cached session went bad mid-work. The agent panel asks you to sign in, sometimes with no button. Because Antigravity's App, IDE and agy CLI share one backend, a stale session on one surface can leave the others in a bad state.

Fix:

1. Open Settings, then Account, and click Sign Out. If there is no button, run Antigravity: Reset Onboarding from the Command Palette.
2. In agy, run /logout to disconnect the account and clear its saved profile.
3. Fully quit and relaunch, then sign in with one account.
4. If the app will not respond at all, end the Antigravity process (Task Manager on Windows, Activity Monitor on macOS, pkill -f antigravity on Linux) and relaunch.

If the same screen reports an eligibility problem rather than a sign-in problem, clearing tokens will not help; use the Account Not Eligible guide. If quota looks wrong after this bug, see the quota guide.

Eligibility Messages (Handled in a Separate Guide)

These messages mean your account was checked and refused or needs verification. Each has its own cause and steps in the Account Not Eligible guide:

• "Sorry, this account is ineligible to use Antigravity" / "Your current account is not eligible for Antigravity, because it is not currently available in your location": country association, age or account type.
• "Eligibility check failed: your current account is not eligible for Antigravity. Verify your account to continue." (CLI).
• "Further action is required to use Antigravity" / "Please verify your account to continue using Antigravity".
• "This account isn't eligible for Google Antigravity benefits included with Google AI plans".

Terms of Service Flag (Third-Party Tools)

If a working account suddenly cannot set up and you have connected Antigravity sign-in to third-party tools, the cause may be a Terms of Service action. The Antigravity Additional Terms prohibit using the Service in connection with products not provided by Google, and give the example of OpenClaw with Antigravity OAuth, which may lead to suspension or termination of Antigravity and/or Gemini CLI accounts. The FAQ says to use a Gemini Enterprise or API key for third-party coding agents.

Google's post in gemini-cli discussion 20632 (February 27, 2026) describes the recovery path: flagged accounts get an email and an error pointing to a Google Form where you recertify that you will follow the terms; a second violation leads to a permanent ban. Steps:

1. Stop using the third-party tool and remove its access at myaccount.google.com/connections.
2. Look for the email or in-app message from Google and use the form it links to. Do not reconnect the tool.
3. If there is no message, ask on the Antigravity forum. Outcomes for reported bans are inconsistent and Google publishes no timeline.

The full section is in the Account Not Eligible guide. This page does not cover ways around the terms or region availability.

Prevent Future Login Issues

• Sign in with one personal Google Account, and keep other accounts signed out of the browser during sign-in.
• Do not connect Antigravity sign-in to third-party tools. The FAQ and Terms say this can lead to suspension.
• Keep Antigravity updated. Several sign-in reports were answered by an update.
• Bookmark myaccount.google.com/connections: revoking and re-granting access is the fastest reset when sign-in state is corrupted.
• If you used Gemini CLI with a personal login, move to Antigravity CLI instead of retrying the old login.

Earlier Guidance (March 2026)

This section keeps the guidance from earlier versions of this page so nothing is lost. Where an item is outdated or unverified, a dated note says so. For the current steps, use the sections above.

Identify Your Login Issue

Earlier versions grouped login problems into five types, each with a different fix:

• Authentication Loop: the browser says "Successfully Authenticated" but the IDE never receives the redirect and you are stuck in a sign-in cycle. See the current fix.
• "Authentication Required" while signed in: you were already working, and the agent panel suddenly shows "Authentication Required" with no login button. See the current fix.
• "Account not eligible": you can sign in, but are told your account isn't eligible for Antigravity. See Eligibility Messages.
• Account banned / suspended: you can't sign in at all and see "There was an unexpected issue" or your account is "on hold". See Terms of Service Flag.
• "There was an unexpected issue setting up your account": an earlier version said this newer message (v1.20.5 and later) appears when your Google account has been flagged, often because of third-party OAuth tools such as OpenClaw. See the current fix.

Quick Fix (90 Seconds)

Before trying anything else, earlier versions said this resolves the majority of login issues:

1. Fully quit Antigravity. Use Cmd+Q (Mac) or File → Exit (Windows), not just closing the window.
2. Switch your default browser. If you are using Chrome, switch to Edge or Firefox (or vice versa). An earlier version claimed this resolves about 70% of authentication loops caused by browser cache, cookies or session conflicts.
3. Reopen Antigravity and sign in again.

If this didn't work, continue to the specific fix for your issue.

Fix the Authentication Loop

Symptom: the browser shows "You have successfully authenticated. You should be redirected back to the product" but the desktop app stays on the Sign In screen.

An earlier version called this the most common variant, confirmed by 5+ users on the Google AI Forum. The OAuth redirect from browser back to the desktop app fails silently. The current steps are in the section above; the four earlier fixes follow.

Fix 1: Install on C: drive with Chrome as default (Windows)

An earlier version said this specific combination resolves about 70% of login loops on Windows (community-reported, March 2026):

1. Uninstall Antigravity completely.
2. Set Chrome as your default browser in Windows Settings.
3. Reinstall Antigravity to C:\Program Files\Google Antigravity (not a custom path).
4. Sign in again.

This is a user-reported workaround, not an official requirement.

Fix 2: Set proxy variables (macOS / corporate networks)

If you are behind a corporate firewall or VPN, the OAuth redirect may be blocked. Launch Antigravity from Terminal with proxy variables:

This was reported as a working fix on the Google AI Forum for users behind corporate firewalls.

Fix 3: Clear all auth data

1. Sign out of ALL Google accounts in your browser.
2. Clear cookies for accounts.google.com and antigravity.google.
3. Revoke Antigravity's access to your Google account at myaccount.google.com/connections.
4. Restart Antigravity and sign in fresh with a single Google account.

Fix 4: Disable VPN temporarily

Fix "Authentication Required" While Signed In

Symptom: you were actively coding, and the agent panel suddenly shows "Authentication Required: Please sign in" even though you are already signed in. Sometimes there is no login button at all.

Solution

1. Go to File → Preferences → Antigravity Settings → Account.
2. Click Sign Out.
3. Fully close Antigravity (Cmd+Q or File → Exit).
4. Reopen and sign in again.

If the Sign Out option is missing, earlier versions said to kill Antigravity from Task Manager (Windows) or Activity Monitor (Mac), delete the auth cache, and reinstall:

Fix "Account Not Eligible"

Symptom: "Your current account is not eligible for Antigravity. Try signing in with another personal Google account."

Earlier versions said this is usually caused by one of three things:

• Using a Google Workspace account instead of a personal @gmail.com. An earlier version said Antigravity requires a personal account.
• Region restriction: your Google Account's country isn't in the supported list.
• Age verification required: Google may require ID-based age verification before granting access.

We have a complete, dedicated guide for this error: Fix: Account Not Eligible for Antigravity.

Account Banned / Suspended

Symptom: "There was an unexpected issue" on sign-in, your account is "on hold" with no further options, or you see "There was an unexpected issue setting up your account" when Antigravity first launches after an update to v1.20.5 or later.

Earlier versions said account bans were reported by developers who:

• Used OpenClaw or similar third-party OAuth tools. Google's Terms prohibit using the Service with products not provided by Google. See the OpenClaw section below and Terms of Service Flag.
• Logged in from multiple devices. One developer reported being banned for using 3 PCs sequentially (not simultaneously), suggesting Google's bot incorrectly flagged normal multi-device usage. This is a single community report (March 2026), not confirmed by Google.
• Used third-party quota extensions that authenticated with Google OAuth. Some of these extensions were reported as security risks.

What to do

1. Revoke all third-party access at myaccount.google.com/connections. Remove anything related to Antigravity, OpenClaw, or quota monitors.
2. Contact Google support through the AI Pro/Ultra subscription support channel. Reference your subscription and explain the situation.
3. Wait 24 to 72 hours. Some bans were reported as temporary and resolved once the flagged activity stopped (community-reported).

OpenClaw Permanent Bans (March 2026)

Symptom: after connecting Antigravity or Gemini via OpenClaw's OAuth flow, you see "There was an unexpected issue setting up your account" and can no longer sign in at all.

Community reports from March 2026 said Google began issuing permanent account bans to users who connected Antigravity or Gemini API access through OpenClaw using OAuth tokens, across all subscription tiers, including Ultra subscribers (reports quoted $250 per month; check Google's plans page for current pricing). Reports said no refunds were issued and no advance warnings were sent. Affected users reported that Gmail and Google Drive continued to work normally while Antigravity access was revoked, and that the ban was tied to the Google account, not the device. Google has not confirmed these details.

If your Antigravity access was revoked after using OpenClaw, earlier versions advised:

1. Revoke OpenClaw's OAuth access at myaccount.google.com/connections and remove all OpenClaw entries.
2. Do not attempt to reconnect OpenClaw via any OAuth flow. Reports said repeated connections could accelerate permanent status.
3. Contact Google AI support referencing your Ultra or Pro subscription. Cite the date of the ban and your subscription payment history. Some users on annual Ultra plans reported having bans reviewed, though outcomes were inconsistent.
4. If there is no resolution in 72 hours, earlier versions suggested creating a new personal Google account and a fresh subscription, noting that your existing subscription would likely not transfer.

For context on whether your account qualifies for reinstatement, see our guide: Fix: Account Not Eligible for Antigravity.

Linux-Specific Login Issues

Linux users reported additional auth problems because of how the OAuth callback is handled:

• Keyring issues: if you are using a headless or minimal desktop environment, the system keyring may not be available. Install gnome-keyring or libsecret to store OAuth tokens.
• Agent panel stuck with no login button: reported on Ubuntu 20.04, where the "Authentication Required" message appears but there is no way to trigger the login flow. The earlier fix was to clear the session storage and restart:

These paths are community-reported and not documented by Google. Confirm the folders exist and consider renaming instead of deleting.

If you are also seeing "This version is no longer supported," see our version update fix guide. The login error may be secondary to an outdated version.

Considering Alternatives?

If login issues are a recurring problem, explore other options that don't require Google authentication: Best Alternatives 2026 and Cursor vs Antigravity.

Sources (checked October 30, 2026)

• Antigravity FAQ: personal vs. Workspace accounts, availability, third-party software.
• Antigravity Additional Terms and changelog.
• Gemini Code Assist for individuals deprecation page; gemini-cli issue 28229; issue 28846.
• Google AI Developers Forum threads 172137, 144283 and 178878 (links above), and discussion 20632.
• Third-party migration tests: jwatte.com and getdmn.com (installer commands, June 18 date, API key route).