Bug Report: Antigravity Agent/Executor fails to initialize in Remote SSH environment (stuck in Loading/Authenticating)

[coldstork]

1. Summary of the issue: In a local environment, Antigravity works perfectly
   with Gemini 3.1 Pro and Claude models. However, when connecting to a remote
   Linux server via SSH, the AI Agent remains stuck in the “Loading” or
   “Generating” state. The console reports executor is not currently running and
   command ‘antigravity.xxx’ not found.

2. Environment:

• Local OS: Windows 10/11
• Remote OS: Linux (Ubuntu/CentOS)
• IDE Version: Antigravity (latest build)
• Proxy Setup: SSH Remote Port Forwarding (RemoteForward 7897 127.0.0.1:7897).
  Local proxy is Clash Verge with TUN mode enabled.

3. Steps to Reproduce:

4. Establish an SSH tunnel for port 7897.

5. Connect to the remote server using Antigravity’s SSH extension.

6. Configure Http: Proxy to http://127.0.0.1:7897 in Remote settings.

7. Attempt to start a conversation in the AI chat panel.

8. Observed Behavior:

• The terminal can successfully access Google via proxy (verified by curl -I
  https://www.google.com returning HTTP 200).
• The AI panel shows “Generating…” indefinitely.
• The bottom status bar frequently shows “Antigravity: Authenticating”.
• Console Logs: ERR [unknown] executor is not currently running: ConnectError,
  ERR command ‘antigravity.isFileIgnored’ not found.

5. Comparison: On the same server with the same SSH tunnel, Kiro IDE (a similar
   fork) works perfectly and can call Claude models without issues. This suggests
   the issue is specific to the Antigravity Remote Agent’s initialization or
   authentication logic.

6. Expected Behavior: The remote agent should successfully initialize and
   utilize the established SSH tunnel for model requests and authentication.