Skip to content

chore(desktop): refresh the vendored AA plugin to main 1f82713 - #1598

Open
NightmareAway wants to merge 1 commit into
anywhere-labs:masterfrom
NightmareAway:fix/desktop/aa-bridge-2.0
Open

NightmareAway wants to merge 1 commit into
anywhere-labs:masterfrom
NightmareAway:fix/desktop/aa-bridge-2.0

Conversation

@NightmareAway

Copy link
Copy Markdown

背景

anywhere-labs/Agents-Anywhere#498:Windows 上同时运行 DSH Desktop 与 Agents Anywhere 2.1.0 桌面端时,DSH Runtime 永久停在「等待本地 DSH Bridge」,退出桌面端后立即恢复。

根因不是让位逻辑,而是本机桥接协议代次不一致:

  • Desktop 0.2.1-rc.2 内置的 AA 插件是 2.1.0-desktop.c39b82d4fffb1.r2e406d2a,来自 AA 提交 39b82d4(2026-10-18)。该构建仍是 Bridge 1.0:endpoint_path() = <bridge>/endpoint.json、回环 TCP 的 RuntimeServer,包内没有 meshcall / aa.dsh.v2.Bridge。
  • AA 在 2026-10-19 的 firework好像无法添加kimi-k3模型 #353 才把本机桥接迁到 MeshCall(Bridge 2.0,connector.json 会合点);AA 2.1.0 发布说明也写明「硬切 2.0」。
  • 让位后 1.0 的 RuntimeServer 其实仍在监听(bridge.stopped 只出现在 DSH 退出时),但 2.0 的 Connector 只读 connector.json,两边永久互不可见。

即:Desktop 需要带 ≥ Bridge 2.0 的 AA 构建。

改动

  • 用 corepack yarn aa:prepare-release 从 AA main 重建并采纳 artifact:d471c5f → 1f82713(AA 2.1.0,含 Bridge 2.0)。
  • 同步 vendor/agents-anywhere/provenance.json、三个 Desktop 包与根 package.json 的 artifact 引用、yarn.lock、dsh-plugin-desktop/THIRD_PARTY_NOTICES.md 的 AA 版本行。
  • 在 vendor/agents-anywhere/README.md 记录版本沿革:0.2.1-rc.2 内置的 39b82d4 早于 MeshCall 迁移,避免后续 release 再回到 1.0 桥接。

验证

  • node scripts/prepare-agents-anywhere-release.mjs --check:Stable / Beta / Next 三个通道均指向 1f82713。
  • node --test scripts/agents-anywhere-release-policy.test.mjs:16 passed / 1 skipped。
  • node --test scripts/agents-anywhere-connector.test.mjs:9 passed。
  • yarn workspace dsh-plugin-desktop verify:licenses:通过。verify:notices 在 Windows 上重新生成会把 Darwin 平台行替换成 win32 行,因此只手工更新了 AA 版本行。
  • 产物检查:lib/index.js 含 aa.dsh.v2.Bridge、aa.dsh.v2.Sync、connector.json、meshcall;endpoint.json 出现 0 次;lib/bundled-connector/connector/mesh/hub.py 存在。
  • 用本机 DSH 0.2.1-rc.2 运行时加载验证:插件可 import(name=agents-anywhere-bridge-next,导出 apply),临时 profile --dump-config 正常合成 agents-anywhere-bridge-next 行,headless 启动可完成插件初始化。

未运行:完整 yarn check、submodule layout gate(本机未初始化 deepseek-harness/ 子模块)、签名安装包与真实 AA Desktop 握手。

关联

Adopt the latest official Agents Anywhere main for the Stable, Beta and Next
channels: d471c5f -> 1f82713 (AA 2.1.0). The rebuild keeps the MeshCall bridge
2.0 (connector.json rendezvous, aa.dsh.v2.Bridge / aa.dsh.v2.Sync) and picks up
the AA fixes merged since the previous adoption.

Context for the DSH runtime deadlock reported as
anywhere-labs/Agents-Anywhere#498: Desktop 0.2.1-rc.2 shipped an AA artifact
built from commit 39b82d4 (2026-10-18), one day before AA moved the local
bridge to MeshCall (anywhere-labs#353, 2026-10-19). That build still exposes the 1.0
loopback endpoint, so an AA 2.1.0 Desktop, which only reads connector.json,
can never reach it once Desktop yields the local Connector. The pinned artifact
here already carries bridge 2.0; this refresh keeps the next Desktop build on
the latest AA main and records the version story in the vendor README so the
release that follows 0.2.1-rc.2 does not regress.

Verified: yarn aa:check keeps all channels on 1f82713; AA release-policy tests
pass (16 pass, 1 skipped) and Connector compatibility tests pass (9/9);
verify:licenses passes; the packed artifact contains the bridge 2.0 calls and
the MeshCall Router, with no 1.0 endpoint. Not run here: the full yarn check
gate, the submodule layout gate, a signed package and a live AA Desktop
handshake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant