Existing issues
What happened?
On Windows 11, the Antigravity provider reports that the local language server is not running even though the native Antigravity desktop app is open, signed in, and its language_server.exe process is listening on loopback ports.
The provider fails during discovery in both auto mode and when the CLI source is forced.
Expected: Win-CodexBar detects the active local Antigravity language server and shows usage.
Actual: The provider displays:
Provider not installed: Antigravity language server not running. Start Google Antigravity and sign in, then retry.
Affected area
Steps to reproduce
-
Install Win-CodexBar and Google Antigravity natively on Windows 11.
-
Sign in to Antigravity, open a workspace, and leave the desktop app running.
-
Enable Antigravity in Win-CodexBar and refresh the provider.
-
Run:
$cli = "$env:LOCALAPPDATA\Programs\CodexBar\codexbar-cli.exe"
& $cli diagnose --provider antigravity --pretty --no-color
-
Observe the false “language server not running” result.
Logs, screenshots, or recordings
2026-07-10T21:35:39.697135Z WARN codexbar::providers::antigravity: Antigravity probe failed: Provider not installed: Antigravity language server not running. Start Google Antigravity and sign in, then retry.
{
"provider": "antigravity",
"source": null,
"source_mode": "auto",
"auth": {
"configured": false,
"modes": ["cli_supported"]
},
"usage": null,
"fetch_attempts": [
{
"kind": "auto",
"was_available": false,
"error_category": "config"
}
],
"error": {
"category": "config",
"message": "Provider not installed: Antigravity language server not running. Start Google Antigravity and sign in, then retry."
},
"settings": {
"enabled": true,
"source_mode": "auto",
"supported_sources": ["auto", "cli"]
}
}
Additional local evidence (no credentials included):
- Win-CodexBar:
codexbar 0.41.3
- Native Antigravity
language_server.exe is running from %LOCALAPPDATA%\Programs\Antigravity\resources\bin\language_server.exe.
- That process listens on
127.0.0.1:53084 and 127.0.0.1:53085.
- Its command line includes both a CSRF-token flag and the Antigravity app-data marker.
agy.exe is also available on the native Windows PATH.
- Forcing
--source cli yields the same error.
Existing issues
What happened?
On Windows 11, the Antigravity provider reports that the local language server is not running even though the native Antigravity desktop app is open, signed in, and its
language_server.exeprocess is listening on loopback ports.The provider fails during discovery in both
automode and when the CLI source is forced.Expected: Win-CodexBar detects the active local Antigravity language server and shows usage.
Actual: The provider displays:
Affected area
Steps to reproduce
Install Win-CodexBar and Google Antigravity natively on Windows 11.
Sign in to Antigravity, open a workspace, and leave the desktop app running.
Enable Antigravity in Win-CodexBar and refresh the provider.
Run:
Observe the false “language server not running” result.
Logs, screenshots, or recordings
Additional local evidence (no credentials included):
codexbar 0.41.3language_server.exeis running from%LOCALAPPDATA%\Programs\Antigravity\resources\bin\language_server.exe.127.0.0.1:53084and127.0.0.1:53085.agy.exeis also available on the native Windows PATH.--source cliyields the same error.