Repository navigation
[Bug]: Antigravity Provider Google Sign-in not working #9405
Description
Activity
- addedbugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.
on Sep 3, 2026 I too have this issue
same issue
Same Problem
Anyone found a solution?
+1 same issue
My PR fix this, just wait the team wake up to check
Reacted by Ralph Lee and Pasindu SadaminaReacted by Gorlik, Tristan, Ayoub Ziane and Pasindu Sadaminasomeone should wake them up
Additional reproduction and diagnostics from another Windows 11 user:
Environment
- OS: Windows 11 25H2
- T3 Code: 0.0.39-nightly.20260903.1272 (d5825e1)
- Antigravity provider: managed runtime installed by T3 Code
- Managed ACP runtime: agy_acp_server_20260818_01_RC01
- Browser: Vivaldi, registered as the default HTTP/HTTPS browser
Reproduction
- Enable Antigravity in Settings > Providers.
- Install the managed Antigravity runtime.
- Click Sign in with Google / Retry Google sign-in.
- No browser window opens.
- The UI does not show Open sign-in page or Copy sign-in link.
- After waiting, authentication fails.
Observed diagnostics
The managed runtime starts and ACP initialization succeeds. During the sign-in attempt, T3 records successful:
- ProviderAuthService.start
- ws.rpc.provider.auth.start
- antigravityAuthSupport.handleStdoutLine
- offerOutgoing
However, no external browser launch is recorded and no complete authentication URL is exposed in the server or desktop logs. The local ACP authentication endpoint on 127.0.0.1 returns:
Authentication failed
After approximately three minutes, T3 fails with:
Error: Onboarding failed: The authentication flow did not complete successfully.
The local agy.exe CLI is installed and runs, but it does not expose an agy login subcommand. Signing in through the CLI/IDE is not a workaround because the T3-managed Antigravity provider keeps its own credentials.
Suspected failure
The ACP server appears to emit/process the Google authentication URL, but the URL is lost between the T3 server outgoing event and the desktop/web provider UI. The expected Open sign-in page / Copy sign-in link fallback is never rendered, so the callback cannot be completed.
Please investigate the Antigravity ACP auth URL handoff from handleStdoutLine / offerOutgoing to the provider UI and browser-opening fallback.
Reacted by Egor KharitonovSAme problem
they havent even fixed it in the new release. crazy
Reacted by Ayoub Ziane
Before submitting
Area
apps/desktop
Steps to reproduce
After installing antigravity on the provider menu , Click Google Sign-in
Expected behavior
Google sign-in to succeeds and the agy provider starts working
Actual behavior
Clicking on google sign-in hang like this for about 10 - 15 minutes before expiring
Impact
Blocks work completely
Version or commit
0.0.39-nightly.20260903.1268
Environment
Windows 11 25H2
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response