Agent Manager Completely Unresponsive - any LLM

Google Antigravity
1

I’m doing a lot of internal debugging to no avail. The last few days Antigravity IDE has been completely unusable. The agent manager is completely dead. I’ve cleared cache. I’ve reset various features and things. I’ve disabled extensions. I’ve opened and closed in debug mode. I’m about to try a full uninstall and re-install, which is generally unacceptable.

Conversations aren’t even initializing.

Has anyone had any luck?

2

image
image765×601 10 KB

3

This error has been plaguing me for several versions, and I just accidentally found a solution that worked for me. It’s almost embarrassing that all I needed to do was disable the “GitHub Theme”.

I had Gemini craft the following technical summary as it’s likely a regression the engineers need to see:

Found a fix/workaround for the unresponsive Agent Manager UI in v1.21.6.

Symptoms: ‘File/Edit/View’ menus and LLM dropdowns fail to register clicks; Markdown split-view renders invisible text.

The Cause: It appears to be an Extension Host conflict. For me, disabling the “GitHub Theme” extension immediately restored all functionality.

It seems the latest update is vulnerable to third-party UI/Theme extensions that inject global styles or CSS overrides. If you’re experiencing a “frozen” UI, try disabling all theme-related extensions.

4

Yeap, I turned off the theme I used and now everything works

5

Inside Agent Manager and a Workspace that I shared with ClaudeCode I ran into this issue. The root case seems to be that AG does not allow work trees while ClaudeCode does. I had to sent Claude to use a different folder than inside the project. I think opened a new workspace and that was always working with the LLM interaction. In there I would run this MD file I had generated after getting this fix to work Agent Troubleshooting & Reset Guide

If the agent (Antigravity/Claude) becomes stuck, unresponsive, or throws TypeError related to __store, follow these steps to perform a deep reset.

Symptoms

  • Agent Manager shows “Not Responding” for a specific workspace.
  • Multiple orphaned language_server processes are running.
  • TypeError: Cannot read properties of null (reading '__store') when opening a workspace.
  • High CPU usage by language_server_macos_arm or node.

Reset Steps (To be performed by the Agent)

1. Clear Active Processes

Identify and kill stuck language server processes for the affected workspaces:

# Search for processes
ps aux | grep -iE "WORKSPACE A|WORKSPACE B" | grep -v grep

# Kill them (replace <PID> with actual IDs)
kill <PID>

2. Clean Workspace Git State

Prune orphaned worktrees and unset problematic extensions:

# Prune worktrees
git -C /path/to/repo worktree prune

# Unset worktreeconfig if it causes deadlocks
git -C /path/to/repo config --unset extensions.worktreeconfig

3. Delete Agent Metadata

Remove hidden agent directories in the workspace:

# In the workspace root or platform folders
rm -rf .claude .agents .gemini .sandbox_backup

4. Clear Global Application State

Reset internal app storage to resolve UI/Store errors:

  • Location: ~/Library/Application Support/Antigravity/User/
  • Actions:
    • Delete the specific workspace folder in workspaceStorage/ (search for the path in workspace.json inside each folder).
    • Remove entries for the workspace in globalStorage/storage.json.

5. Clear Global Claude Metadata

# Remove stale sessions
rm -rf ~/.claude/sessions/*
rm -rf ~/.claude/session-env/*
# Clean project metadata
rm -rf ~/.claude/projects/*<project-name>*

Prevention

  • Ensure .vscode/settings.json excludes .claude/worktrees from the watcher and search index.
  • Avoid using git worktree manually inside a folder that the agent is also managing.
  • If a session fails, check for index.lock files in the .git directory.

Created by Antigravity during the Great Reset of April 2026.