pi-tmux

I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon. pi-tmux is one such example (seems to be archived now) which inspired me to use tmux as communication layer and provide visibility of subagents of multiple models in their native harnesses [1]. There's also herdr, which is not 0-stars, but is super interesting but lesser known project [2]. This also has interesting substrates to allow agent coordination. None of these are harnesses per se, but they're pointing towards clear gaps in existing harnesses. For example, we've known for a while now that compounding knowledge of different class of models achieves better performance. Why is there no harness where this is a native functionality? And there's no harness where subagents are first class citizens both in

Every time i see some new orchestrator framework worth more than a few hundred loc i cringe so hard. Reddit is flooded with them on the daily and HN has them on the front page occasionally. My current setup is this; - `tmux-bash` / `tmux-coding-agent` - `tmux-send` / `tmux-capture` - `semaphore_wait` The other tools all create lockfiles and semaphore_wait is a small inotify wrapper. They're all you need for 3 levels of orchestration. My recent discovery was that its best to have 1 dedicated supervisor that just semaphore_wait's on the 'main' agent spawning subagents. Basically a smart Ralph-wiggum. https://github.com/offline-ant/pi-tmux if anybody is intrested.

Yeah i jumped on board. Build https://github.com/offline-ant/pi-tmux and am happy with it.

Picked up PI, and I'm really happy with its minimalism. Only thing missing for me was a bit more structure to long-running tasks and subagents and test-runners^1 Tried a few designs and came up with this minimal solution. A pi extension to start/capture/stop in the same tmux environment you're already using. [1]: https://github.com/badlogic/pi-mono/blob/main/AGENTS.md#test...