Unable to send messages in Agent/Chat console on latest version (Chat UI unresponsive)

Google Antigravity
1

After updating to the latest version of Antigravity IDE, the Agent/Chat interface has stopped processing user input. When typing a prompt into the chat box and hitting Enter (or clicking the send button), nothing happens—no message appears in the conversation thread, no loading indicator is triggered, and no output is generated.

Steps Taken So Far:

  • Completely uninstalled and reinstalled the application.

  • Cleared local project and session cache directories (.antigravity, .jetski, .cortex).

  • Verified Language Server execution (language_server_windows_x64.exe is running and bound to local ports).

  • Tested across multiple projects and clean workspaces.

The chat input UI accepts text normally, but submitting the message results in zero feedback or activity in the chat stream.

2

Hi @XtarlinG,

Could you please follow these steps:

  1. Clear Global App UI Cache (Close Antigravity first):

    • Windows (PowerShell):

      Remove-Item -Recurse -Force "$env:APPDATA\Antigravity\Local Storage", "$env:APPDATA\Antigravity\IndexedDB"

    • Linux / macOS:

      rm -rf ~/.config/Antigravity/"Local Storage" ~/.config/Antigravity/IndexedDB

  2. Remove Stale IPC Socket Locks:
    Delete %USERPROFILE%\.gemini\antigravity-ide\ipc (or ~/.gemini/antigravity-ide/ipc/ on Linux/macOS).

  3. Reset & Reload:
    Relaunch the IDE, press Ctrl+Shift+P (or Cmd+Shift+P), and run:

    • Antigravity: Reset Chat Panel Webview
    • Developer: Reload Window

(Also check that your workspace is not locked in Restricted Mode (Workspace Trust) in the status bar).

Let me know is the issue resolves or the issue still persists.

3

It’s not working, it’s still the same. When I try to send a message, nothing happens.

Details:
Version: IDE v2.5.5 on Windows

Error: "No LS client info found for local authority" → Language Server timeout

Key Log: The LS opens ports and successfully connects to the extension server, but it never publishes LsClientMachineInfos to the USS, triggering a 60-second timeout.