agent-orchestrator vs worktrunk
Desktop agent IDE for fleets of coding agents: each task gets a worker with its own workspace and agent CLI, while a project orchestrator plans work and handles CI fixes, conflicts and reviews. — versus — wt: the Rust git-worktree CLI built for parallel AI agents - worktrees addressed by branch name, `wt switch -c -x claude feat` creates one and starts an agent, plus hooks, list-with-status and merge.
agent-orchestrator gives each task a worker with its own workspace inside a desktop IDE; worktrunk provides the workspace-per-task primitive without the IDE.
| agent-orchestrator | worktrunk | |
|---|---|---|
| Stars | 12k | 8.0k |
| Forks | 1.7k | 274 |
| Language | Go | Rust |
| License | Apache-2.0 | NOASSERTION |
| Last activity | 2 days ago | yesterday |
| Topics | coding, orchestration, agents | coding, orchestration |
| Curated connections | 8 | 5 |
agent-orchestrator — the curator's take
The one to try if you want a GUI cockpit rather than a terminal multiplexer — a background daemon, a Kanban over live workers, isolated workspaces and browsers per task, and an orchestrator that will actually decompose an outcome into tasks and sequence them. That framing costs scriptability: it is a desktop product first, so headless CI use and remote-only setups fit worse than tmux-style tools, and you still install and configure every agent CLI yourself. The isolated-workspace-per-worker discipline is the part worth stealing even if you don't adopt the app.
worktrunk — the curator's take
If you run 5-10 Claude Code / Codex sessions in parallel and each needs its own checkout, this is the tool: worktrees become as cheap as branches, paths are templated, `wt list` shows status across all of them, hooks run on create/pre-merge/post-merge. It is deliberately a CLI primitive, not an orchestrator - it will not dispatch tasks, watch agent output, or merge for you beyond the git operation. Pair it with a multiplexer (herdr) or orchestrator (squad, fractal) rather than expecting either from it. If you want the worktree management *inside* a cockpit UI, codenomad and agent-orchestrator bundle it; if you want it in your shell, worktrunk is the most polished option and the author is unusually responsive.