ACCOUNT SWITCHING · ANTIGRAVITY TOOLS
Antigravity Manager: Fix Account Switching
Choose the switch action for Classic, IDE or CLI, then check the account inside that app. For storage_json_not_found, check its local profile before retrying. If the app still shows Login, compare direct sign-in with the same account.
For version 5.0.0 · Updated
Save your work and identify the profile
Save open files and preserve important conversations before trying another switch. Record the target app’s version, executable, current account and any portable installation or --user-data-dir setting. Before an update or recovery, make the backup appropriate to the data you need.
Run Manager and the target app as the OS user who owns that profile. If you are troubleshooting requests through the API proxy, use the API account-selection guide. For an empty account list in Manager, check Manager’s active data directory.
CHOOSE THE APPLICATION
Select Classic, IDE or CLI explicitly
In Accounts → Grid View, use the switch control for the application you intend to use. The controls have these labels when you hover over them:
- Switch to Antigravity (Classic) — the Classic desktop application.
- Switch to Antigravity IDE — the code editor.
- Switch to Antigravity CLI (agy) — Google’s command-line client.
In List View, the single switch button selects Classic. Use Grid View to choose IDE or CLI.
After switching, compare Manager’s Classic, IDE or CLI badge with the account shown inside that application. Confirm the intended email there, then try a short task. If the switch control is unavailable and the account shows Disabled, follow the account reauthorization steps.
For an unusual install location, open Settings → Advanced and check Antigravity Path, Antigravity IDE Path or Antigravity CLI (agy) Path. Choose the executable for that target; on macOS the desktop-app selection points to its .app bundle.
If Manager runs in Docker or headless mode, perform local IDE switching with desktop Manager on the computer that owns the IDE profile. A server can provide the API proxy connection for your clients; changing its selected account updates server-side state.
MISSING PROFILE
Fix storage_json_not_found
Open the selected target application once under your normal OS user, then check the profile it created. This error means Manager’s storage lookup could not find a usable candidate for that target.
- Confirm the target is installed. Launch the exact Classic or IDE application you selected. Note whether it reaches its start or sign-in screen, or fails before creating a profile.
- Locate its data directory. Use the paths below as a starting point. For a custom or portable installation, check the directory used by your usual shortcut or launch command.
- Check the directory and both files. Record whether
storage.jsonandstate.vscdbexist inUser/globalStorage. Keep existing files intact. - Retry once after checking the target and path. Save work first. If the switch succeeds, check the account in the reopened application. If it fails, keep the new error and the paths you found for a report.
In version 5.0.0, an existing standard client directory can let Manager initialize a missing storage.json. Let the application create its profile first; manually making an empty file can leave the rest of the profile incomplete.
Find the standard, custom or portable storage path
Replace <client> with the actual folder name. For storage.json, IDE lookup checks Antigravity IDE, antigravity-ide and AntigravityIDE; Classic checks Antigravity and antigravity.
| Installation | Path to inspect |
|---|---|
| Windows | %APPDATA%\ |
| macOS | ~/ |
| Linux | ~/ |
| Custom user data | <user-data-dir>/ |
| Portable install | <executable-directory>/ |
Manager checks an existing custom-profile file first, then a portable file, then standard locations. If the custom or portable file is absent, lookup can continue to a standard profile.
state.vscdb has its own lookup. In 5.0.0, its standard IDE folders are Antigravity IDE, antigravity-ide and antigravity_ide; its Classic folder is Antigravity. When the two files lead to different profiles, record both paths and report the mismatch. Keep the original folder names and contents.
Check a custom --user-data-dir before closing the app
Record the full path and launch arguments while the intended application is still open. Manager can discover custom arguments from a running process, and those arguments may become unavailable after you close it.
Also inspect Settings → Advanced → Antigravity Startup Arguments. In 5.0.0, this setting is shared by Classic and IDE and takes priority over discovered arguments when it names an existing directory. Check for an override left over from another profile.
Keep a copy of the current value before changing it. For a path containing spaces, preserve your working configuration: the 5.0.0 text field splits edited arguments at spaces. If the detected profile differs from the one you use, include the redacted path and launch method in your report before another switch.
FAILED LOCAL WRITE
File, database and keyring errors
Follow the resource named in the error. A file read failure, a locked database and an unavailable system credential store require different checks.
- Read or write permission error: confirm the path belongs to the intended OS user and that user can access it. Check any security-software event naming Manager or the target file.
- Database locked: save work and close the target normally. Once its executable and profile are recorded, try one switch, then reopen the same application and profile. For custom data paths, complete the checks above before closing it.
- JSON parse or database corruption error: preserve a copy of the affected profile and the exact error. Use the client-profile recovery guidance before replacing any file.
- Keychain, Keyring, Secret Service or
secret-toolerror: run Manager in your normal desktop session and check that its credential store is available and unlocked. On Linux, use the installation and dependency checks for the named missing component.
Keep access limited to the profile’s owner when correcting permissions. Retain the original storage.json and state.vscdb; copying either from another client can mix credentials and settings. Restore temporary launch settings after the comparison.
ACCOUNT IN THE APPLICATION
The old account remains, or the app still shows Login
Check the signed-in account inside the intended application and profile. If it remains wrong, test direct sign-in there with the account you selected in Manager.
- Confirm the executable and profile, especially if you have Classic and IDE installed together or use several shortcuts.
- If direct sign-in requests verification or rejects account access, follow the login and eligibility guide with that message.
- If direct sign-in works, record both application versions. Save work, check the profile settings and try one explicit switch to the same target.
- Check the account display after the app reopens and send a short request. Record whether the account stayed unchanged, returned to Login immediately, or worked before failing later.
For invalid_grant or unauthorized_client during the switch, use the token or OAuth-client checks. Manager validates account credentials before applying the local switch.
For CLI, finish and exit active agy sessions before switching, then start a new session. A running session can keep its previous credentials and write them back. Classic and CLI also use the system credential store, so check both when you use them together.
SESSION AND HISTORY
Will switching restart the app?
Expect an IDE restart and save your work first. Classic can keep its main window open through hot-switching, with a full restart as the fallback.
- IDE: the desktop switching flow closes the target, writes credentials and starts it again.
- Classic: Manager attempts to refresh the background service while keeping the window open. If that service cannot be restarted successfully, Manager falls back to restarting the application.
- CLI: switch after finishing active sessions, then use a new command or session to load the saved credentials.
Classic Auto Hot-Switch is the separate quota-triggered feature for Classic Standalone. Its settings and thresholds are covered in the quota guide.
If a conversation disappears after switching
Stop repeated switching and reopen the same workspace and client profile. Check that the executable and user-data directory match the session where the conversation was created. Preserve both the current profile and any earlier backup, then follow the missing-history checks.
Before another attempt, save useful conversation text through the client’s available export or copy controls. Keep a separate backup of client data; Manager’s account export contains account credentials.
AFTER AN UPDATE
Switching stopped working with IDE 2.6.0
Compare the exact Manager and IDE versions with the switching changes in the release notes. Include the full beta suffix when identifying a Manager build.
These preview releases describe changes for IDE 2.6.0 switching problems:
- 5.0.1-beta.5: target/process detection, IDE credential writes and restart handling.
- 5.0.1-beta.7: credential format and recognition of background
agyprocesses. - 5.0.1-beta.9: IDE credentials written to both its database and the system credential store, plus background-process cleanup.
Use the release and compatibility guide to choose a build that addresses your version pair. Back up Manager and the target client before changing builds, then repeat the same switch and check the account, a short request and your workspace. Keep the previous installer and matching backup available for recovery.
If the same symptom remains, report both versions and the result of direct sign-in. Preserve the current data before any rollback so newer work remains available.
Should I change device bindings?
Keep the current device settings while diagnosing a switch. Start with the selected target, profile path and account error. Device bindings control local profile values; Google account-access messages need the sign-in checks.
For an intentional device-profile change, use the device settings guide and preserve the existing profile first.
Report a switch that still fails
Include the target and failing step so the maintainer can reproduce your case: Manager build, OS, app version, executable and profile path, exact error and time, account before and after, restart behavior, and the direct sign-in result.
For storage failures, say which directories and files exist. Replace emails and personal path segments with placeholders. Keep tokens, credential databases, device identifiers and private conversations out of the report.