中文

AgentBridge 今天把 Claude Code ↔ Codex 接成了会话内的实时对等体。下一个该接哪个 agent?

用 👍 reaction 给下面的候选投票(在本 issue 正文的每个候选行上点表情不方便,所以请在评论里 +1,或对本 issue 用 👍/🎉/🚀 等 reaction 表示「我要更多 adapter」,并在评论里写下你想要的那个)。也欢迎评论补充没列到的 agent。

候选 / candidates:

• OpenCode — 开源终端 agent(sst/opencode)
• OpenClaw —
• Hermes Agent —
• Gemini CLI — Google 的终端 agent

投票方式:在评论里写下候选名 + 一句你的用例;想要「更多 adapter」这件事本身,就给 issue 加个 👍。得票高的先做。

接一个新 agent 需要什么?一个能讲 AgentBridge control 协议(Envelope)、持有 PSK 身份的进程即可成为合法房间成员(见 docs/09-v3协作系统规格.md)。真正的活是「会话集成」:把房间事件收进该 agent 的会话、并在它完成时发布完成信号——目前只有 Claude Code 端到端打通。

English

AgentBridge today wires Claude Code ↔ Codex as real-time, in-session peers. Which agent should we adapt next?

Vote with a 👍 reaction on this issue if you want more adapters, and drop a comment naming the candidate you want (plus a one-line use case). New candidates welcome in the comments.

Candidates:

• OpenCode — open-source terminal agent (sst/opencode)
• OpenClaw
• Hermes Agent
• Gemini CLI — Google's terminal agent

How to vote: comment with the candidate name + your use case; react 👍 on the issue to signal "I want more adapters" in general. Highest-signal candidates get built first.

What does adapting a new agent take? Any process that speaks the AgentBridge control protocol (Envelope) and holds a PSK identity is already a valid room member (see docs/09-v3协作系统规格.md). The real work is session integration — feeding room events into that agent's session and publishing a completion signal when it finishes. Only Claude Code is end-to-end wired today.