Back to News
Advertisement
bbyhong03 about 8 hours ago 0 commentsRead Article on github.com

HI version is available. Content is displayed in original English for accuracy.

Hey HN,

There’s been a lot of interest recently in meta-harnesses, loops, and multi-agent orchestration. Obviously, there are already a lot of good tools: Conductor, cmux, the native Codex / Claude Code apps, etc.

For my own use cases, I’ve felt that the orchestration layer tends to feel overengineered. I mostly wanted a simple local harness (i.e Pi) for running and tracking CLI agents with the ability to hop in (via tmux). Relaymux is my opinionated attempt at that.

A few design principles:

- The frontend is just Telegram / iMessage / CLI. If I want more visibility, I hop into tmux.

- Subagents are normal interactive CLI agents running in tmux windows, usually with their own worktrees.

- The harness owns the tmux session, so each longer task becomes a named tab/window. Subagents report back to the orchestrator via CLI when they’re blocked or done. Then the orchestrator just messages me on Telegram / iMessage

- It works with any CLI agent that has an interactive terminal mode, so I don’t need special print-mode/non-interactive support. This means I don’t need to stress about the Agent SDK / claude -p billing limitations.

Advertisement

Discussion (0 Comments)Read Original on HackerNews

No comments available or they could not be loaded.