treework
An interactive CLI for people who like git worktree but don’t like remembering the commands.
treework wraps the git worktree lifecycle in a simple arrow-key menu so you can create, manage, and remove worktrees without typing long flags or paths from memory.
Built in Go. Open source. MIT licensed.
Repo:
https://github.com/vanderhaka/treework
What it does
treework scans your development folder for repositories and lets you create a new worktree on a new or existing branch, automatically copy .env files, install dependencies, open your editor, and safely remove a worktree with checks for uncommitted changes.
It handles the boring glue so you can focus on the branch you actually care about.
Who it’s for
Developers who use worktrees regularly, context switch between repos, and forget git worktree add ../some-long-path -b branch-name five minutes after reading the docs.
If you like worktrees but don’t want to memorise the syntax, this is for you.
Who it’s not for
People who are genuinely elite at Git and enjoy typing long commands from memory. You probably don’t need this.
Why it exists
git worktree is powerful. It’s just not friendly.
treework removes the cognitive overhead and turns it into a fast, repeatable workflow. Create. Code. Clean up. Done.
Status
Polished? Probably not. Battle-tested? Only by me, which is not reassuring.
But if you also forget Git commands immediately after reading the docs, this might help.
submitted by
/u/Vandercoon
Originally posted by u/Vandercoon on r/ClaudeCode