Same problem here. I made a post about it as well:
Yes, I am facing the same issue and I have Pro plan
same problem here, sometimes, If I put 3 times the prompt start to work
Same problems here, am on Google AI Ultra. It completely doesn’t worth the money I paid. I mean, is there some way that I can ask a partial refund?
Well, I managed to fix it temporarily. What I did was download the February version of Antigravity, 1.19.6, from Google Antigravity . in the section “releases” Then, in the options, I indicated that it shouldn’t update. To do this, once I downloaded the old executable, I disconnected from the internet and went to Settings → Online Service Settings. There, I found the “Update” option and changed it to “None.” Now the agent is working correctly; it’s not indicating that I’ve exceeded the quota or anything like that. For now, it’s fine. We’ll have to wait for an official solution from the Google team, but at least I was able to continue working without problems. It’s been almost two hours of full agent use, and it hasn’t crashed. I hope Google can resolve this.
I was able to fix buy disabling the workspace config.
AntiGravity’s internal git library doesn’t support the worktreeConfig extension. Look back at your .git/config — I saw:
[extensions]
worktreeConfig = true
git config --local --unset extensions.worktreeConfig
Remove the –local if it was happening for all your projects.
Temporary Fix for Antigravity Bug for Windows 11
If you are still encountering this issue, apply the following steps exactly:
-
Uninstall Antigravity
- Remove the current version completely from your system.
-
Install a Stable Version
-
Go to: Google Antigravity – Releases
-
Download Version 1.19.6
- Select: Windows x64 (.exe)
-
Install the downloaded version.
-
-
Disable Auto-Updates (Critical Step)
-
Open Antigravity
-
Navigate to:
-
Settings icon (top-right, beside profile)
-
→ Editor Settings
-
→ Application
-
→ Update
-
-
Apply the following:
-
Uncheck: Enable Windows Background Updates
-
Set Mode to: None
-
-
Result
Prevents Antigravity from updating to newer versions where the bug exists.
this worked for me, i used worktree on claude which messed up working in AG
It’s working. Thank you.
Antigravity should fix this little big bug.
Adding to this thread for anyone who’s tried the extensions.worktreeConfig unset alone and still has dead-silent chat. I hit two compounding faults — either one breaks the agent, both together make it look unfixable. Confirmed via dev tools console + ls-main.log. Took an afternoon to nail down; tested fix below.
Symptoms (you have all three):
-
Prompts go in, nothing comes back. No spinner, no error toast.
-
Dev tools console (
Help → Toggle Developer Tools → Console) shows[createInstance] ooe depends on UNKNOWN service agentSessions -
%APPDATA%\Antigravity\logs\<latest>\ls-main.logshowscore.repositoryformatversion does not support extension: worktreeconfigand/orworkspace infos is nil -
(Bonus tell) console also shows
Error activating plugin Apigee: failed to parse JSON file ...combined_OI_workspace.code-workspace
The two faults:
-
Antigravity’s Go-based LSP can’t parse
extensions.worktreeConfig = trueregardless ofrepositoryformatversion. The error message is misleading — it doesn’t matter that you have version 1. -
Antigravity’s auto-managed
.code-workspacefile at~\.gemini\antigravity\brain\<uuid>\is written with JSONC trailing commas, but the plugin loader uses strictJSON.parse. The Apigee plugin trips on it, and theagentSessionsservice registration appears to depend on a successful workspace load downstream.
Fix (Windows / PowerShell):
powershell
# 1. Strip trailing commas from the auto-managed workspace file
$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
Set-Content $ws.FullName -Value ((Get-Content $ws.FullName -Raw) -replace ',(\s*[\]}])', '$1') -NoNewline
# 2. For each affected repo: preserve longpaths in main config, drop the extension
$repo = "C:\path\to\your\repo" # <-- change me
git -C $repo config core.longpaths true
git -C $repo config --unset extensions.worktreeConfig
# 3. Fully close Antigravity (every process), then reopen the workspace.
Verify after restart:
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" }
CLEAN + a test prompt that gets a response = done.
Bonus: have an AI agent walk you through this
If you’re stuck and want Claude (or any IDE-integrated AI assistant) to do this with you, paste this prompt into your chat:
My Antigravity IDE chat panel has gone silent — I send prompts but get no response,
no spinner, no error toast. Walk me through the canonical fix step by step. Don't
run destructive commands. Back up files before modifying. Ask me to confirm before
each step.
Step 1 — Diagnose. Open Antigravity's dev tools (Help → Toggle Developer Tools →
Console) and tell me whether each of these is present:
• "[createInstance] ooe depends on UNKNOWN service agentSessions"
• "failed to parse JSON file ...combined_OI_workspace.code-workspace"
Also check the latest %APPDATA%\Antigravity\logs\<latest>\ls-main.log for hits on
"worktreeconfig" or "workspace infos is nil".
Step 2 — If any of those fired, run this PowerShell. Tell me what to substitute:
$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" -Force
Set-Content $ws.FullName `
-Value ((Get-Content $ws.FullName -Raw) -replace ',(\s*[\]}])', '$1') -NoNewline
$repo = "<my repo path>" # Ask me for this
git -C $repo config core.longpaths true
git -C $repo config --unset extensions.worktreeConfig
Step 3 — Have me fully close and reopen Antigravity.
Step 4 — Re-check ls-main.log for "worktreeconfig" hits and confirm chat responds.
Explain what each step is doing in one sentence so I learn the why, not just the how.
The worktreeConfig half of this was first called out by @demigod and detailed beautifully by @mk_4oto — credit to both of them. Adding the JSON-parse fault here for anyone whose repo doesn’t have the gitlink complications mk_4oto described but whose chat is still dead.
Hope this saves someone an afternoon.
It looks like the Antigravity IDE Version 2.0.1 for Windows has fixed this issue. At least all prompts work without crutches.
Antigravity IDE Version: 2.0.1
VSCode OSS Version: 1.107.0 (user setup)
Commit: bf9a033f33934fb4496d7eebed52486272437c3a
Date: 2026-05-19T04:56:43.093Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200 // It’s weird numbering for Win 11, BTW
Language Server CL: 917586812


