ACCOUNT SETUP · ANTIGRAVITY TOOLS 5.0.0
Add, Import & Switch Accounts in Antigravity Manager
To add an account to Antigravity Manager, open Accounts → Add Account → OAuth and sign in with Google. You can also import your existing credentials. Once the account appears, choose how to use it in your IDE, CLI or API gateway.
These steps cover the desktop app’s controls in version 5.0.0. For a server installation, use the Docker setup guide.
CHOOSE HOW TO USE THE ACCOUNT
After adding an account, choose your client
Save the account in Manager first. Then switch your installed Antigravity client or connect an API client to the gateway, depending on where you want to work.
Find your email in Accounts
Check that the address matches the Google account you authorized. Review its status and refresh the model quotas.
Select the account for that client
Choose Classic, IDE or CLI in Manager, then confirm the signed-in email inside the client you switched.
Choose a switching target →Allow the account in the gateway pool
Enable proxy access for the account, connect your client and check which account serves its request.
Manage API pool access →SIGN IN THROUGH YOUR BROWSER
Add an account with Google OAuth
Choose OAuth to sign in through Google and let Manager save the account. Have Antigravity Tools open and use a Google account you control.
- Open Accounts → Add Account → OAuth and wait for the authorization link.
- Click Start OAuth to open your default browser, or use Copy Auth Link and open the link in your preferred browser.
- Select the intended Google account and review the consent screen. If the browser picks a different account, cancel and start again with the correct one.
- Keep Manager open on the OAuth tab of the Add Account dialog until sign-in finishes. Moving to another tab in that dialog cancels the prepared sign-in link.
- Return to Accounts and find the email you authorized. Check its status and refresh its quotas before using it.
Account added: your email appears in the list. If the account is present but quotas fail to load, keep the entry and investigate the quota error.
Finish a sign-in that is still waiting
After completing authorization in the browser, click I already authorized in the same dialog if Manager is still waiting. Then check Accounts for your email.
Complete sign-in with a callback URL or code
Use the manual field when the browser has returned a callback URL or authorization code but the automatic handoff fails:
- Keep the current OAuth flow open in Manager. If you closed it or changed tabs, start a fresh flow and use its new link.
- After browser consent, copy the full callback URL or code from that flow.
- Paste it into Paste callback URL or code... in Manager and click Submit.
- Wait for processing, then check that the email appears in Accounts.
Keep callback URLs and codes private. If the browser shows localhost refused to connect, or you are signing in to a remote server, follow the callback troubleshooting steps.
For invalid_grant, a missing refresh token or a rejected authorization, use the sign-in error guide with the exact message.
USE EXISTING ACCOUNTS
Import a token, JSON export or local database
Use Refresh Token for pasted credentials, the Accounts page’s Import button for JSON files, or Import DB for local client data. Keep these files and tokens as private as a password.
Start with a small set and keep a protected backup before a larger import. Adding an email already in Manager updates its existing account credentials. For your first account, browser sign-in is usually the easiest route.
Paste a refresh token
- Open Accounts → Add Account → Refresh Token.
- Paste your own refresh token. Version 5.0.0 recognizes tokens beginning with
1//; use a refresh token for this field. If you only have an access token, add the account through OAuth. - Click Confirm and read the success and failure counts.
- Search Accounts for the expected email and check its status. An expired or revoked token needs fresh authorization.
For a batch, this field accepts a JSON array with refresh_token fields or text containing matching tokens. Paste only the credentials you intend to import. Manager obtains the account email from Google when it validates the credential.
Import an account JSON file
- On the Accounts page, click Import and choose your JSON export. Use an export from Manager when available.
- Wait for the result and compare it with the number of accounts you expected. Check both successful and failed entries.
- Search for the expected emails. Keep the successfully imported accounts and resolve the missing or failed entries before retrying.
Accepted account entries contain refresh_token or token.refresh_token and can be grouped in arrays or account containers. Entries without a recognized refresh token are skipped before import, so compare the account list with your original file even when the reported batch succeeds.
The desktop importer tries to create a copy beside the source file with -backup appended to its name. Protect that copy too, and keep your own backup in case it cannot be created. An account export contains credentials; use the backup and migration guide for a full move between computers.
Import accounts already signed in on this computer
Open Add Account → Import DB. Choose Scan & Import All Local Accounts to look for local client credentials, then review every email added to the list.
For a specific supported database, choose Import Custom DB and select your local file, such as a .vscdb database. This desktop file picker is for client databases; use the Accounts page’s Import button for JSON exports.
Imported the wrong account? Identify which entries were added or updated. Remove unwanted entries using the deletion steps. If an existing account’s credentials were replaced, sign in again with the intended account or recover from a compatible backup.
FIND AN ACCOUNT
Search the list and read its status
Search Accounts by email. If an account seems missing, select All, clear the search and check the other pages of results.
Email search ignores capitalization. The tier filters narrow the list to Free, Pro or Ultra accounts. Use Grid View when you want the explicit Classic, IDE and CLI switching controls.
- Disabled
- The account has been disabled, often because its saved authorization expired or was revoked. The gateway skips it and switching or refresh controls may be unavailable. Read the reason and reauthorize the account when needed.
- Proxy Disabled
- You have excluded the account from gateway requests. It remains saved in Manager for desktop use. Choose Enable Proxy to allow it back into the API pool.
- Quota or validation warning
- Read the message for the affected model and check the refresh time. Use the quota guide for balances and reset times, or quota and availability troubleshooting for rejected requests.
CHOOSE THE CLIENT TO CHANGE
Switch an Antigravity IDE or CLI account
Use Grid View to choose the exact client you want to switch. Save your work first: switching can restart the target application.
Manager offers three targets: Classic for the standalone Antigravity desktop client, IDE for Antigravity IDE, and CLI for the agy command-line client. In List View, the generic switch button selects Classic.
- Note the account currently signed in to your target client. For
agy, end running sessions before switching so they can release the old credentials. - In Accounts, find the account you want to use and check its status and model quotas.
- In Grid View, choose Switch to Antigravity (Classic), Switch to Antigravity IDE or Switch to Antigravity CLI (agy). Hover over the switch icon to read its label.
- Wait for the operation to finish. Open the chosen client, or start a new
agysession, and confirm the active email there. - Start a fresh conversation with a short prompt, then send a follow-up.
Ready to use: the intended client shows the selected account and completes the conversation.
If the client keeps the old account, fails to open or reports storage_json_not_found, follow switching and storage troubleshooting. To return to your previous account, repeat the switch with the same client target and check its identity again.
CONTROL GATEWAY REQUESTS
Exclude an account from the API pool
Choose Disable Proxy to keep an account saved while excluding it from new API requests. This leaves its desktop-account use available.
- Find the account by email and choose Disable Proxy.
- Check that the account shows Proxy Disabled. If Manager reports a synchronization error, resolve it before sending more requests.
- To use the account for API requests again, choose Enable Proxy and check its authorization, available models and quota.
If this is the fixed gateway account and the proxy is running, disabling it also clears that fixed-account selection. Set the preference again if you want it back after re-enabling the account.
Use a small request through your API client and inspect the gateway’s request details to see which account served it. The active IDE badge identifies the IDE’s account; gateway scheduling has its own selection. The proxy guide and client setup guide cover that connection.
For an account marked Disabled, address the underlying authorization error before enabling proxy access.
REMOVE FROM MANAGER
Delete an account and understand what remains
Deleting removes the saved account entry and its account file from Manager. For a temporary break from API traffic, use Disable Proxy instead.
- Keep a protected export or data backup if you may need the account again. If it is signed in to a client, switch that client to the account you want to keep using.
- Check the email on the account card or row before choosing its delete action. For a bulk deletion, review all selected accounts and the count in the confirmation.
- Confirm deletion, clear any filters and search for the email to check that the entry has gone.
Your Google account, existing client sessions and provider authorization remain separate from Manager’s saved entry. To sign out of a client or revoke access, use that client’s or Google account’s controls. Exports and backups also retain any credentials they contain; manage those copies through the security guide.
If you delete Manager’s current account, it may select another remaining entry internally. Verify the account in each client you continue to use.
To add it back: sign in through OAuth again or import your protected account export. Restore a compatible full backup if you also need settings or device-profile history.
OPTIONAL DEVICE SETTINGS
Manage an account’s device profile
A device profile stores machine identifiers associated with an account. Manager uses that binding during supported client switches. For ordinary account setup, you can leave the profile settings alone.
Open the account’s Device Fingerprint dialog to see its Account Binding and history. Generate and Bind opens a preview; choose Confirm to save it or Cancel to leave the binding unchanged. Manager can also generate a missing profile automatically when you switch accounts.
Saving or restoring a profile updates the account’s stored binding. A subsequent switch applies it to supported client storage. The dialog labels the stored binding Pending Application. Check the intended client after switching to confirm the result.
Before changing a working profile, back up the relevant data. To return to a recorded version for this account, use Restore beside that version in its history.
Check the target before using Restore Original
In version 5.0.0, Restore Original changes the binding of Manager’s current account, which may differ from the account whose dialog you opened. Verify the current account before confirming. To restore a specific account’s history version, use its own Restore action.
The original-profile action needs a saved baseline. Review the profile shown in the confirmation; the baseline is the saved set of identifiers available to Manager. After restoration, apply the binding through the appropriate client switch.
Account restrictions still apply when device identifiers change. For a blocked sign-in, quota error or missing storage file, follow authorization troubleshooting or switching troubleshooting before changing device settings.
CONTINUE WITH YOUR ACCOUNT
Choose what to do next
With the account saved and its status checked, open the guide for your next task:
- Read quotas and reset times before choosing an account for a long session.
- Start the API proxy to use the account through an external client.
- Back up or migrate your data before moving to another computer.
- Review account and gateway security before sharing access.