Antigravity not working? Fixes for agent errors, sign-in and more

When Antigravity is not working, update to the latest build first (the changelog lists App v2.28.0 on 27 October 2026 and Antigravity CLI v1.4.0 on 16 October), restart, and match your error below. Google publishes no single fix for the generic "Agent execution terminated due to error"; its own docs and changelog point to quota and credits running out, sign-in and account eligibility, network or certificate problems, and broken MCP servers.

This guide uses Google's Antigravity FAQ, CLI troubleshooting page, authentication docs and changelog, checked on 28 October 2026. Fixes that come only from forum users are labeled as community reports. Quota errors and 429s have their own page: Antigravity rate limits.

What should you try first when Antigravity isn't working?

Three quick checks clear many problems:

1. Update. Compare your App version with the changelog and install the latest build if you're behind; for the CLI, run agy --version to see your build.
2. Check your quota. Open View Usage in the App's model selector or run /usage in the CLI. An empty quota can surface as a generic error.
3. Sign out and back in. Google's App changelog shows a run of sign-in fixes through October 2026, so stale sessions are a common cause.

How do you fix "Agent execution terminated due to error"?

The message means the agent stopped without a more specific error to show. Work through the causes Google documents:

1. Quota or AI credits ran out. Google's changelog for Antigravity CLI v1.2.15 (2 October 2026) says that when your plan quota was used up and your AI credits couldn't cover a request, the CLI used to retry for about two and a half minutes and then show the generic agent-terminated message. It now says "Your AI credits balance is too low to continue." instead. Check your remaining quota with /usage in the CLI or View Usage in the App's model selector, and see the rate limits guide.

2. An old build. App v2.15.0 (18 September 2026) "Fixed an issue where an error that arrived without any tool activity in the turn was dropped," and App v2.3.0 added automatic retries on backend overload errors. Updating gets you clearer errors and fewer silent stops.

3. Business sign-in setup. If you sign in with a Google Cloud project, the authentication docs say the Gemini Enterprise API (aiplatform.googleapis.com) must be enabled in that project.

4. Network and certificate interception (forum report). In a September 2026 Google AI Developers Forum thread, a responder traced one case to tls: failed to verify certificate: x509: certificate signed by unknown authority, caused when "a corporate network proxy, VPN or anti-virus SSL inspection tool intercepts network traffic." The suggested fixes were installing your network's CA certificate in the system trust store or having the proxy skip SSL inspection for *.googleapis.com. The responder is marked as forum staff, but a forum reply isn't official documentation, so treat it as a community fix.

5. Other community reports. Forum users have reported that the error went away after downgrading, after switching to a Google Cloud project for sign-in. None of these is an official fix.

If it keeps happening, report it with your trajectory ID (see the last section).

Why won't Antigravity let you sign in or finish account setup?

Personal accounts. Google's FAQ says that if sign-in fails, check that your country is supported, that you're 18 or older, and that you aren't using a work or school account, which counts as an enterprise account.

Work and school accounts. Google Workspace and Gemini Enterprise accounts must be enabled by your organization first. A Workspace admin has to provision Antigravity for your account. With a Gemini Enterprise license, you pick Business account at sign-in, and your Google Cloud admin must assign you the license or the required IAM role. The FAQ notes enterprise sign-in works in the Antigravity App, CLI and IDE extensions, but not in the standalone Antigravity IDE. AI developer tools may also be off by default in Gemini Enterprise until an admin turns them on for your region.

Sign-in that worked before. Recent App releases fixed several sign-in bugs, so update first:

• v2.16.0 fixed browser sign-in failing permanently if the app reloaded or the computer slept mid-sign-in.
• v2.18.1 fixed Google Sign-In failing with a browser security error.
• v2.24.0 added an Authentication expired notice with a Log back in button.
• v2.28.0 fixed some enterprise accounts on macOS and Windows not staying signed in after a restart.

Antigravity CLI over SSH. The CLI can't open a browser, so it prints a URL. Open it on your own machine, sign in, and paste the code back into the terminal. The Antigravity CLI guide covers API key and Application Default Credentials sign-in too.

Error: failed to retrieve token: secret keyring is locked. The CLI keeps tokens in your OS keychain. On macOS, open Keychain Access, find the Antigravity CLI item and check agy is allowed under Access Control; over SSH, unlock the keychain with security unlock-keychain ~/Library/Keychains/login.keychain-db. On Linux, unlock GNOME Keyring or KWallet, and in headless sessions make sure a D-Bus session is running, for example with export $(dbus-launch).

What do "verification required" and "location not supported" mean?

Verify your account to continue. Your Google account needs an identity check or has a Terms of Service block to appeal. The CLI v1.3.1 changelog (7 October 2026) says the verification or appeal link now always appears with this message, and the CLI "no longer suggests logging out and back in when that would not help." Follow the link instead of reinstalling.

Age. Antigravity isn't available to users under 18. If you meet the requirement but are blocked, the FAQ says you can verify your age through your Google account.

Location. Antigravity is available in many countries and territories, but your account's country is what counts. The FAQ says to check the country on your Google Terms of Service page and, if it's wrong, submit a request to change your associated region. Google One AI plans are unavailable in some regions, including Türkiye, Sudan and South Sudan, so a paid plan may not be an option there.

Account suspensions. The FAQ warns that using third-party tools such as Claude Code, OpenClaw or OpenCode with your Antigravity login violates the Terms of Service and can lead to suspension. If a third-party wrapper was signed in with your account, that may be the reason for a block.

Why won't Antigravity open on Linux or Mac?

Check the requirements. Google's getting started page lists macOS 12 (Monterey) or later, Windows 10 or 11 (64-bit), and on Linux "glibc >= 2.28, glibcxx >= 3.4.25 (Ubuntu 20+, Debian 10+, Fedora 36+, RHEL 8+)". On Linux you extract the tar.gz archive and launch the Antigravity binary; when upgrading on macOS, choose Replace when you drag it into Applications.

Known startup bugs fixed in the App:

• v2.3.1: an empty or malformed config.json in ~/.gemini/config/ stopped the app loading.
• v2.0.11: certain antivirus products caused a dark blank screen at startup.
• v2.8.0: the header and top menu bar failed to display on Linux.
• v2.11.0: network or DNS timeouts at startup caused permanent account failure screens.

agy: command not found. The CLI installs to ~/.local/bin on macOS and Linux. Add it to your PATH in ~/.zshrc or ~/.bashrc, then reload the file. On Windows, the default location is C:\Users\<username>\AppData\Local\agy\bin.

CLI hangs on update. A crashed updater can leave a lock behind. Google's fix:

rm -f ~/.gemini/antigravity-cli/updater/update.lock

To stop auto-updates, add export AGY_CLI_DISABLE_AUTO_UPDATE=true to your shell profile.

What if an MCP server or extension breaks the agent?

Turn MCP servers off one at a time to find the culprit. Google's MCP docs give the controls:

• App: Settings > Customizations > Installed MCP Servers, then use each server's toggle.
• CLI: type /mcp to open the MCP manager and view connection logs, or set "disabled": true for a server in the config file.
• Config files: global servers live in ~/.gemini/config/mcp_config.json, and workspace servers in <workspace>/.agents/mcp_config.json.

Common MCP errors from the docs:

• MCP tool call to server "..." timed out after 3m0s. Default timeouts are 300 seconds to connect and list tools and 180 seconds per tool call. Raise timeoutSeconds for that server.
• Remote server won't connect. Remote servers must use Streamable HTTP; the legacy HTTP+SSE transport and the httpUrl field aren't supported.
• Server stopped after a restart. App v2.23.0 fixed restarting an MCP server leaving it stopped.

Hooks can end sessions too on older builds: App v2.12.0 changed it so "A failing custom hook no longer ends the session; it is now reported as an error and the conversation continues."

How do you report a bug with your trajectory ID?

1. In the App, open Settings and use Feedback, which sends "reports directly to the team." App v2.15.0 fixed feedback failing when large diagnostic logs were attached, so update first if sending fails.
2. On the forum, post in the Antigravity area of the Google AI Developers Forum. In the forum thread linked above, the responder first asked for the operating system, Antigravity version and the trajectory ID of the failing conversation, so include all three.
3. Include the exact error text and any error ID shown under the message.

While you troubleshoot, keep your rules, prompts and skills somewhere you can reinstall from. Kipt keeps prompts and Agent Skills as Markdown in a private GitHub repo you own, so a reinstall or a switch to another agent doesn't cost you your setup. The Antigravity guide explains how Antigravity loads skills.