Repository navigation
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Related, not duplicates: #34327 (fixed by #38957), #37587 (fixed by #39485), open PRs #36733 and #39544. This is the gap left between #38957 and #39485 for Google-account instances that were already signed in.
Area
apps/server
Steps to reproduce
- On Linux with a working Secret Service keyring (gnome-keyring), use an
oauth-personalAntigravity instance on agy 1.5.13 with T3 Code up to0.1.11-nightly.20261119.4954, signed in with Google. agy keeps the sign-in in the OS keyring: the ACP log sayskeyringAuth: loaded token … ChainedAuth: authenticated via keyring (effective: keyring), and the keyring holdsPassword for 'antigravity' on 'gemini'. - Update to
0.1.11-nightly.20261120.4979(contains fix(server): Antigravity limits read the 1.5.x CLI's stored sign-in #38957 and fix(server): each Antigravity Google sign-in stays in its own instance #39485). - Open Usage → Limits.
Expected behavior
Antigravity's quota windows appear, or T3 tells me the sign-in has to be redone because its storage changed.
Actual behavior
Antigravity is missing from Usage → Limits; only Claude is shown. The provider snapshot is contradictory:
"auth": { "status": "authenticated", "type": "oauth-personal", "label": "Google account" },
"usageLimits": { "windows": [], "unavailable": { "reason": "unsupported", "message": "Sign in with Google to see Antigravity limits." } }The profile <T3 home>/userdata/providers/antigravity/<sha256(instanceId)>/antigravity-acp/ has neither acp_token.json nor antigravity-oauth-token.
Cause, as far as I could trace it in the 4979 bundle
makeAntigravityUsageProbe: with noacp_token.json, it readsantigravity-oauth-token, and falls back toreadCliKeyringSecret(gemini/antigravity) only whenauthMethod === "oauth-business"(fix(server): each Antigravity Google sign-in stays in its own instance #39485). Foroauth-personalit returnsunsupported/ "Sign in with Google to see Antigravity limits."antigravityEnvironmentnow setsSSH_CONNECTIONforoauth-personalso agy stores the sign-in in the profile file. That only takes effect on the next Google sign-in. Before this, agy 1.5.x ignoredAGY_ACP_FORCE_FILE_STORAGEand wrote the Google sign-in to the shared keyring entry.- So for every Google-account instance signed in before fix(server): each Antigravity Google sign-in stays in its own instance #39485, the credential is only in the keyring. The probe will no longer read it, nothing moves it into the profile, and the provider still reports
authenticated. Limits stays empty with no hint that re-signing in is needed.
Suggested fix
One of:
- Migrate once: when an
oauth-personalprofile has noantigravity-oauth-tokenand the provider was signed in before the storage change, mark the instance as needing a fresh Google sign-in, and say so in Settings → Providers and in the Limits notice. Don't keep reportingauthenticated. - Or have the Limits notice say "Sign in again to see Antigravity limits (Antigravity now keeps this instance's sign-in in its own profile)" instead of "Sign in with Google", since the user is already signed in as far as the UI shows.
Impact
Minor bug or occasional failure
Version or commit
0.1.11-nightly.20261120.4979 (server, Linux background service). Antigravity CLI agy 1.5.13 (custom binary path ~/.local/bin/agy).
Environment
Arch Linux (Omarchy), x64, Hyprland, gnome-keyring as Secret Service. Single Antigravity instance, oauth-personal.
Logs or stack traces
auth_store.go:199] Using file-based secret storage at ~/.config/antigravity/plugin-secrets.json
keyring.go:64] keyringAuth: loaded token, expiry=2026-11-20 16:37:19 +0800 CST expired=false
auth.go:157] ChainedAuth: authenticated via keyring (effective: keyring)
Workaround
Not verified yet: sign out of Antigravity and sign in again from Settings → Providers so agy writes antigravity-oauth-token into the profile.
Activity
juliusmarminge commentedon Nov 20, 2026
I tried to reproduce this on the current build and could not.
Commit f2d4df0 (origin/main), agy 1.5.13 (same as the reporter) on PATH, Linux, under headless-desktop (Xvfb + D-Bus + unlocked gnome-keyring). (1) Seeded the shared keyring entry agy 1.5.x used before #39485:
secret-tool store service gemini username antigravitywith {"token":{"access_token":"ya29.SEEDED…","refresh_token":…,"expiry":<now+1h>},"auth_method":"consumer"}, standing in for a Google sign-in made before the storage change. (2) Fresh T3 home with settings.json holding oneantigravityinstance (driver antigravity, authMethod oauth-personal, binaryPath agy). StartedT3CODE_DEV_SEED=0 vp run dev --home-dir <scratch> --no-seed. (3)t3 project add, thent3 thread start --provider antigravity. Observed: the instance profile<home>/userdata/providers/antigravity/<sha256>/antigravity-acp/has no acp_token.json and no antigravity-oauth-token (matches the report). agy's ACP log:Using file-based token storage because SSH session detected→ACP authenticate: methodId="oauth-personal"→authenticate("oauth-personal") failed: No browser is available here (this is a remote (SSH) session…). agy never read the keyring entry. The thread failed. Settings → Providers in the web client showed Antigravity asNot authenticated · Sign in with Google to use Antigravity., notauthenticated. In AntigravityProvider.ts the provider only becomesauthenticatedin onSessionStarted, after a successful session, so an instance whose sign-in is only in the keyring cannot reach the reported state (authenticated + usageLimits unsupported) on main. The reporter'sauthenticated via keyringlog has noSSH session detectedline, which suggests it came from an agy launched before the update. The Usage → Limits panel itself was not viewable here (no Google sign-in on the VM).Closing as not planned. If it still happens for you, reply with the exact steps and the version you are on and it will be looked at again.