[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

オープン
#39,620 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

[!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
主要言語
TypeScript
スター
24.8k
フォーク
6.4k
平均マージ
4時間 29分
マージ済み PR(30日)
488

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pingdotgg/t3code のほかの issue

pingdotgg/t3code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。