Critical Bug: Antigravity Server/AI Agent Crashes Immediately Language Server Client Initialization Failure

Google Antigravity
,
1

I am not able to use the product. I downloaded the antigravity latest version just a day ago when started facing this

Issue Summary

The Antigravity extension fails to initialize the LanguageServerClient, which prevents the AI agent/chat interface from loading. The extension activates but cannot complete initialization, resulting in undefined command errors and a non-functional agent panel.

[Here is how the UI look

Screenshot 2026-02-23 115152
Screenshot 2026-02-23 1151523826Ă—2061 243 KB

Symptoms

Users experience the following when opening Antigravity:

  1. Antigravity IDE opens but the chat/agent panel shows no content or displays an error

  2. Menu items referencing Antigravity commands are greyed out or produce errors:

    • antigravity.importAntigravitySettings
    • antigravity.importAntigravityExtensions
    • antigravity.prioritized.chat.open

  3. The following error appears repeatedly in renderer logs every 60 seconds:

    [error] [Extension Host] Failed to update user status
Error: LanguageServerClient must be initialized first!

  4. No indication in the UI that the language server failed to start

Root Cause Analysis

Primary Issue

The LanguageServerClient singleton is never initialized when the Antigravity extension activates.

Error Trace

From renderer.log (lines 24-31):

2026-02-23 10:59:44.039 [error] [Extension Host] Failed to update user status
Error: LanguageServerClient must be initialized first!
  at R.getInstance (c:\Users\user\AppData\Local\Programs\Antigravity\resources\app\extensions\antigravity\dist\extension.js:2:1106230)
  at a.updateUserStatus (c:\Users\user\AppData\Local\Programs\Antigravity\resources\app\extensions\antigravity\dist\extension.js:2:1195683)
  at a.restartUpdateLoop (c:\Users\user\AppData\Local\Programs\Antigravity\resources\app\extensions\antigravity\dist\extension.js:2:1196174)
  at t.activate (c:\Users\user\AppData\Local\Programs\Antigravity\resources\app\extensions\antigravity\dist\extension.js:2:710004)

Key observation: The error occurs during t.activate() in the extension’s activation sequence, specifically when trying to access LanguageServerClient.getInstance() before it has been initialized.

Timeline of Events

10:59:39.835 - google.antigravity extension activation starts
10:59:44.039 - LanguageServerClient.getInstance() throws error (5 seconds into activation)
10:59:43.255 - Extension host becomes unresponsive (before error)
10:59:43.557 - Extension host becomes responsive again
10:59:44.039 - First LanguageServerClient error logged
11:00:41.315 - Same error repeats (every 60 seconds)
11:01:41.320 - Error repeats
11:02:41.323 - Error repeats

Secondary Issue

Multiple stale Antigravity processes remain running even after closing the application, consuming system resources and potentially interfering with new launches:

  • Observed: 24 Antigravity.exe processes (PIDs: 2948, 6708, 4884, 852, etc.)
  • Memory usage: 45MB - 242MB per process
  • These processes do not respond to normal termination and require forced kill

Steps to Reproduce

Minimum Reproduction Steps

  1. Launch Antigravity IDE for the first time or after clearing cache
  2. Wait for IDE to fully load (up to 3 minutes for full initialization)
  3. Observe the chat/agent panel
    • Expected: Agent interface loads and is ready for interaction
    • Actual: Agent panel is blank or shows error; no chat functionality available

How to Verify the Bug

Check the logs at: C:\Users\user\AppData\Roaming\Antigravity\logs\<latest_timestamp>\window1\renderer.log

Look for these errors:

[error] [Extension Host] Failed to update user status Error: LanguageServerClient must be initialized first!

If this error appears repeatedly every 60 seconds, the bug is present.

Full Reproduction Scenario

  1. Close Antigravity completely
  2. Delete/clear: C:\Users\user\AppData\Roaming\Antigravity\logs and CachedData
  3. Launch Antigravity
  4. Observe chat panel does not load
  5. Check logs - find repeated LanguageServerClient initialization errors
  6. Try to use Antigravity commands - they will be undefined
  7. Close Antigravity - observe 20+ processes remain in Task Manager
  8. Attempt to relaunch - may fail due to stale processes

Expected Behavior

  1. On launch: LanguageServerClient should be initialized during extension activation
  2. During startup: Logs should show successful client initialization before extension completes activation
  3. After startup: Chat/agent panel should be fully functional and ready for use
  4. On close: All Antigravity processes should terminate cleanly with no stragglers

Actual Behavior

  1. On launch: LanguageServerClient initialization is skipped or fails silently
  2. During startup: Extension tries to use uninitialized client, producing errors
  3. After startup: Agent panel does not load, chat is unavailable
  4. On close: Multiple Antigravity processes remain in memory (24+ observed)
  5. Repeated errors: Same initialization error repeats every 60 seconds in logs

Environment Information

Please provide when reporting:

  • OS: Windows 11 Pro 10.0.26200
  • Antigravity Version: 1.18.4
    VSCode OSS Version: 1.107.0 (user setup)
    Commit: c19fdcaaf941f1ddd45860bfe2449ac40a3164c2
    Date: 2026-02-20T22:30:09.460Z
    Electron: 39.2.3
    Chromium: 142.0.7444.175
    Node.js: 22.21.1
    V8: 14.2.231.21-electron.0
    OS: Windows_NT x64 10.0.26200
    Language Server CL: 873063495
  • System RAM: 24 GB
  • Number of Extensions Installed: 0
  • Extensions that might affect startup:
    • GitHub Copilot
    • GitHub Copilot Chat
    • Remote SSH/Dev Containers

Log Files Required for Investigation

When reporting this bug, please include:

  1. renderer.log - Contains the LanguageServerClient error trace

    • Location: C:\Users\user\AppData\Roaming\Antigravity\logs\<timestamp>\window1\renderer.log
    • Look for lines containing “LanguageServerClient must be initialized first”

  2. exthost.log - Shows extension activation sequence

    • Location: C:\Users\user\AppData\Roaming\Antigravity\logs\<timestamp>\window1\exthost\exthost.log
    • Look for google.antigravity activation timestamps

  3. main.log - Overall IDE startup sequence

    • Location: C:\Users\user\AppData\Roaming\Antigravity\logs\<timestamp>\main.log

  4. Antigravity.log - Extension-specific logs (if any)

    • Location: C:\Users\user\AppData\Roaming\Antigravity\logs\<timestamp>\window1\exthost\google.antigravity\Antigravity.log

Possible Root Causes

  1. Initialization Race Condition: LanguageServerClient is being accessed before its initialize() method completes

    • The extension’s activate() method calls updateUserStatus() which immediately tries to get the client singleton
    • The singleton may not have been created yet

  2. Missing Initialization Hook: The LanguageServerClient’s static initialization may not be happening during extension activation

    • Check if there’s an initialization step that’s being skipped

  3. Async/Promise Issue: The language server initialization is async but the code treats it as synchronous

    • getInstance() may be called before the async initialization promise resolves

  4. Dependency Order: Dependencies are loaded in wrong order during extension activation

    • LanguageServerClient should be fully initialized before extension code calls getInstance()

Workaround (Temporary)

Until this is fixed:

  1. Force close all Antigravity processes: taskkill /IM Antigravity.exe /F
  2. Clear cache and logs: rm -rf ~/AppData/Roaming/Antigravity/logs ~/AppData/Roaming/Antigravity/CachedData
  3. Clear browser cache: rm -rf ~/AppData/Roaming/Antigravity/{Cache,GPUCache,"Code Cache",Crashpad}
  4. Relaunch Antigravity
  5. Note: This is not a permanent fix, just a temporary reset

Impact Assessment

  • Severity: Critical
  • Scope: All users affected - agent/chat functionality completely unavailable
  • Frequency: Consistent - occurs on every launch
  • User Impact: Core AI agent feature is completely non-functional

Made using Claude and antigravity logs.

1 Like