I found a reproducible startup issue in Antigravity.
Error
Antigravity repeatedly logs the following on startup:
Failed to update user status Error: LanguageServerClient must be initialized first!
What makes this reproducible
I fully reset local cache and extension storage, then launched Antigravity again.
The error still appeared in a brand new log session.
Steps already performed
-
fully terminated Antigravity processes
-
removed:
-
AppData\Roaming\Antigravity\Cache -
AppData\Roaming\Antigravity\CachedData -
AppData\Roaming\Antigravity\Service Worker\CacheStorage -
AppData\Roaming\Antigravity\User\globalStorage\google.antigravity -
AppData\Roaming\Antigravity\User\workspaceStorage
-
-
launched Antigravity again
Result
The issue reproduced immediately in a fresh log directory:
C:\Users\USER\AppData\Roaming\Antigravity\logs\20260306T123111
Additional findings
Earlier logs also showed that the language server itself starts successfully afterward, which suggests this is likely an initialization order / race condition rather than a broken login.
I did not find evidence of:
-
401 -
403 -
unauthenticated -
missing token -
failed to set auth token
Expected behavior
User status should only be updated after LanguageServerClient has been fully initialized.
Actual behavior
Antigravity attempts to update user status too early during startup, causing repeated errors and likely incorrect status / plan / quota display.
Please investigate startup sequencing around:
-
user status update
-
language server client initialization
-
extension activation order
Thank you.