Language server startup timeout on remote HPC environment

Google Antigravity
1

Hi Antigravity Community

I’m running into a language server startup timeout in a remote HPC session. Antigravity (1.20.6) connects to the remote host and starts the extension host, but the language server never becomes ready and times out after about 60 seconds.

log lines:

2026-03-24 22:28:39 [info] Extension host agent started.

2026-03-24 22:28:40 [info] Launched Extension Host Process.

2026-03-24 22:29:42 [error] Failed to start language server: Timed out waiting for language server start

2026-03-24 22:29:42 [error] LS startLanguageServer error: Timed out waiting for language server start

What I checked so far:

  • python3 is available and works normally

  • localhost binding works

  • starting a local HTTP server on 127.0.0.1 works

  • curl to that local server also works

  • ~/.antigravity-server/data/logs/…/remoteagent.log is present and shows the remote extension host starting normally

  • the timeout seems to happen after the extension host is already up, during language server initialization

Has anyone seen this on a remote Linux/HPC setup?

I’m mainly trying to understand whether this is usually caused by:

  • the Python environment not being detected correctly

  • workspace size or indexing

  • something specific to remote HPC sessions

Any help would be highly appreciated.

Thank you.