Original Summary

Hi HN, I’m RC.<p>When I worked at ThoughtWorks, we were pretty religious about pair programming: one person driving, another reviewing, both working through the same problem.<p>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&#x27;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.<p>That became Agent Exchange, or ax, which we built at Summation.<p>After installing AX, start two sessions in separate terminals:<p>ax claude -n api ax codex -n web<p>Then ask Codex: “Ask api whether the schema is ready.”<p>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.<p>AX supports Claude Code, Codex CLI, Grok Build, OpenCode, and Pi. Underneath, it’s a local Go broker, Unix sockets, and a SQLite mailbox. Messages survive broker restarts, subject to expiry.<p>There’s no AX cloud relay or telemetry. The messaging runs locally; the coding agents still communicate with their configured AI providers.<p>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.

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/9/23 22:27:29