Antigravity IDE 2.5.5 Agent Fails Due to a Compatibility Issue with SentinelOne

Google Antigravity
1

For reference, I am still using Antigravity IDE version 1.23.2.

For some time, I could not determine why the agent stopped working whenever I installed Antigravity IDE 2.5.5. I have now identified what appears to be the cause.

Antigravity IDE 2.5.5 installs successfully. However, the agent fails because of a compatibility conflict between SentinelOne—the security software installed on my office PC—and Antigravity’s bundled language server.

The observed sequence is as follows:

  • Antigravity IDE 2.5.5 installs successfully.
  • The agent attempts to start language_server_windows_x64.exe.
  • SentinelOne injects InProcessClient64.dll into the language-server process.
  • The Go runtime encounters stack corruption.
  • The process reports: fatal error: unknown caller pc
  • The language server exits with code 2.
  • As a result, the IDE itself opens normally, but the agent does not respond.

I am not suggesting that SentinelOne itself is defective. More specifically, this appears to be a compatibility issue between SentinelOne Agent 24.1.5.277 and the language server bundled with Antigravity IDE 2.5.5.

Because this is a company-managed office PC, I cannot disable SentinelOne or modify its security policy myself. For now, I have uninstalled version 2.5.5 and returned to version 1.23.2, which still works.

Could the Antigravity team please investigate this compatibility issue or provide a supported workaround? If additional crash logs or diagnostic information are required, I would be happy to provide them.

Any help would be greatly appreciated.

2

Hi @youngmin ,

Thank you for reporting.

The root cause for the issue is :

In Antigravity IDE v2.1.x–v2.5.5 on Windows, the Go language server (language_server_windows_x64.exe / language_server.exe) compiles a large regex table (enry/data.init()) at startup, triggering a concurrent Go Garbage Collector stack scan (runtime.scanstack). When SentinelOne (InProcessClient64.dll) injects into the process, Go’s stack unwinder hits an unrecognized frame offset inside enry/data.init() and crashes with fatal error: unknown caller pc (exit code 2).

Could you please follow the below recommended steps:

Approach 1: Delay Go GC Stack Scanning at Startup (GOGC=2000)

Raising the initial GC threshold prevents runtime.scanstack from running until after enry/data.init() finishes and pops off the call stack. Run in PowerShell, then fully restart Antigravity IDE:

[System.Environment]::SetEnvironmentVariable("GOGC", "2000", "User")
[System.Environment]::SetEnvironmentVariable("GODEBUG", "asyncpreemptoff=1", "User")

Approach 2: Use the Working v1.23.2 Binary or Roll Back (Confirmed Working)

Since v1.23.2 do not hit this crash on your machine:

  • Binary Swap: Copy language_server_windows_x64.exe from a working v1.23.2 install into your v2.5.5 folder (%LOCALAPPDATA%\Programs\Antigravity\resources\app\extensions\antigravity\bin\ or %LOCALAPPDATA%\Programs\antigravity\resources\bin\language_server.exe).

  • Or Roll Back: Reinstall v1.23.2 and add “update.mode”: “none” to %APPDATA%\Antigravity\User\settings.json to pause auto-updates until the patched release is out.

Approach 3: Use WSL2 or a SentinelOne Interoperability Exclusion

  • WSL2 (No Admin Required): Open your project inside a WSL2 environment in Antigravity IDE, which runs the Linux language_server binary inside WSL2 and bypasses Windows InProcessClient64.dll injection entirely.

  • SentinelOne Admin Exclusion: Ask your IT administrator to add a SentinelOne Path Exclusion in Interoperability (Disable DLL Injection) mode for %LOCALAPPDATA%\Programs\Antigravity\ (standard file scan exclusions do not stop DLL injection).

3

Hi @Rebbanpalli_Naveen

Thank you so much for the detailed response and solutions.
I will definitely try out the approaches you suggested, and I really hope this solves the issue!

Currently, we are on the Chuseok holiday (Korean Thanksgiving) here in South Korea, and the office PC I need to test this on is at my workplace. I will try your suggestions first thing next Monday as soon as I am back in the office. I am really looking forward to it!

Thank you so much once again for your kind help. I will keep you updated with the results as soon as I test them out.

Best regards,
Youngmin