Agent silently drops messages after "trajectory not found" — workspace-specific. *RESOLVED*

Google Antigravity
1

One of my workspaces stopped responding entirely. When I send a message, the spinner briefly appears and then nothing happens. No response, no error shown in the UI. All other workspaces on the same machine works perfectly.

Before this, the agent panel was stuck on “Locating Antigravity Memory Architecture” for an extended period. After pruning old conversation data from ~/.gemini/antigravity/brain/ (it had grown to ~1 GB across 100+ conversations), the initialization step started completing, but messages still go to void.

At one point the UI showed [unknown] trajectory not found + hash.

What I’ve tried (none resolved it):

  • Quit and reopen Antigravity

  • Clear ~/Library/Saved Application State/com.google.antigravity.savedState

  • Clear ~/Library/Caches/com.google.antigravity*

  • Clear ~/Library/Application Support/Antigravity/Local Storage/leveldb

  • Reset onboarding

The issue is workspace-specific — other workspaces on the same machine respond normally. Happy to provide logs if someone can point me to where they live.

EDIT: some log findings:
2026-05-18 10:16:35.578 [error] Failed to set Cloud Code URL on Language Server: Language server client has not been initialized!

EDIT 2:

UPDATE — Resolved with Claude. Root cause was a stale git config flag, not Antigravity state.

.git/config in the workspace had extensions.worktreeconfig = true (left over from a past git worktree add) while core.repositoryformatversion was still 0. Real git tolerates this inconsistency with a warning. Antigravity’s embedded git library treats it as fatal — every call into the LS (GetAgentScripts, ResolveWorkspaceInfos) returns the error core.repositoryformatversion does not support extension: worktreeconfig. The cascade manager then logs workspace infos is nil and silently fails to initialize, which is what the UI surfaces as the “Locating Antigravity Memory Architecture” hang / send-button-no-op.

Fix (1 command):

git config --unset extensions.worktreeconfig

Then quit + reopen Antigravity. Messages send and responses come back immediately. But chat logs are cleared.

Where to look in logs:
~/Library/Application Support/Antigravity/logs/<latest>/ls-main.log — search for core.repositoryformatversion does not support extension. If it’s there, this is your bug.

Likely Antigravity-side issue: the embedded git library should match upstream git’s tolerance for this case (warn, continue) instead of treating it as fatal. Better still, surface the error in the UI rather than leaving the workspace state nil with no user-visible signal.