[Bug Report] Antigravity Server Crashes on Remote SSH — Missing AVX2 CPU Support on QEMU VPS

Google Antigravity
1

Summary

Antigravity IDE server crashes immediately when connecting via Remote SSH to a VPS running on a QEMU virtual CPU that does not support AVX/AVX2 instructions. The error manifests as Exit Code 132 and a kernel “invalid opcode” trap, indicating the server binary was compiled with AVX2 instructions not available on the host CPU.

Additionally, the bundled securecoder extension is missing its compiled output (out/extension.js), causing a secondary activation failure.

Environment

  • Antigravity IDE version: 2.0.1 (build bf9a033f)
  • Client OS: macOS (Apple Silicon)
  • Remote server: Ubuntu Linux, VPS on Exabytes (QEMU/KVM)
  • Remote CPU flags: SSE, SSE2 only — no AVX, no AVX2
  • Remote RAM: 7.5 GB (3.5 GB available)
  • Remote glibc: 2.39

Steps to Reproduce

  1. Install Antigravity IDE 2.0.1 on macOS
  2. Connect via Remote SSH to a VPS with a QEMU virtual CPU (SSE2 only, no AVX2)
  3. Antigravity IDE server is installed on the remote server automatically
  4. Connection fails immediately with “Antigravity server crashed unexpectedly”

Expected Behavior

Antigravity IDE server should run on standard QEMU VPS environments, as VS Code and Cursor do on the same server without issues.

Actual Behavior

  • Server process exits immediately with Exit Code 132
  • Kernel log shows: traps: antigravity-ser[PID] trap invalid opcode
  • remoteexthost.log shows: Language server has not been started!
  • Extension Google.securecoder fails with: Cannot find module ‘…/securecoder/out/extension.js’

Relevant Logs

remoteexthost.log:
2026-05-20 15:34:16.239 [error] Activating extension Google.securecoder failed due to an error:
Error: Cannot find module ‘…/securecoder/out/extension.js’
2026-05-20 15:34:19.815 [error] Language server has not been started!

CPU flags:
$ grep flags /proc/cpuinfo | head -1 | tr ’ ’ ‘\n’ | grep -E “avx|sse”
sse
sse2
(no avx or avx2 present)

Root Cause Hypothesis

The Antigravity server binary appears to be compiled with AVX2 instruction requirements. When executed on a QEMU virtual CPU that only exposes SSE/SSE2 flags, the process triggers an illegal instruction fault (SIGILL), resulting in Exit Code 132. VS Code and Cursor run on this same machine without issues, suggesting those binaries do not require AVX2.

Bug #2 — securecoder extension missing compiled output

The securecoder extension installed at ~/.antigravity-ide-server/…/extensions/securecoder/ contains only package.json, plugins/, and static/. The out/ directory and extension.js are absent. Manual npm run bundle fails because src/extension.ts is also not included in the distributed package.

Suggested Fix

  1. Recompile the Antigravity server binary without mandatory AVX2 instructions (or provide a fallback binary for non-AVX2 CPUs), matching the approach used by VS Code.
  2. Include the compiled out/extension.js in the securecoder extension bundle distributed to remote servers.