HELP · ANTIGRAVITY TOOLS

Antigravity Manager Troubleshooting

Choose the first step that fails: opening Manager, signing in, switching accounts, connecting a client or getting a response. Each symptom below gives you an initial check and a guide for the next step.

For version 5.0.0 · Updated

What stopped working?

Pick the closest symptom. If you have an error code, keep the full message beside it so you can choose the matching check.

Before you change settings

Copy the exact error and note your Manager version. Change one setting at a time, keeping its previous value so you can undo the change.

Back up your data before updating or replacing a profile. Keep existing account files and conversations while you investigate. If there is no error message, write down the last action that worked and what happened next.

Prepare a report if the cause is still unclear →

Start with one useful check

Use the check for your symptom, then follow the linked guide. Keep the same model and client settings when comparing a working request with a failing one.

App will not open

Match the downloaded installer to your operating system and CPU, then follow the steps for the exact launch error. The download page lists the available packages.

For a macOS “damaged” message, start with the macOS installation checks. For a blank window, crash or missing dependency, keep the installer filename and OS message and use the startup troubleshooting steps.

Check installation and first launch →

Cannot sign in

Find where sign-in stops: the Google page, the return to Manager, or the token exchange. A refused localhost callback goes to the OAuth callback checks; a token-exchange error goes to the token exchange guide.

For an eligibility or verification message, try the same account in the official Antigravity app. If that also fails, follow the account-service message. If direct sign-in works, note which Manager step fails. For a remote installation, check the Docker OAuth setup.

Find your sign-in error →

Account did not switch

Check the account shown inside the IDE or CLI you intended to switch. In Manager, confirm that you selected the matching client and local profile.

For storage_json_not_found, check the target profile and storage path before editing files. If Manager’s own account list became empty after a move or restart, check the active data directory. Preserve the IDE’s profile before investigating missing conversations.

Check account switching and the active session →

Client cannot connect

Check that API Proxy is running, then compare the client’s host, port, base URL and credential with its connection instructions. For a client on another device or in another container, use an address that reaches the Manager host.

Once the connection works, send one small model request. Use the returned message to choose the next check below.

Work through connection, key and URL checks →

429, 503, or no available accounts

Wait for any retry delay shown and pause repeated client retries. Read the full message to see whether it describes a rate limit, model capacity or Manager’s available accounts.

If only one model fails, check its account access and routing. If every request fails, also confirm that API Proxy is running and inspect the shared error.

Check 429, 503 and account availability →

400 or a rejected request

Match the error text to the checks below. Messages about account access, an image URI and a tool schema require different follow-up steps.

Choose a guide by the message returned
Message containsWhat to check next
USER_PROJECT_DENIED or project not foundRecord the account and project error from the failed request, then follow the project access checks.
User location is not supportedCheck the account-service message and the affected model through the location and eligibility guide.
Unsupported file URICheck how the image or file is supplied and whether the service receiving it can access it. Follow the media input checks.
thought_signature or an invalid/missing signatureCompare the selected model family and conversation history using the thinking and signature checks.
Field required or an invalid tool schemaCompare the tool definition and returned result with the tool request checks.

For an unknown or unsupported model, check the model ID your gateway exposes. If the message is still unclear, try one short text-only request with the same model and connection settings. If it works, add the failing image, tool or history back one change at a time; if it fails too, keep that smaller reproduction for your report.

Response stops or tools fail

Save the failing conversation, then try the same model in a fresh, short chat. Note whether the failure occurs before any text arrives, during the answer, after a tool result or on the next turn.

Use the stream interruption checks for Stream interrupted before completion. For a missing signature, use the thinking and signature checks. For incomplete tool calls or a file that stayed unchanged, use the tool and result checks. When a client says it edited a file, open the file and inspect the actual change.

A reply can contain an error even with HTTP 200. Keep the returned text and the last completed action when collecting the matching log entry.

Check streaming, thinking and tool results →

Version no longer supported

Record the full message and the versions of Manager, Antigravity IDE and your API client. Identify which application displays or returns the error, then check unsupported-version guidance.

Before changing versions, save and check a backup. Compare the release notes with your exact symptom and keep any beta suffix in your notes. After the change, repeat the same small task and inspect the result. Use the rollback instructions if you need to restore the previous version and its matching data.

Review updates and compatibility →

Still stuck?

Search the project’s issues for the exact error and your version. If the checks above leave the cause unclear, use the bug report template to describe the smallest task that reproduces the failure.

  • What happened: the action, expected result, actual result and complete error message.
  • Your setup: Manager and client versions, OS, model and whether Manager runs locally or on a server.
  • One useful comparison: what still works, the change you tried, and the failure time with time zone. Include a relevant request ID if available.

If the log view appears empty or stale, follow the log-location instructions and find the same time range. Share a short relevant excerpt after removing keys, OAuth tokens, account details, private prompts and identifying file paths. Keep raw account files and unredacted network captures private.

WINDOWS DOWNLOAD

Archive password

Keep this password to open your Windows download if prompted.