CodeNomad vs worktrunk
Desktop cockpit for OpenCode: multi-instance sessions, git worktrees, remote browser access, voice input and a command palette — a workspace for living in AI coding sessions. — 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.
codenomad bundles git-worktree management into a desktop cockpit for OpenCode; worktrunk is the standalone, agent-agnostic CLI version of that feature.
| CodeNomad | worktrunk | |
|---|---|---|
| Stars | 2.6k | 8.0k |
| Forks | 172 | 274 |
| Language | TypeScript | Rust |
| License | MIT | NOASSERTION |
| Last activity | 2 days ago | yesterday |
| Topics | coding | coding, orchestration |
| Curated connections | 7 | 5 |
CodeNomad — the curator's take
For developers who run OpenCode all day and have outgrown the terminal: parallel sessions across projects in one window, git-worktree awareness for agent branches, a password-protected server mode for driving sessions from any browser, and quality-of-life extras (voice input, SideCars for embedding local web tools). NOT useful if OpenCode isn't your driver — it's a cockpit for that engine specifically, not a general agent UI; and it's young (2k stars), so expect rough edges alongside the fast release cadence.
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.