Bug Report: "Sign in with Google" button fails to open browser — agentSessions service not registered (Antigravity v1.20.5)

Google Antigravity
1

subject: Bug Report: Sign in with Google does not open browser in Antigravity IDE v1.20.5

Hello Antigravity / Google Developer Tools Team,

I am writing to report a critical authentication bug in Antigravity IDE that makes it impossible to sign in with Google.

Environment

  • Product: Antigravity IDE

  • Version: 1.20.5 (app version 1.107.0)

  • Commit: 4603c2a412f8c7cca552ff00db91c3ee787016ff

  • OS: Windows 11

Summary

Clicking the “Sign in with Google” button does nothing. No browser window ever opens, so the OAuth flow cannot complete. As a result, the Go language server repeatedly throws state syncing error: key not found and the IDE cannot be used.

Steps to Reproduce

  1. Install Antigravity IDE v1.20.5 on Windows 11

  2. Launch the IDE

  3. Click “Sign in with Google” in the authentication prompt

  4. Observe: no browser opens, no error is shown to the user, and the button appears to do nothing

Technical Investigation

I collected detailed trace logs by launching the IDE with the --log trace flag and analyzed main.log, renderer.log, and exthost.log. The following root cause chain was identified:

Finding 1 — openExternal is never called In main.log, no call to openExternal occurs at any point after the sign-in button is clicked. This confirms the browser-opening code path is never reached.

Finding 2 — DI container error in renderer.log Approximately 8 seconds after the sign-in click, the renderer process logs the following error:

[error] [createInstance] xoe depends on UNKNOWN service agentSessions.

This means the component responsible for the sign-in flow (xoe) fails to instantiate because the agentSessions service has not been registered in the dependency injection container.

Finding 3 — agentSessions service is never registered The service token is defined in workbench.desktop.main.js as:

js

var pbt = Wt("agentSessions");
```
However, a search of all bundled extension `package.json` files shows that **no extension declares the `chatSessionsProvider` capability**, which is required to register this service. The service appears to be conditionally registered in the workbench core, but the condition is never met (likely a missing or disabled feature flag).

**Finding 4 — OAuth token is empty in storage**
Inspection of `%APPDATA%\Antigravity\User\globalStorage\state.vscdb` (SQLite) shows:
```
antigravityUnifiedStateSync.oauthToken = [EMPTY]
antigravityAuthStatus = null
```
Because the OAuth flow never completes, the Go language server finds no token and throws:
```
state syncing error: key not found

Root Cause Summary

The agentSessions DI service is not registered at workbench startup. The sign-in component (xoe) depends on this service. When instantiation of xoe fails, the code path that calls openExternal (to open Chrome with the Google OAuth URL) is never reached. The user sees no feedback and the IDE is effectively unusable without an authenticated session.

Request

Could you please investigate why the agentSessions service is not being registered on Windows in v1.20.5? It appears this may be controlled by a feature flag (the Unleash proxy at http://localhost:12674/proxy/unleash/client/features was not reachable in my environment). If there is a workaround — such as a configuration flag, manual token injection, or a patched build — I would greatly appreciate guidance.

Thank you for your time and for the work on this tool.

Best regards,