GitHub Trending: max-sixty/worktrunk — worktrees for parallel AI agents

Running four agents on one repo the way people now want to — different features, different bugs, one codebase — breaks down fast without isolation. stash, switch, stash pop is a full-time job and a sharp knife. max-sixty/worktrunk is a small Rust CLI for doing exactly this properly with git worktrees: multiple working directories, one repo, agents that never step on each other. 11,274 stars, 1,261 this week — early, focused, and solving a real pain.

What it actually does

• Creates and manages git worktrees designed for parallel agent sessions — one worktree per task, each on its own branch.
• Keeps the bookkeeping sane: which worktree belongs to which task, what's merged, what's been left behind.
• Rust-native and fast; designed to sit next to your agent harness rather than replace it.

Why it's trending this week

Parallel agents are the obvious next step past 'one agent in a terminal', and the tooling for it is still primitive. Worktrees are the oldest, boringest git feature that suddenly matters again — worktrunk is the sharp edge of that particular renaissance, and the Rust + agent-workflows combination is catnip for this audience.

Who it's for

• Solo devs running two or more agents at once on one repo (features, bugfixes, refactors).
• Teams adopting agent-first workflows who need isolation without the stash dance.
• Anyone who has already burned an afternoon on worktree path juggling.

What to check

• If you've never used worktrees: git worktree add <path> <branch> — this CLI is sugar plus housekeeping for that pattern, aimed at agent lifecycles.
• Small, young project — read the source issues before relying on it in shared infra; it's moving fast.
• Works alongside any agent harness — it's harness-agnostic plumbing, not a framework.

The boring primitives of git are quietly becoming agent infrastructure — worktrees are having their moment. Repository: github.com/max-sixty/worktrunk.