orchestmuxlisted

# orchestmux — multi-agent orchestration in tmux `orchestmux` spawns coding-agent CLIs as tmux panes and gives every dispatched task a reporting protocol, so a coordinator can block on actual completion instead of scraping terminal output. You are normally the **coordinator**. Workers are separate agent processes in tmux panes; they report back by calling the CLI. ## Preconditions Check once before coordinating: ```bash orchestmux ps # also confirms the CLI is installed and state is readable tmux -V ``` If `orchestmux` is not on PATH, stop and tell the user how to install it (`npm i -g orchestmux`, or `npm link` from a clone) rather than improvising a substitute. ## When to use - The user wants two or more agents working at the same time. - The user wants work delegated to a *specific* agent (codex, kimi, …) while still getting the result back here. - A job splits cleanly into independent pieces worth running concurrently. ## When not to use - Work you can simply do yourself in this session. Spawning an agent to do a two-file edit is slower and burns another quota. - The user asked to hand something off and explicitly does *not* want it supervised — then just spawn and dispatch, and do not sit in `wait`. ## The coordinator loop ```bash orchestmux up # idempotent orchestmux spawn --name w1 --agent codex --yolo TASK=$(orchestmux task add "<precise, self-contained spec>") orchestmux dispatch --task $TASK --to w1 orches