BACKUP & RESTORE · ANTIGRAVITY TOOLS
Back Up, Migrate & Remove Antigravity Manager Data
Save the whole Manager data folder to keep accounts, settings and local databases together. Use an account export when you only need to transfer credentials. Before replacing a working profile, open a separate copy of the backup and check that it contains the data you need.
For version 5.0.0 · Updated
START WITH THE ACTIVE PATH
Where does Manager store my data?
Open Settings → Advanced → Data Directory to see the active folder. Use that displayed path for your backup, especially if you previously moved the data or run Manager in Docker.
In the desktop application, Open opens the folder in your file manager. The Web UI displays the server’s path; access those files on the server or through its storage tools.
- Windows default
%USERPROFILE%\.antigravity_tools, under the Windows user running Manager.- macOS and Linux default
~/.antigravity_tools, a hidden folder in that user’s home directory. Enable hidden-file display or use your file manager’s Go to Folder command.- Docker
- Find the host folder or volume mounted at the container’s data path. The Docker guide’s Compose file maps host
./datato/root/.antigravity_tools. Back up the contents of that persistent mount.
If the folder or account list has changed unexpectedly
Check the environment used to launch Manager. A nonempty ABV_DATA_DIR overrides the saved location. Without that override, Manager can read ~/.antigravity_tools_location to find a custom folder; ABV_DATA_DIR_POINTER_FILE can set a different pointer-file location.
Compare the displayed path with your previous location before importing accounts again. Look for accounts.json, the accounts/ folder and gui_config.json. An empty new profile often means a different folder was opened. Preserve any candidate folders while you identify the correct one.
CHOOSE WHAT TO PRESERVE
Which backup do I need?
Use a complete data-folder copy to restore Manager’s accounts and settings together. Use JSON export for account-only transfer, and save client configurations and conversation history from their own locations.
| Your task | What to save | What to save separately |
|---|---|---|
| Transfer selected accounts | Accounts JSON export: email and refresh token for each selected account. | Manager settings, local labels, device profiles, logs and user tokens. |
| Restore the Manager profile | The entire active data folder after Manager has stopped, including account files, configuration, databases and logs. | The location/launch settings, Docker deployment files and any client files outside that folder. |
| Undo a client configuration change | The client’s current config and the relevant sync backup, such as JeikCode’s config.toml backup. | Client credentials stored elsewhere, workspace files and conversations. |
| Preserve IDE conversations | The IDE’s profile, conversation files, index and relevant workspace state. | The Manager profile if you also need its accounts and settings. |
Account exports and full profile copies contain credentials. Keep them in protected storage and use a private transfer method. See how Manager stores account data.
MAKE THE COPY
How do I make a complete backup?
Stop Manager and copy its entire active data folder to a new, dated location outside the source. Keep the backup untouched while you test a second copy.
- Record the setup. Note the Manager version, active data path and any launch overrides. For Docker, also keep
compose.ymland the private.env. - Stop writes. Finish client requests and quit Manager completely, including its tray process. Stop the headless service or container and pause automatic restarts during the copy.
- Copy the complete folder. Choose a new destination, with room for a backup and a restore-test copy. Preserve the source’s contents and file permissions. A dated folder helps you keep snapshots separate.
- Keep database sidecars. Include any
-wal,-shmand journal files that remain beside the databases. SQLite’s WAL documentation explains that committed data can still reside in the WAL file. - Compare the copy. Check that the files and sizes match; use hashes if your backup tool provides them. Keep the version and source-path note beside the protected backup.
For the Compose deployment, use the stopped-service backup commands. Keep the active profile on storage local to the Manager host; transfer closed backups to network storage separately.
Recognize the main files
accounts.jsonindexes the account records inaccounts/<id>.json. Preserve the index and records together.gui_config.jsonholds application settings, including connection credentials.- Databases can include
token_stats.db,proxy_logs.db,thinking_store.db,user_tokens.dbandsecurity.db. Copy the whole folder so additional files are included too. - Keep existing recovery files such as
accounts.json-backupuntil you have checked the new backup.
Do logs and thinking records preserve my conversations?
Preserve conversations through the IDE’s own profile or export. Manager’s thinking store supports request handling, while proxy logs record traffic according to logging and retention settings.
Retention can remove old rows or payloads, and busy log writers can skip persistence. The request option store: false controls particular response/session storage paths; logging, statistics and client caches have separate settings. For a support case, collect a focused diagnostic export.
Export just the accounts
In Accounts, select the accounts you want to transfer and choose Export. Version 5.0.0 exports each selected account’s email and refresh token. Check the saved file and account count before relying on it.
The desktop app uses your configured export folder or a save dialog; the Web UI uses the browser download. Keep an existing export under a separate name before exporting again: the generated filename includes the date. After import on another installation, refresh the accounts and reauthorize any expired or revoked credentials.
OPEN A SEPARATE COPY
How do I restore a backup?
Copy the backup into an empty restore-test folder and open it with the same Manager version first. Use a temporary ABV_DATA_DIR launch override to keep the original profile in place.
- Quit the current Manager instance and its background service. Keep the untouched backup separate from both the original and restore-test folders.
- Use a test machine or OS profile with networking disconnected for the initial local check. Copied settings can start services, tunnels or scheduled work; review them before reconnecting.
- Launch Manager against the restore-test folder using the command for your operating system below.
- Confirm the displayed Data Directory, account identities and labels, selected settings, and any user tokens or statistics you need.
- Close Manager after checking. If you need to inspect database integrity, work on the stopped test copy. Reconnect only after reviewing copied credentials, paths and service settings, then test the required account or client workflow.
Linux or macOS: launch the restore-test folder
Replace the first path with the full path to your restored copy and the second with the installed Manager executable. On Linux, command -v antigravity-tools can locate an installed binary; an AppImage uses its own executable path. On macOS, choose the executable inside the app bundle’s Contents/MacOS directory.
ABV_DATA_DIR="/absolute/path/manager-restore-test" \
"/absolute/path/to/manager-executable"
Quit this test instance before using your usual launcher again.
Windows: launch the restore-test folder
Replace D:\Manager-restore-test with the restored folder and C:\Path\To\Manager.exe with the executable path from your Manager shortcut. Paste the block into PowerShell. It waits for the test process to exit and restores the terminal’s previous data-directory setting.
$previousDataDir = $env:ABV_DATA_DIR
try {
$managerExecutable = 'C:\Path\To\Manager.exe'
if (-not (Test-Path -LiteralPath $managerExecutable -PathType Leaf)) {
throw "Manager executable not found: $managerExecutable"
}
$env:ABV_DATA_DIR = 'D:\Manager-restore-test'
Start-Process -FilePath $managerExecutable -Wait -ErrorAction Stop
} finally {
$env:ABV_DATA_DIR = $previousDataDir
}
For Docker, create a separate deployment pointing at a copy of the backup, with its own project name and port. Follow the Docker restore procedure for the Compose files and mount layout.
If the restored profile is incomplete
Stop the test instance and compare its path, accounts.json, account files and configuration with the untouched backup. Preserve the matching index and account records as one set. Return to the original profile while you investigate; use diagnostics for read errors or damaged files.
To make a successful restore your working profile, first preserve the current destination, then put the checked copy at the intended active path or update its launch override. Verify the final path after restarting. If an update changed the storage format, roll back with the earlier application version and its matching backup.
MOVE THE DATA YOU NEED
How do I move data or import accounts?
Use the desktop data-directory control to relocate a complete local profile. For another computer, transfer either a stopped full backup or an account export, depending on which settings you want to keep.
Move the active data folder
- Make an independent backup and check it first. Stop API Proxy, any tunnel and incoming client activity while leaving the desktop app open for the move.
- Open Settings → Advanced → Data Directory → Select. Choose a new or empty folder outside the current data directory.
- Read the Migrate data directory confirmation and choose Confirm. Manager renames or copies the source to the destination and removes the old directory when possible.
- Restart Manager so open log files switch to the new location. Check the displayed path, accounts and settings.
- If your launcher sets
ABV_DATA_DIR, update it to the new path. Otherwise the next launch can open a fresh profile at the old location.
The Web UI shows the server path but has no desktop folder-selection control. For a server or Docker deployment, stop the service, copy the data, update the deployment path or mount and restart it. Keep the original until the new path has been checked.
Manager rejects a populated destination or a folder inside the source. Choose a separate empty folder instead of deleting an existing destination to force the move. If migration fails, stop further changes and recover from the independent backup.
Move to another computer
Transfer the protected backup and its version/path note, install the same Manager version and run the restore test on the destination. Adjust executable paths, export folders, proxy addresses and container mounts before enabling connected clients.
Copy external client configurations, workspace files and conversation history separately when you need them. OS keychain credentials and active sessions need their own setup. Review copied API keys and management passwords, then verify authorization on the destination.
Import JSON or an older client database
For an account export, use Accounts → Import, review the success and failure counts, then confirm the intended identities. The account-import guide explains accepted formats and the authorization check.
For an existing local client, open Add Account → Import DB. Choose Scan & Import All Local Accounts for local discovery or Import Custom DB for a saved database such as state.vscdb. Identify the matching client profile first and preserve a copy before importing.
Version 5.0.0 can also convert supported older Manager files that contain complete account records into the current index and individual account files, saving accounts.json-backup during conversion. Keep that original and test the converted profile before retiring the old installation. Reauthorize credentials that the provider rejects through the normal account workflow.
CLIENT CONFIGURATION & HISTORY
How do I restore client settings or missing conversations?
Find the affected client’s configuration and history on the machine where that client runs. Preserve its current files before restoring settings or investigating an empty conversation list.
Restore JeikCode configuration
JeikCode is a coding client that Manager can configure. Its folder is JEIKCODE_HOME when that variable is set for the Manager process, or ~/.jeikcode by default.
- Close JeikCode and copy both
config.tomlandconfig.toml.antigravity.bakto a separate safe location, if the backup exists. - Check the backup’s contents. Manager normally keeps the first existing configuration when syncing; later syncs leave that backup unchanged.
- In API Proxy → One-Click Agent Tools Configuration, use the JeikCode card’s restore icon, labelled Restore Defaults, then confirm the Restore Backup dialog. This replaces the current config with the backup and consumes the backup file.
- Reopen JeikCode and check the provider, base URL, model and credentials. Use your separately saved config if you need to undo this restore.
When the backup is missing, Restore Defaults writes http://127.0.0.1:8046/v1 with an empty API key. Save the current config first, then set the URL and key for the connection you intend to use. OpenCode and Claude Code have their own backup rules: use the OpenCode restore guide or Claude Code restore guide.
Web UI client sync writes on the Manager server or inside its container. For a client on your laptop, inspect and restore the laptop’s files.
Conversations disappeared after an account switch
Record the IDE version, selected account, workspace and active profile path, then stop switching or cleaning up files. Close the IDE and preserve its history files, index and workspace before changing anything else.
- The files exist, but the sidebar is empty
- Check that you opened the original account, profile and workspace. Investigate indexing or display problems against a copied profile.
- The index reports errors
- Keep the original files and use the client’s supported repair or export workflow on a copy. Compare the recovered conversation contents before replacing the working profile.
- The conversation files are missing
- Look for an earlier client backup or export. An index rebuild needs the underlying conversation files.
Tools for finding unindexed Antigravity conversations
The separate antigravity-history CLI and Antigravity History editor extension document ways to find and export existing .pb conversations through Antigravity’s LanguageServer.
Their instructions require Antigravity running with a workspace open. The CLI’s 0.2.6 guide lists Windows support, macOS as untested and Linux as planned; the extension documents Windows verification. Check the project’s current requirements and use a separate test environment with a copied IDE profile. Start with an export and inspect its contents before attempting to replace an index.
REMOVE ONLY THE DATA YOU CHOOSE
How do I remove Manager and its data?
Stop Manager, uninstall it through the method used to install it, then review the data folders and backups you want to retain or delete. Revoke account or client access separately when that access should end.
- Save anything you need. Check the backup or export before removing the last working copy.
- Stop all instances. Quit the tray app, stop headless services or containers and disable their automatic restart.
- Remove the app. Use the operating system’s uninstall flow or the appropriate package manager. Check the active data location afterward.
- Remove selected Manager files. Delete the confirmed Manager-owned data folder if you no longer need it. Review custom paths, exports, external backups and container volumes individually.
- Clear stale path settings. Remove a location pointer or launch override that still refers to deleted data. Check the value before deleting the pointer file.
- End access. Follow credential revocation for Google authorization, API keys, user tokens and tunnel connectors.
To remove just one account, use Manager’s account-removal control. Keep IDE profiles, workspace files and other clients’ data unless you have deliberately chosen to remove those too.
Afterward, confirm that the intended services are stopped and selected files are gone. Any retained backup still contains its data and credentials. If you install Manager again, it can create a new empty profile at its configured location.
Before replacing the working profile
Finish these checks while the original and untouched backup are still available:
- The active source path and Manager version are recorded.
- The backup contains the complete folder copied with Manager stopped.
- A separate restored copy opens with the expected accounts and settings.
- Client files, machine-specific paths and copied credentials have been reviewed.
- The account or client workflow you need works on the intended destination.