Terminal orchestration for multiple AI coding agents on Windows and Unix
Try running multiple CLI-based coding agents side-by-side in a single terminal with thurbox, a TUI and CLI for agent orchestration from LeTuR. It uses terminal multiplexers (tmux, psmux, rmux) for session persistence, supports git worktrees, and exposes Lua hooks for custom panes. Designed for developers and DevOps engineers, the tool targets terminal-first workflows that need persistent, scriptable agent sessions across local and remote environments.
What thurbox actually runs and how it composes agents
thurbox launches and manages multiple AI coding agents through their existing CLIs, keeping the tool neutral toward any vendor-specific SDK. The interface places agents in separate panes inside a TUI, and the headless thurbox-cli permits scripted session creation. Support for git worktrees lets agents operate on different repositories or branches within the same session, so concurrent tasks do not overlap the main checkout.
How reliable session persistence behaves in practice
The tool delegates session stability to established multiplexers, using tmux on Unix and psmux or rmux on Windows, which preserves agent processes when terminals close or systems reboot. Because thurbox uses those backends rather than a custom session layer, long-running agent tasks survive terminal crashes and restarts, making the TUI suitable for extended background orchestration on development hosts and remote servers.
Safety, permissions, and remote operation constraints
thurbox requires standard CLI access to each agent and relies on existing local permissions; it does not add privileged system writers. Remote use works via SSH and WSL integration, and the headless CLI supports automation without interactive input. Because it operates by launching vendor CLIs, any safety guarantees depend on those agents; thurbox itself keeps orchestration and pane layout separate from agent internals.
Who can use it and how steep the learning curve is
The interface expects familiarity with terminal multiplexers and basic Lua for customization, so DevOps engineers and power users gain the most. Casual users may run basic sessions via the CLI, but defining custom panes and automations requires editing Lua scripts and understanding git worktrees. The Windows installer uses PowerShell and psmux/rmux, which preserves parity with Unix workflows for experienced terminal users.
Clear fit for terminal-first engineers, with one key trade-off
thurbox suits developers and DevOps engineers who prefer terminal-based workflows and need persistent, scriptable orchestration of multiple agent CLIs. A practical tip: run long-running agent sessions under the multiplexer and schedule automated headless tasks during idle hours to avoid interfering with interactive work. The main trade-off is the requirement for multiplexer and Lua knowledge before you can extend the interface deeply.
