"Antigravity silent on specific workspace, all other workspaces work, reinstall+state cleanup not solving"

Google Antigravity
1

Summary

Antigravity is completely silent (chat sends messages but no AI response, no error toast) only on one specific workspace. All my other workspaces work normally with the same account.

Environment

  • Antigravity version: [vedi About → version] — installed fresh today from antigravity.google.com DMG
  • macOS: 14.x (Sonoma) on Apple Silicon
  • Account: Google AI Ultra (paid), confirmed Active in Settings → Account
  • Other Antigravity workspaces (TRELLO_IMPORT, Aurelius): working perfectly with the SAME account, SAME models (Gemini 3.1 Pro)
  • Broken workspace: TypeScript/Node.js project (~50k files including node_modules), Git tracked, ~250MB after cleanup

Symptom

Chat receives user messages (they appear in the history list now / 15m / 18m), but never produces an AI response. The “thinking” indicator never appears. No error visible to the user.

DevTools Console errors (critical)

ERR [google.antigravity]: Menu item references a command ‘antigravity.prioritized.chat.open’ which is not defined in the ‘commands’ section ERR [google.antigravity]: Menu item references a command ‘antigravity.importAntigravitySettings’ which is not defined ERR [google.antigravity]: Menu item references a command ‘antigravity.importAntigravityExtensions’ which is not defined

Confirmed via Cmd+Shift+P: typing prioritized chat → “No matching commands”. The Antigravity extension’s chat command is not registered on this workspace, while it IS registered on other workspaces.

[Extension Host] Running in One LS mode is logged, language server starts (LS lspClient started successfully), but Antigravity command contributions are missing.

Fixes already tried (none worked)

  1. Cmd+Q + reopen multiple times
  2. Clear all caches: ~/Library/Application Support/Antigravity/{Cache,CachedData,Code Cache,GPUCache,Network,Session Storage}
  3. Move entire ~/Library/Application Support/Antigravity to _OFF backup → fresh init
  4. Disable Python extensions in workspace (ms-python.python, etc.)
  5. Add .vscode/settings.json with files.watcherExclude + search.exclude to skip heavy dirs
  6. Untrack logs/, .local/, .claude/worktrees/ from Git (~2750 deleted files committed)
  7. git reset --hard origin/main to align local with deployed production branch
  8. Full uninstall + reinstall: drag /Applications/Antigravity.app to Trash, delete ALL paths matching ~/Library/**/*Antigravity* and ~/.antigravity*, defaults delete com.google.Antigravity, then fresh download + install from antigravity.google.com
  9. Re-login with Google AI Ultra account
  10. Toggle Agent Manager (Cmd+E)

After step 8 (full clean reinstall) Antigravity opens fine on other workspaces (chat works), but still silent on this one specific workspace. This points to server-side state keyed on workspace_id.

What we expect

Since the same Antigravity app + account + models work on other workspaces, and even a fully clean reinstall doesn’t change behavior on this one specific workspace, we believe Google has cached some server-side state for this workspace_id (file_Users_<user>_SVILUPPO_<project>) that prevents extension activation.

Could you please:

  1. Reset the server-side state for our workspace? Happy to share workspace_id privately.
  2. Or provide a CLI flag / settings toggle to force a server-side workspace_id reset on next open.

We’re blocked from using Antigravity on our main project. Cursor and other VS Code forks open the same project without issue.

Thanks!