Reset Antigravity Config, MCP, or CLI State Safely

Reset Antigravity by moving the smallest documented state path to a timestamped backup, relaunching, and testing the original symptom. Do not delete the entire ~/.gemini directory: it can contain conversations, knowledge, MCP configuration, skills, plugins, global rules, CLI settings, and OAuth tokens.

Google documents ~/.gemini/antigravity/ as Antigravity 2.0's local app-data area and documents separate paths for CLI settings and shared MCP config. The path map below is based on the current Antigravity agent settings, CLI settings, and MCP documentation.

Reset Safely Before Touching State

1. Save project work. Commit, stash, or copy uncommitted files. This guide never targets a workspace, but a backup makes path mistakes recoverable.
2. Finish or stop active agents. Moving live conversation state while Antigravity writes to it can produce an inconsistent backup.
3. Sign out normally when auth is the problem. In CLI, run /logout; in Antigravity 2.0, use the account UI before moving token state.
4. Quit every Antigravity process. Confirm the app and CLI are closed before renaming directories.
5. Keep backups private. MCP config and OAuth files may contain secrets. Store recovery folders under your user profile with restrictive permissions.

Current Documented Antigravity Paths

On Windows, ~ means the current user profile (for example, C:\Users\name). These are product paths under the user profile, not assumptions about platform-specific Electron cache folders.

Choose the Smallest Reset

Create a Private Backup

Renaming is already a rollback mechanism, but make a separate copy of shared customizations before a broad app-state reset. The following macOS/Linux script creates a new private recovery folder and copies only named paths that exist:

reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_backup="$HOME/antigravity-recovery-$reset_stamp"
mkdir -m 700 "$reset_backup"

for reset_item in config GEMINI.md; do
  if [ -e "$HOME/.gemini/$reset_item" ]; then
    cp -R "$HOME/.gemini/$reset_item" "$reset_backup/"
  fi
done

echo "$reset_backup"

On Windows PowerShell:

$ResetStamp = Get-Date -Format "yyyyMMdd-HHmmss"
$ResetBackup = Join-Path $env:USERPROFILE "antigravity-recovery-$ResetStamp"
New-Item -ItemType Directory -Path $ResetBackup | Out-Null

@("config", "GEMINI.md") | ForEach-Object {
  $ResetSource = Join-Path $env:USERPROFILE ".gemini$_"
  if (Test-Path $ResetSource) {
    Copy-Item $ResetSource $ResetBackup -Recurse
  }
}

$ResetBackup

Inspect the recovery folder before continuing. Treat it as secret-bearing data; do not upload or commit it.

Reset MCP Only

Prefer the supported UI first: uninstall or disable the specific server, then press Refresh. In CLI, /mcp exposes status, reload, and connection logs. If the global file itself is malformed or poisoned, rename only that file:

# macOS / Linux
reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_mcp="$HOME/.gemini/config/mcp_config.json"
if [ -f "$reset_mcp" ]; then
  mv "$reset_mcp" "$reset_mcp.disabled-$reset_stamp"
fi

# Windows PowerShell
$ResetStamp = Get-Date -Format "yyyyMMdd-HHmmss"
$ResetMcp = Join-Path $env:USERPROFILE ".geminiconfigmcp_config.json"
if (Test-Path $ResetMcp) {
  Rename-Item $ResetMcp "mcp_config.json.disabled-$ResetStamp"
}

Relaunch and confirm the global MCP list is empty before restoring servers one at a time. A workspace may still contribute .agents/mcp_config.json; that is expected and should be reviewed in the project rather than deleted globally.

For an OAuth-only reset, close Antigravity and apply the same rename pattern to ~/.gemini/antigravity/mcp_oauth_tokens.json. This signs those MCP connections out; it does not prove that unrelated Google account authentication is cleared.

Reset Antigravity CLI Only

Start with /logout for authentication and /settings for preferences. Google separately documents deleting only keybindings.json to restore default keybindings. For a broader but reversible CLI-state reset:

The CLI directory can also contain global CLI skills and plugins. Renaming it keeps those files in the backup, but they will be unavailable to the active CLI until you restore or selectively copy them back.

# macOS / Linux, after exiting agy
reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_cli="$HOME/.gemini/antigravity-cli"
if [ -d "$reset_cli" ]; then
  mv "$reset_cli" "$reset_cli.disabled-$reset_stamp"
fi

On Windows, use the same Rename-Item pattern under $env:USERPROFILE\.gemini\antigravity-cli. This path may not exist if you have never used Antigravity CLI; absence is not an error.

Last-Resort Antigravity 2.0 Data Isolation

This is a high-impact, last-resort diagnostic that uses a product-documented data path. Google identifies ~/.gemini/antigravity/ as Antigravity 2.0's local app-data directory; it does not publish this rename procedure as an official reset. Backup-and-rename is the reversible isolation method used here. A local inspection on macOS on July 21, 2026 found conversations, knowledge, MCP state, context state, and browser recordings inside the directory, so moving it can make valuable history disappear from the active profile until rollback.

# macOS / Linux, after fully quitting Antigravity
reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_app="$HOME/.gemini/antigravity"
if [ -d "$reset_app" ]; then
  mv "$reset_app" "$reset_app.disabled-$reset_stamp"
fi

# Windows PowerShell, after fully quitting Antigravity
$ResetStamp = Get-Date -Format "yyyyMMdd-HHmmss"
$ResetApp = Join-Path $env:USERPROFILE ".geminiantigravity"
if (Test-Path $ResetApp) {
  Rename-Item $ResetApp "antigravity.disabled-$ResetStamp"
}

Relaunch once and check whether Antigravity creates fresh state. Do not simultaneously rename MCP config, global rules, skills, and plugins: changing one layer at a time preserves the ability to identify the cause.

macOS UI-Shell State: A Locally Verified Fallback

The public docs above identify the product-managed ~/.gemini paths but do not publish a cross-platform map for every native UI cache. On one current macOS installation, we verified these additional paths by name on July 21, 2026:

• ~/Library/Application Support/Antigravity — contained UI/editor state such as User, Workspaces, Session Storage, Local Storage, Backups, and logs.
• ~/Library/Caches/com.google.antigravity — native application cache.

This is local inspection evidence, not a promise that every build uses the same layout. For a blank or corrupted macOS shell, test the lower-risk cache first and never wildcard-match Antigravity paths:

reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_cache="$HOME/Library/Caches/com.google.antigravity"

if [ -d "$reset_cache" ]; then
  mv "$reset_cache" "$reset_cache.disabled-$reset_stamp"
fi

Relaunch and reproduce once. If the shell is still broken, quit the app again before isolating the higher-risk Application Support folder in a separate test:

reset_stamp=$(date +%Y%m%d-%H%M%S)
reset_ui="$HOME/Library/Application Support/Antigravity"

if [ -d "$reset_ui" ]; then
  mv "$reset_ui" "$reset_ui.disabled-$reset_stamp"
fi

We also observed ~/.antigravity on that machine, but its role was not established by current official documentation, so this guide intentionally leaves it untouched. For Windows or Linux native UI caches, inspect your actual installation or use official support instead of translating the macOS path by guesswork.

Verify the Result Before Removing Any Backup

1. Relaunch the same Antigravity product you reset.
2. Reproduce the original symptom before changing settings or restoring files.
3. Confirm the renamed backup still exists and note whether a fresh active path appears. Optional MCP, OAuth, or keybinding files may remain absent until you reconfigure them.
4. For MCP, open the manager, reload, and test one read-only tool.
5. For CLI, verify sign-in, settings, and one harmless prompt.
6. For 2.0 app state, confirm the expected conversations or knowledge are absent from the fresh profile—that proves which layer was moved, not that the data was deleted.

If the symptom survives a fresh state directory, configuration was probably not the cause. Network, quota, proxy, extension, server, or binary problems need their own diagnosis. Use the Antigravity not responding guide, proxy/TLS guide, or the troubleshooting index.

Roll Back Without Overwriting Fresh State

Quit Antigravity again. First rename the newly created active path, then move the timestamped backup back to its original name. For example:

# Replace the timestamp placeholders with the actual suffixes.
mv "$HOME/.gemini/antigravity"    "$HOME/.gemini/antigravity.failed-new-YYYYMMDD-HHMMSS"

mv "$HOME/.gemini/antigravity.disabled-YYYYMMDD-HHMMSS"    "$HOME/.gemini/antigravity"

Apply the same two-step pattern to mcp_config.json, the CLI directory, or the macOS UI-shell folder. Never restore over a live or newly populated directory. Keep the failed-new copy until you have checked whether it contains anything worth preserving.

Frequently Asked Questions

All Sources and Links

Official sources accessed July 21, 2026:

• Google Antigravity: Agent Settings and the 2.0 local app-data boundary
• Google Antigravity: MCP paths, manager actions, config schema, and OAuth token storage
• Google Antigravity CLI: settings and keybindings paths
• Google Antigravity CLI: authentication and /logout behavior
• Google Antigravity: shared rules, skills, and MCP migration paths
• Google Antigravity: global and workspace skill locations
• Google Antigravity: Antigravity 2.0 plugin locations
• Google Antigravity CLI: CLI plugin locations

Local verification note: the two macOS native UI paths were inspected by directory name on a current installation on July 21, 2026. No file contents or credentials were read, and those paths are clearly separated above from official documentation.