Featured

How to fix Agent is not responding error in Antigravity?

by
Your Antigravity chat panel on Windows accepts prompts but returns nothing. You may also see cryptic console or log messages about agentSessions, worktreeconfig, or JSON parsing.

Antigravity agent chat is silent on Windows with no spinner and no error

You type a prompt, nothing happens. No spinner and no toast. Developer tools Console shows one or more of:
  • [createInstance] ooe depends on UNKNOWN service agentSessions
  • Error activating plugin Apigee: failed to parse JSON file …combined_OI_workspace.code-workspace
The latest log at %APPDATA%\Antigravity\logs\\ls-main.log includes:
  • core.repositoryformatversion does not support extension: worktreeconfig
  • workspace infos is nil
If your issues also include token budgeting anomalies, see our quick token limit troubleshooting.

Solution Overview

AspectDetail
Root CauseTwo compounding faults: 1) Git setting extensions.worktreeConfig enabled breaks Antigravity’s Go LSP regardless of repositoryformatversion. 2) The auto managed .code-workspace file contains trailing commas that strict JSON parsing rejects, preventing agentSessions from registering.
Primary FixRemove trailing commas from the active .code-workspace, then unset extensions.worktreeConfig in each affected repository, and restart Antigravity.
ComplexityMedium
Estimated Time10 to 20 minutes

Fix the silent agent now

Step by Step Solution

Step 1 — Confirm the symptoms
  • Open developer tools: Help → Toggle Developer Tools → Console.
  • Check for these messages:
– [createInstance] ooe depends on UNKNOWN service agentSessions – failed to parse JSON file …combined_OI_workspace.code-workspace
  • Open the newest log: %APPDATA%\Antigravity\logs\\ls-main.log and look for worktreeconfig or workspace infos is nil.
If you also have separate browser agent troubles, compare with this targeted fix in our browser agent troubleshooting. Step 2 — Strip trailing commas from the active workspace file This converts JSONC commas to strict JSON so the plugin loader can parse it. PowerShell 
# Find the most recently written workspace file and back it up with a timestamp
$ws = Get-ChildItem "$env:USERPROFILE\.gemini\antigravity\brain" -Recurse -Filter "*.code-workspace" |
 Sort-Object LastWriteTime -Descending | Select-Object -First 1
Copy-Item $ws.FullName "$($ws.FullName).bak-$(Get-Date -Format yyyyMMddHHmmss)" -Force


Strip trailing commas before } or ] to make strict JSON

Set-Content $ws.FullName -Value ((Get-Content $ws.FullName -Raw) -replace ',(\s*[\]}])', '$1') -NoNewline
Step 3 — Fix each affected repository’s Git configuration This preserves long path support and removes the breaking extension flag. PowerShell 
# Change this path to your repository root
$repo = "C:\path\to\your\repo"

git -C $repo config core.longpaths true
git -C $repo config --unset extensions.worktreeConfig
If you previously enabled worktrees with AI assistants, repeat the two git commands for every repo that is opened by Antigravity. Step 4 — Fully close and reopen Antigravity
  • Quit Antigravity.
  • In Task Manager, ensure no Antigravity processes remain.
  • Reopen the same workspace.
Step 5 — Verify the fix You should now get a response to a test prompt. Also validate the logs are clean. PowerShell 
$ls = Get-ChildItem "$env:APPDATA\Antigravity\logs" -Directory |
 Sort-Object LastWriteTime -Descending | Select-Object -First 1 |
 ForEach-Object { Join-Path $_.FullName "ls-main.log" }
if (Select-String -Path $ls -Pattern 'worktreeconfig|workspace infos is nil' -Quiet) { "STILL BROKEN" } else { "CLEAN" }

Alternative Fixes and Workarounds

Pin Antigravity to a stable version and disable auto updates If you prefer a quick rollback while waiting for a product fix:
  • Uninstall Antigravity.
  • Install a known stable build: version 1.19.6 for Windows x64 from the official releases page.
  • In Antigravity, open Settings icon then Editor Settings then Application then Update:
– Uncheck Enable Windows Background Updates – Set Mode to None This prevents upgrades that reintroduce the bug. For cross version browser side issues, compare with our additional browser agent notes. Only remove the Git extension flag If your Console does not show JSON parse errors, try only unsetting the extension: PowerShell 
$repo = "C:\path\to\your\repo"
git -C $repo config --unset extensions.worktreeConfig
Then restart Antigravity and test.

Troubleshooting Tips

  • Confirm you edited the most recent .code-workspace under %USERPROFILE%\.gemini\antigravity\brain. There can be multiple files.
  • If you use multiple repos in the workspace, unset extensions.worktreeConfig in each one.
  • Ensure you have write permissions for the workspace file and the repo config.
  • Re run Step 2 if Antigravity regenerates the workspace file after an update.
  • Look for any other JSON parse errors in the Console that point to a different .code-workspace path.
  • If the log still mentions worktreeconfig, verify there is not a global setting:
– PowerShell 
git config --global --get extensions.worktreeConfig

If it prints 'true', then:

git config --global --unset extensions.worktreeConfig
  • If prompts still fail, temporarily disable non essential plugins to isolate a loader failure, then re enable after a clean run.
For background on strict JSON versus JSON with comments, see VS Code JSON and JSONC. For the Git setting behavior, review git config extensions.worktreeConfig.

Best Practices

  • Avoid enabling extensions.worktreeConfig in repos opened by Antigravity until an upstream fix ships.
  • Keep a backup of the active .code-workspace whenever Antigravity updates it.
  • Pin to a stable product version and keep auto updates disabled when your workflows are critical.
  • Make small changes then re test, and always back up files before modifying.
  • Keep long path support enabled in repos that need it.

Final Thought

The silent chat issue stems from a strict JSON parse failure and a Git extension flag that the language services cannot handle. By fixing the workspace JSON and unsetting the extension in your repos, you restore agentSessions and get immediate responses again.

Leave a Comment