[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)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 49/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- authentication, backend
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
- Windows 11, T3 Code 0.1.11 running as the background service (
t3 service install), Antigravity provider withauthMethod: oauth-personal, managed runtime (binary path empty). - Settings → Providers → Antigravity → Retry installation (managed runtime updates to Antigravity CLI 1.5.13).
- 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. - Start any thread on the Antigravity provider (e.g. via MCP
t3_thread_launch, modelgemini-4-neon-high).
Expected behavior
After a successful sign-in, Antigravity sessions are authenticated.
Actual behavior
- The trace shows
AntigravityAuth.respondandAntigravityAuth.runSignInboth ending inSuccess. - Every new session still fails:
ProviderAdapterOpenSessionError: Failed to open antigravity provider session, caused byAcpRequestError: No browser is available here (this is a remote (SSH) session …). Run agy acp --login …. - The ACP log under
<profileDirectory>/antigravity-acp/log/sayserror 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.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 24.8k
- Forks
- 6.4k
- Ø Merge
- 4 Std. 29 Min.
- Gemergte PRs (30 T.)
- 488
Entwicklungsumgebung
Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus pingdotgg/t3code
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
needs more info
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
pingdotgg/t3code#39400 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelEvtl. vergeben @iamdatvt94 hat das vor 1 Tag übernommen. Offenbug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in pingdotgg/t3code
Ähnliche Issues
-
area:plugins kind:bug priority:p2 ready
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
Maintainer antworten meist innerhalb von 1 Tag
-
Escaped `*` followed by `*` (`\**`) never matchesEvtl. vergeben @bardrop hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 71/100
editorconfig/editorconfig-core-js#172 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 63/100
puckeditor/puck#1929 ·
Maintainer antworten meist innerhalb von 1 Tag
-
compression() compresses every response at Brotli quality 11Evtl. vergeben @staylor hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag