StackMap
Subscribe

nanoflow vs worktrunk

Claude Code plugin that ties ticket → worktree → branch → ports → PR → CI → teardown together for parallel agent sessions, with a live dashboard pane, status line, toasts and a secrets vault. — 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.

The curated verdict

Both exist to keep parallel agents in their own git worktrees; worktrunk is a lean branch-addressed worktree CLI, nanoflow wraps worktrees with ticket, ports, PR, CI status and teardown inside Claude Code.

nanoflowworktrunk
Stars1513k
Forks0505
LanguageTypeScriptRust
LicenseMITApache-2.0
Last activity16 days agotoday
Topicscoding, orchestrationcoding, orchestration
Curated connections47

nanoflow — the curator's take

Use it when you run several Claude Code sessions in worktrees and keep losing track of which one is on which ticket, port, PR and red CI run — its deterministic `nf` commands also stop the agent re-improvising gh/git rituals. Very early (tiny user base) and Claude Code-specific; if you want a standalone multi-agent app across Codex/OpenCode, or only need worktree switching, pick a dedicated orchestrator or worktree CLI instead.

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.