[Bug]: Antigravity Gemini Enterprise (oauth-business) still fails headless sign-in with "No browser is available here": the #36034 code-login path only covers oauth-personal
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- authentication
Línea de trabajo
Start with AntigravityDriver.codeLogin in the 0.1.11 bundle, where the issue reports an oauth-personal guard, and trace how provider sign-in calls ACP authenticate for oauth-business. Check the --login code path and existing business-token loading behavior. Done means headless Gemini Enterprise sign-in accepts a pasted code and the existing business sign-in behavior is addressed; verify on a headless Linux host.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[!NOTE]
🤖 Claude Opus 5.5 (Claude Code) responding on behalf of Peter
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: #36034 (closed; the headless sign-in fix for "No browser is available here", reported and verified only for oauth-personal), #36033 (closed; the 1.5.x update does not carry over the old sign-in, reported for acp_token.json), #37653 (Gemini Enterprise license-picker link on Linux, runtime 1.4.5).
Area
apps/server
Steps to reproduce
- On a headless Linux x64 host (T3 service without
DISPLAY/WAYLAND_DISPLAY, no usable Secret Service keyring), configure an Antigravity instance with sign-in method Gemini Enterprise (authMethod: "oauth-business",gcpProjectandgcpLocationset). The instance was signed in and working before the update. - Let T3 update the managed runtime to Antigravity CLI 1.5.13.
- Settings → Providers → Antigravity → Retry sign-in.
Expected behavior
Gemini Enterprise gets the same headless sign-in as oauth-personal after #36034: T3 shows the Google link and accepts the pasted code. Ideally the existing business sign-in also survives the runtime update.
API keys or Application Default Credentials (AGY_ADC_AUTH) are not a workaround here, because they do not use the Gemini Enterprise subscription.
Actual behavior
- The Account row shows "Google sign-in failed. Start sign-in again." Every retry fails within about 100 ms.
- The ACP server log in the instance profile:
manager.go:819] ACP authenticate: methodId="oauth-business" meta=map[] composite_token_storage.go:586] Failed to load stored token from keyring, falling back to file: The name org.freedesktop.secrets was not provided by any .service files auth_handlers.go:144] authenticate("oauth-business") failed: No browser is available here (no graphical display is available to open a browser). Use a Gemini API key or Gemini Enterprise Agent Platform instead. (code -32603) - Before that, the runtime reports
error getting token source: You are not logged into Antigravity., although<profile>/antigravity-acp/acp_business_token.jsonfrom the previous runtime is still present (it holdsclient_id,client_secret,refresh_token,token_uriandscopes). So 1.5.13 does not pick up the existing business sign-in, similar to #36033 foroauth-personal. - Model refresh then fails with "Sign in to Antigravity in provider settings before refreshing models".
Likely cause (from reading the 0.1.11 bundle): AntigravityDriver.codeLogin starts with
if (auth.authMethod !== "oauth-personal") return void 0;
So the --login / paste-code path from #36034 is never offered for oauth-business. T3 calls ACP authenticate directly, and the runtime refuses it without a display.
Impact
Blocks work completely for Gemini Enterprise on headless or remote hosts.
Version or commit
T3 Code 0.1.11; managed Antigravity CLI 1.5.13
Environment
Linux x64, headless server running the T3 service, no Secret Service keyring, client connected remotely.
Logs or stack traces
From server.trace.ndjson:
AntigravityDriver.startCompatible → Failure
AcpRequestError: No browser is available here (no graphical display is available to open a browser). Use a Gemini API key or Gemini Enterprise Agent Platform instead.
at AntigravityDriver.startCompatible
at AntigravityAuth.runSignIn
at ProviderAuthService.start
at ws.rpc.provider.auth.start
- Lenguaje dominante
- TypeScript
- Estrellas
- 24.8k
- Forks
- 6.4k
- Merge medio
- 4 h 29 min
- PR fusionados (30 d)
- 488
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pingdotgg/t3code
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
needs more info
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pingdotgg/t3code#39400 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelPosiblemente ocupada @iamdatvt94 la tomó hace 1 día. Abiertobug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
Todos los issues de pingdotgg/t3code
Issues similares
-
area:plugins kind:bug priority:p2 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
Escaped `*` followed by `*` (`\**`) never matchesPosiblemente ocupada @bardrop la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
editorconfig/editorconfig-core-js#172 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbiertotype: bug 🐛
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
puckeditor/puck#1929 ·
Los mantenedores suelen responder en 1 día
-
compression() compresses every response at Brotli quality 11Posiblemente ocupada @staylor la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día