[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)
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 49/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- authentication, backend
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- TypeScript
- Estrelas
- 24.8k
- Forks
- 6.4k
- Merge médio
- 4h 29min
- PRs com merge (30d)
- 488
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de pingdotgg/t3code
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
Mantenedores costumam responder em até 1 dia
-
needs more info
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
pingdotgg/t3code#39400 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelTalvez já em andamento @iamdatvt94 assumiu há 1 dia. Abertabug needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
bug needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
Mantenedores costumam responder em até 1 dia
Todas as issues de pingdotgg/t3code
Issues semelhantes
-
area:plugins kind:bug priority:p2 ready
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100
Mantenedores costumam responder em até 1 dia
-
Escaped `*` followed by `*` (`\**`) never matchesTalvez já em andamento @bardrop assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 71/100
editorconfig/editorconfig-core-js#172 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbertatype: bug 🐛
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 63/100
puckeditor/puck#1929 ·
Mantenedores costumam responder em até 1 dia
-
compression() compresses every response at Brotli quality 11Talvez já em andamento @staylor assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia