[Critical Bug] Antigravity Remote Agent Crash: Command Not Found & Language Server Timeout in SSH Environment

[coldstork]

1. Context & Verification (Proof of Network) I am using Antigravity in a Remote
   SSH environment.

• Local: Windows 10/11 with Clash Verge (TUN Mode Enabled).
• Remote: Linux Server connected via SSH.
• Proxy Method: SSH Remote Port Forwarding
  (RemoteForward 7897 127.0.0.1:7897).
• Network Status: The network tunnel is fully operational. Verified by running
  curl -I https://www.google.com in the remote terminal, which returns
  HTTP/2 200 OK.

2. The Issue While Antigravity works perfectly in Local Mode, it consistently
   fails in Remote SSH Mode. Despite the working proxy, the AI chat panel is stuck
   in “Generating” or “Loading” forever.

3. Error Logs (Developer Tools Console): The following critical errors are
   observed:

• ERR [google.antigravity]: Menu item references a command
  ‘antigravity.isFileIgnored’ which is not defined.
• [ERROR]: Failed to start language server: Error: Timed out waiting for
  language server start.
• ERR [unknown] executor is not currently running: ConnectError.
• Antigravity server crashed unexpectedly. Please restart to fully restore AI
  features.

4. Steps Taken to Troubleshoot (All Failed):

• Reinstalled the local Antigravity client.
• Manually deleted the remote server directory (rm -rf ~/.antigravity-server)
  and let the IDE reinstall the agent.
• Configured Http: Proxy to http://127.0.0.1:7897 in Remote Settings.
• Killed all conflicting processes (kiro, node, etc.) on the server.
• Enabled Clash TUN mode to ensure all system-level traffic is captured.

5. Comparative Analysis: On the exact same server and exact same SSH tunnel, the
   Kiro IDE (a similar fork) works flawlessly, correctly identifies the proxy, and
   initializes its AI Agent without any “command not found” errors.

6. Conclusion & Request: The issue lies in how the Antigravity Remote Agent
   initializes its core plugins and commands on the Linux host. It appears the
   antigravity-server binary fails to register its API commands or establish a
   local socket connection with the frontend, possibly due to a pathing error or a
   race condition during the SSH boot sequence.

Please investigate the initialization logic of the executor and language server
in the Remote SSH extension.