[Bug]: Antigravity existing sessions reject newly discovered models due to stale cached configOptions

未关闭
  • 哪里不对？
#35,693 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
ai-infra-agents, backend

调研方向

Start in apps/server/src/provider/acp/AntigravityAcpSupport.ts with applyAntigravityAcpModelSelection, which validates the model against runtime.getConfigOptions and fails with AcpRequestError.invalidParams. Then trace how AntigravityDriver.refreshModels and makeDisposableRuntime publish newly discovered models, since existing sessions never see them. Done means a model discovered after a session started can be selected on that existing thread and the turn starts, either by refreshing the cached options or by restarting the ACP session.

由索引模型根据 Issue 内容生成。

描述

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Start a thread with the Antigravity provider (agy acp), which keeps a long-lived AcpSessionRuntime open and caches the configOptions returned by the initial session/new.
  2. Wait for AntigravityDriver.refreshModels (or a backend/CLI rollout such as gemini-pro-orchestrator becoming available) to spawn a fresh makeDisposableRuntime (session/new) that discovers a newly available model and updates the UI model catalog.
  3. Return to the existing thread whose ACP session is still alive from before the new model appeared, switch its model selector to the newly discovered model (e.g. gemini-pro-orchestrator), and send a message.
Expected behavior

Either session/set_config_option / setModel applies the newly available model on the agent (or T3 Code restarts/refreshes the ACP session if the live session's cached configOptions are stale), allowing the turn to start normally.

Actual behavior

T3 Code rejects the model locally in applyAntigravityAcpModelSelection (~0.07–0.22 ms, without sending session/set_config_option to agy) because it validates solely against the existing session's cached runtime.getConfigOptions:

Provider error
The agent did not accept the model "gemini-pro-orchestrator". Choose another model for this provider, then retry.

Even though agy models and a fresh agy acp session/new both list gemini-pro-orchestrator (Orchestrator) as available for the same Google account.

As soon as session/close happened on that thread and a new agy acp runtime was started (session/new), applyAntigravityAcpModelSelection and session/set_config_option immediately succeeded with gemini-pro-orchestrator.

Impact

Minor bug or occasional failure

Version or commit

0.1.10-nightly.20261112.4580 (also present in origin/main @ 637507056 in apps/server/src/provider/acp/AntigravityAcpSupport.ts)

Environment

Linux (T3-Code.AppImage 0.1.10-nightly.20261112.4580), Antigravity CLI 1.5.6 / 1.5.7 (oauth-personal), model gemini-pro-orchestrator

Logs or stack traces
ProviderAdapterTurnStartError: Failed to start run ... on antigravity provider thread ...
  [cause]: AcpModelSelectionError: The agent did not accept the model "gemini-pro-orchestrator". Choose another model for this provider, then retry.
      at rejectedModel (...)
    [cause]: AcpRequestError: Antigravity model 'gemini-pro-orchestrator' is unavailable for this Google account. Select an available model.
        at AcpRequestError.invalidParams (...)
        at applyAntigravityAcpModelSelection (...)
        at AntigravityAdapterV2.applyModelSelection (...)
        at AcpAdapterV2.startTurn (...)

In apps/server/src/provider/acp/AntigravityAcpSupport.ts, applyAntigravityAcpModelSelection checks antigravityModelOptions(yield* input.runtime.getConfigOptions) and immediately fails with AcpRequestError.invalidParams if the model isn't in that session's cached configOptions. Because AntigravityDriver.refreshModels updates the provider catalog via a separate disposable runtime without refreshing existing active sessions' configOptions, any pre-existing thread rejects newly added models until its ACP process is closed and recreated.

Workaround

Close/restart the provider session (or restart T3 Code / open a new thread) so agy acp starts a fresh session/new and picks up the updated configOptions.

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
59 分钟
30 天内合并 PR
418

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。