You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Antigravity login no longer triggers Google's phone-verification step. The authorize request used the v1 endpoint (/o/oauth2/auth) plus a PKCE code_challenge — a shape no Cloud Code Assist desktop client sends, and one Google's consent screen answers with an SMS challenge for this client. Side-by-side with a working third-party router showed the difference: the v2 authorize endpoint and no PKCE at all, the client secret authenticating the exchange instead. OmniProxy now sends exactly that shape (/o/oauth2/v2/auth, no code_challenge/code_verifier), and a test pins it — endpoint, absent PKCE params, required params — so a regression cannot silently bring the verification step back.
Cancelling an Antigravity login right after starting it could panic the process. The callback server goroutine read session.server at run time while abort() nils that field on cancel, so the two could race into Serve on a nil *http.Server. The new shape test tripped it on its first run (start then deferred cancel); the server is now captured in a local before the goroutine spawns.