Antigravity completely stopped working (Dead silence/No response/Freeze)

Google Antigravity
22

Thank you. Upon executing the command git config --unset extensions.worktreeConfig within the macOS environment, I found it functioned flawlessly.

1 Like
23

Same here solved runnning this command at repo level: git config --local --unset extensions.worktreeConfig

24

I used the option 1 command inside the terminal in a project folder and it came right back alive after exiting the chat window then clicking on a history chat or starting a new one.

25

i have been having same issues but was not the worktree fix mentioned above. according to claude i was having a git reflog issue.

Root cause: Corrupted git reflog entries for HEAD and refs/heads/main — these were causing git fsck to fail with “invalid reflog entry” errors

  • Why it killed agents: Agent tooling reads git state on startup; the corrupt reflog was likely causing crashes or undefined behavior before the agent could even begin work

  • Fix applied: Deleted the corrupt .git/logs/ directory and rebuilt fresh reflogs

  • Result: git fsck is now clean, repo is on main branch, up to date with origin

    this seems to have fixed the issue of my agents dying mid task.

1 Like
26

Life saver, dude! was hard to understand why it was failing

1 Like
27

Perfect, this cmd is helpful.

1 Like
28

Hey everyone,

I’ve been experiencing the issue where typing a message in the Antigravity chat would immediately “complete” without actually sending it to the LLM too. The agent just wouldn’t respond at all.

Root cause: If you use Claude Code (or anything that creates git worktrees), it adds this to your .git/config:

[extensions]
    worktreeConfig = true

…and bumps core.repositoryformatversion from 0 to 1. This breaks Antigravity v1.21.x’s workspace/agent communication — the agent can’t properly resolve the workspace context and silently fails.

How to confirm this is your issue:

  • Chat works fine in other workspaces/directories

  • Your project’s .git/config contains worktreeConfig = true

Fix (run in your project directory):

git worktree prune
git config --unset extensions.worktreeConfig
git config core.repositoryformatversion 0

Then restart Antigravity. Chat should work immediately.

Optional cleanup: If you also have large .next/dev/cache or similar build caches, removing those can help with indexing performance too.

Hope this helps someone — took me a while to track down! :slightly_smiling_face:

29

Hello everyone!
Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.

To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.

1 Like
30

this worked for me :slight_smile:

1 Like
31

Thank you man! As soon as I ran “git config --unset extensions.worktreeConfig” in my terminal, the Agent started working. I started facing the issue as soon as I opened my project in Codex.