Repository navigation
feat: add bili antigravity launcher lane (#2115) - #2134
Conversation
[bot] 🏷 Reviewing this PR now (not redoing it): pulled |
…he recipe lives (#2134 review nit)
3bc5baa to
177bf44
Compare
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2180-pr.2134.121d8faThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2134.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Review 中期更新 — 方向认定成立,已把分支修到可合并状态,等 CI 全绿后给最终七问结论。 审核认定(方向关):机制选型正确 —— Antigravity 的模型通道在闭源 Go 发现并已当场修掉(3bc5baa → 177bf44,已推回 PR 分支):
本地定向验证(rebased head 177bf44): CI 现状:mergeable=True(冲突已消);kernel-guard / version-guard / docs-sync / docs-coverage / build-artifact / codex-e2e / dsh-lane / pi-lane / OpenCode-V2-WS 均已 success,test 矩阵与 registry e2e 还在跑。全绿后补最终结构化七问结论。 |
First-class Google Antigravity support as a launcher client: - LAUNCH_CLIENTS/BaseClientName gain antigravity; resolveClientCommand finds the official CLI binary agy (PATH, ~/.local/bin/agy, or %LOCALAPPDATA%\agy\bin on Windows) - discoverRoutes/buildAntigravityEnv set CLOUD_CODE_URL=<proxy>/bili/<upstream> (stock upstream https://cloudcode-pa.googleapis.com; a user-exported CLOUD_CODE_URL is relayed instead) - the undocumented override verified in the v2.19.1 language_server binary. No MITM, no CA install; the proxy recognizes the wire by path (:streamGenerateContent et al. -> google adapter), gRPC-style paths relay verbatim as a graceful degrade - client-config: AntigravityConfig.baseUrl reads CLOUD_CODE_ENV; ModelWindowScope gains antigravity (no collector branch - nothing readable) - web UI launcher chip + i18n notes (zh/en); cli usage/help lines - docs: README zh/en table+examples, CLIENTS zh/en Gemini-family section incl. the built-in-plugin feasibility verdict (additive-only surfaces) - tests: 10 new cases in launcher-gemini-family (registry, route discovery, env build, MCP exclusion, env config read/load)
…he recipe lives (#2134 review nit)
177bf44 to
a6269b5
Compare
[bot] 🏷 Review 最终结论(结构化七问) —— 审核通过,无拦点。feat 类按 §7.4 由人合并。 1. 是什么问题:功能请求 —— 给 Google Antigravity( 2. 什么原因导致的:非 bug,是机制约束 —— Antigravity 对外只暴露一个网络层入口:未公开的 3. 怎么修复的:launcher 设 4. 是否有回归问题:逐项审过既有行为:纯 additive。新 5. 是否破坏缓存:不涉及 —— session identity、prefix cache、重试/去重机制全部未动。 6. 是否改了设计方向:不涉及 —— 严格沿用既有 per-client launcher 模式(gemini/iflow 一脉);wire 识别复用 google 适配器既有 path 路由,无架构转向。 7. 是否引入了新的配置:无 —— 零 bili config 字段、零 验证:rebased head 本地定向验证 typecheck clean + 42/42(launcher-gemini-family 28 含 10 个新 antigravity case、web-i18n、web-routing);最终 head 相关立项:rebase 分析中发现 master 的 CLIENTS.zh-CN.md 缺 codex pins-embedded(#1867)小节的中文镜像(en/zh 内容差集,cbb7ba27 引入时漏译)—— 属本 PR 范围外,已单独立项 #2136(带来源标记),不混入本 diff。 收工判定:审核通过,可合。#2134 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.45-master.f984400 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #2115
What
First-class Google Antigravity support as a launcher client (
bili antigravity), following the existing per-client pattern (gemini/iflow lanes). The launcher drives the official CLI binaryagy(successor of Gemini CLI, which was discontinued in 2026-06).Mechanism
language_server, which honors an undocumentedCLOUD_CODE_URLenv override (verified by static analysis of the official v2.19.1 build: binary string "Overriding CloudCodeServerURL via CLOUD_CODE_URL environment variable"). Same shape as gemini-cli's base-URL hook.CLOUD_CODE_URL=<proxy>/bili/<upstream>— stock upstreamhttps://cloudcode-pa.googleapis.com; a user-exportedCLOUD_CODE_URLis relayed through the proxy instead (claude relay-wrap semantics). No MITM, no CA install.:streamGenerateContent/:generateContent/:countTokensroute to the google adapter, so compression works exactly likebili gemini. If the server uses gRPC method paths (/google.internal.cloud.code.v1internal.CloudCode/*) those are not recognized and relay verbatim without compression — a graceful degrade, fixable later via a per-laneprotocoldeclaration ([feature] configurable wire-path table (per-provider custom paths) - Claude Desktop's claude.ai private protocol as motivating case #1909) once confirmed against live traffic.HTTPS_PROXYand does not pin certificates): addcloudcode-pa.googleapis.comto"mitm".domainsand trust bili's root CA.Built-in-plugin feasibility (owner question)
Antigravity DOES ship a user plugin system (
~/.gemini/config/plugins/<name>/:plugin.json,hooks.json,mcp_config.json,rules/,skills/, JS sidecars with a Sidecar SDK;/builtin/plugins/ship with the product; enabled viaplugins.<dir>in config.json). But every surface is additive only — tools, prompts, UI, event callbacks. Nothing can intercept or rewrite the model request/response stream, which stays entirely inside the closed language_server; MCP tools cannot reach its internal session state. So wire-only integration via the network layer is the ceiling for v1 — the launcher lane is the mechanism, not a workaround.Config surface
No bili config fields added.
CLOUD_CODE_URLis a client-side (Antigravity) env var, not a bili setting. The launcher reads the user's pre-existingCLOUD_CODE_URLfrom the process env purely to decide what to relay (same asGOOGLE_GEMINI_BASE_URLforbili gemini). No newBILI_*vars, no newconfig.jsonfields, no CLI flags beyond the standard ones.Behavior changes
Additive only: one new launcher entry
antigravity. No existing lane, default, threshold, timing, output format, or cache behavior touched. Web UI gains one launcher chip + zh/en i18n notes.Verification
npm run typecheckclean; targeted suites green locally:tests/launcher-gemini-family.test.ts(28 tests incl. 10 new antigravity cases),tests/web-i18n.test.ts+tests/web-routing.test.ts(14 tests, incl. the Web UI 英文翻译开关(i18n)— 社区 PR #807 (@amirzamli) #1024 i18n key-parity gate). Full suite + build left to CI per local-testing discipline.language_serverstrings analysis performed in-workspace during development, artifacts removed before this commit.CLOUD_CODE_URLtakes effect on the model stream, and which transport (REST/SSE vs gRPC) carries it. If gRPC turns out to be the model-stream transport, this lane degrades to verbatim passthrough until a protocol declaration or MITM route lands — the code already handles both gracefully. Live-verification asks posted in the issue thread for anyone with a running Antigravity setup (@Hiccup543).feat -> human merge per AGENTS.md 7.4.