Ax – Let Claude, Codex and OpenCode talk to each other locally
Show HN: Ax – Let Claude, Codex and OpenCode talk to each other locally
我们发现了什么
When I worked at ThoughtWorks, we were pretty religious about pair programming: one person driving, another reviewing, both working through the same problem. The messaging runs locally; the
- 来源:Hacker News(发现于 2026-09-24)
- 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
- 商业模式:API / Usage-based
- 主题:独立产品
- 初筛评分:18.3/100 · 收录 1 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
中文辅助译文(全文)
嗨 HN,我是 RC。当我在 ThoughtWorks 工作时,我们对结对编程非常虔诚:一个人主导,另一个人审查,两人一起解决同一个问题。我们中的大多数人已经在自己的编程会话中与智能体结对过。我们中的一些人甚至尝试过让智能体同时占据两个位置:一个负责实现,另一个负责审查。我非常喜欢 Claude Code 的跨会话消息功能。我希望在 Claude、Codex 和 OpenCode 之间也能获得同样的体验。现有的方案意味着要安装一个新应用或一些不够可靠的插件。我想要一个本地的、不碍事的东西,让我能继续照常使用每个工具,但能实现异构消息传递。于是就有了 Agent Exchange,或 ax。安装后,在两个独立的终端中启动两个会话:ax claude -n api ax codex -n web 然后向 Codex 提问:“问问 api schema 是否准备好了。”智能体之间通过名字互相寻址,回复会回到它们各自的对话中,包括在同一台机器、同一操作系统用户下跨仓库的情况。你也可以使用每个工具自身的恢复(resume)语法连接已有的对话。AX 支持 Claude Code、Codex CLI、Grok Build、OpenCode 和 Pi。在底层,它是一个本地的 Go 代理、Unix 套接字和一个 SQLite 邮箱。没有 AX 云中继或遥测。消息传递在本地运行;编程智能体仍然与各自配置的 AI 提供商通信。我们自己一直在用它让 Codex 和 Grok 互相审阅 AX 的 PR。我很想知道你们使用哪些智能体组合,以及目前你们自己在它们之间转发什么内容。
译文由上游机器翻译生成,可能有误;判断请以英文原文为准。
英文原文(来源本站未改写)
Hi HN, I’m RC.When I worked at ThoughtWorks, we were pretty religious about pair programming: one person driving, another reviewing, both working through the same problem.Most of us have already paired with an agent in our own coding sessions.Some of us have even tried putting agents in both seats: one implementing, the other reviewing.I really like Claude Code’s cross-session messaging.I wanted that same experience between Claude, Codex, and OpenCode.The existing setups meant installing a new app or plugins that just don't work reliably.I wanted something local that stayed out of the way, let me keep using each tool as usual, but enabled hetergenous messaging.
That became Agent Exchange, or ax.After installing, start two sessions in separate terminals: ax claude -n api ax codex -n web Then ask Codex: “Ask api whether the schema is ready.” The agents address each other by name, and replies come back into their conversations, including across repositories on the same machine under the same OS user.You can also connect existing conversations using each tool’s native resume syntax.AX supports Claude Code, Codex CLI, Grok Build, OpenCode, and Pi.Underneath, it’s a local Go broker, Unix sockets, and a SQLite mailbox.There’s no AX cloud relay or telemetry.The messaging runs locally;the coding agents still communicate with their configured AI providers.
We’ve been using it to send AX’s own PRs between Codex and Grok for review.I’d be interested in which agent combinations you use, and what you currently have to relay between them yourself.
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
- 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。