[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

Ouverte
#39,620 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
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
authentication

Piste de recherche

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.

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

Description

[!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
  1. 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", gcpProject and gcpLocation set). The instance was signed in and working before the update.
  2. Let T3 update the managed runtime to Antigravity CLI 1.5.13.
  3. 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.json from the previous runtime is still present (it holds client_id, client_secret, refresh_token, token_uri and scopes). So 1.5.13 does not pick up the existing business sign-in, similar to #36033 for oauth-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
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.