[Bug]: Antigravity oauth-personal sign-in reports success on Windows, but sessions stay "not logged in" (login not found under the provider's GEMINI_HOME)

Ouverte
#39,778 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
49/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript

Piste de recherche

Start in the apps/server area named in the report and trace AntigravityDriver.codeLogin alongside antigravityEnvironment, which sets GEMINI_HOME for sessions. Compare the child process environment and credential storage with the successful default-home agy run, then reproduce using the managed Windows CLI. Done means successful sign-in is visible to new Antigravity sessions and the provider status reports checked access with models available.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Before submitting
  • I searched existing issues and did not find a duplicate. (Related but different: #36033 is Linux with no usable keyring; #39620 is oauth-business.)
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Windows 11, T3 Code 0.1.11 running as the background service (t3 service install), Antigravity provider with authMethod: oauth-personal, managed runtime (binary path empty).
  2. Settings → Providers → Antigravity → Retry installation (managed runtime updates to Antigravity CLI 1.5.13).
  3. Sign in → Open browser → choose the Google account → Sign in → copy the code from antigravity.google/oauth-callback → paste into "Code from the Antigravity page" → Connect.
  4. Start any thread on the Antigravity provider (e.g. via MCP t3_thread_launch, model gemini-4-neon-high).
Expected behavior

After a successful sign-in, Antigravity sessions are authenticated.

Actual behavior
  • The trace shows AntigravityAuth.respond and AntigravityAuth.runSignIn both ending in Success.
  • Every new session still fails: ProviderAdapterOpenSessionError: Failed to open antigravity provider session, caused by AcpRequestError: No browser is available here (this is a remote (SSH) session …). Run agy acp --login ….
  • The ACP log under <profileDirectory>/antigravity-acp/log/ says error getting token source: You are not logged into Antigravity.
  • Provider status stays at "Google account access is not checked yet", with 0 models. Restarting the service does not help.
Impact

Major degradation or frequent failure

Version or commit

T3 Code 0.1.11 (desktop and service), managed Antigravity CLI 1.5.13

Environment

Windows 11 (x64), background service (t3code-<host>-<user> scheduled task), Windows Credential Manager available.

Logs or stack traces

Isolation test with the managed agy.exe from ~/.t3/tools/antigravity-acp/win32-x64/versions/<id>/agy.exe, running agy -p "Reply with exactly: AUTH OK":

Environment Result
GEMINI_HOME=<profileDirectory> + AGY_ACP_FORCE_FILE_STORAGE=1 + fake SSH_CONNECTION (as in antigravityEnvironment) not logged in (prompts for an auth code, then times out)
Same, without AGY_ACP_FORCE_FILE_STORAGE not logged in
Default home (GEMINI_HOME unset → ~/.gemini), with or without AGY_ACP_FORCE_FILE_STORAGE=1 AUTH OK (the user's own agy acp --login from a terminal)

So the Google credentials themselves are fine, and the CLI looks up its login per home folder. The agy acp --login run by AntigravityDriver.codeLogin exits 0, but afterwards nothing new exists under <profileDirectory> (no new files in antigravity-cli/ or antigravity-acp/). The sessions then run with that GEMINI_HOME and find no login. It looks like the code-login child either persists the login somewhere the session runtime doesn't read, or with a different home/storage than antigravityEnvironment gives the sessions.

GEMINI_HOME is set after the instance's environment variables in antigravityEnvironment, so a user cannot work around it from provider settings.

Workaround

Run Gemini through the Codex provider via an OpenAI-compatible proxy (google-antigravity/gemini-4-neon). The native Antigravity provider stays unusable.

Langage dominant
TypeScript
Étoiles
24.8k
Forks
6.4k
Merge moyen
4 h 29 min
PR mergées (30 j)
488

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pingdotgg/t3code

Toutes les issues de pingdotgg/t3code

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.