Antigravity agent becomes unresponsive when Git repository has extensions.worktreeConfig=true

Google Antigravity
1 
## Title

Antigravity agent becomes unresponsive when Git repository has `extensions.worktreeConfig=true`

## Environment

- macOS Apple Silicon
- Antigravity 1.107.0
- Workspace: Git repository with `core.repositoryformatversion=0` and `extensions.worktreeConfig=true`
- Opened folder: nested folder inside the repository

## Symptoms

- Agent chat accepts the message, but does not respond. The conversation appears stuck.
- Network and auth are OK.
- Restarting or signing in again does not fix the issue until the Git config is changed.

## Relevant Logs

```text
core.repositoryformatversion does not support extension: worktreeconfig
Failed to resolve workspace infos, continuing without: core.repositoryformatversion does not support extension: worktreeconfig
workspace infos is nil
agent state for conversation ... not found

Steps to Reproduce

  1. On macOS, open a Git repository in Antigravity.

  2. Enable Git worktree config extension in that repository:

    git config extensions.worktreeConfig true

  3. Open a project folder inside that repository in Antigravity.

  4. Start a new Antigravity agent/chat session.

  5. Send any prompt, for example:

    Please inspect this workspace and summarize the project.

  6. Observe that the message is accepted, but the agent does not produce a normal response or appears stuck.

  7. Check Antigravity logs. The language server reports errors similar to the logs above.

  8. As a workaround, remove the Git config entry:

    git config --unset extensions.worktreeConfig

  9. Restart Antigravity language server or reload the Antigravity window.

  10. Start a new agent/chat session again. The agent responds normally.

Workaround

git config --unset extensions.worktreeConfig

Then restart the Antigravity language server or reload the window.

Expected Behavior

Antigravity should either support Git worktreeConfig or gracefully ignore it instead of failing workspace info resolution and breaking agent sessions.

Additional Issue

The built-in feedback form also hangs on Submit, so I am reporting this here instead.

After restarting Antigravity, the issue submission form still hangs on Submit. Logs show the UI continues requesting an old local language-server HTTP port:

http://localhost:55486/proxy/unleash/client/features

But the current language server is listening on a different port, for example:

55533

No request to Issue Tracker / Buganizer appears in logs after clicking Submit.