Tmux

**Verdict:** Strong, specialized skill for interactive TTY automation via tmux, best used when non-interactive bash is insufficient. It’s powerful for REPLs, TUIs, and parallel agent orchestration, but introduces complexity and some operational risks. **Recommended scenarios** - When you explicitly need an interactive terminal: language REPLs, full-screen tools, prompts, or CLIs that behave differently without a TTY. - Running multiple coding/automation agents in parallel, each in its own tmux session, and scraping their output. - Long-running interactive workflows where a human may attach/detach alongside the agent. **Key risks & trade-offs** - **Environment constraints:** Only works on macOS/Linux with tmux installed and on PATH; not suitable for native Windows outside WSL. - **Complexity & fragility:** Requires careful handling of sockets, session/window/pane IDs, and prompt detection via text scraping; misconfigured patterns or races can lead to hangs or missed states. - **Resource & cleanup concerns:** Orphaned tmux sessions can accumulate and consume resources if the agent does not reliably kill sessions or servers. - **Command-sending risk:** As with any shell-control tool, sending arbitrary keystrokes/commands carries the full risk surface of shell execution (file modification, deletion, etc.), so it should be combined with appropriate higher-level safety policies. Use this skill when you truly need an interactive TTY and are prepared to manage tmux sessions carefully; for simple, non-interactive workloads, prefer standard bash/background mechanisms instead.