worktrunk: Two jobs at once, without stepping on each other
worktrunk is a small command-line program that lets you keep the same code repository open in several folders at once, one folder per job. Instead of hiding your unfinished work so you can start the next task, you open a second folder that shares the same history and work in both at the same time. One command creates the new folder, a second one shows you a table with where each job sits. It is especially useful when you run several AI assistants in parallel, because each one gets its own space and they stop stepping on each other's work.

What it does
Picture a folder on your computer. Inside it is your project, all its files, and a hidden notebook we call git. The notebook keeps the history: who changed what, when, and in what order. You work there, you save, you carry on.
The trouble starts when you want to do two things at once. You are fixing something and suddenly someone asks for a different fix, urgently. You do not want to throw away the work in your hands. Until now your options were to hide the changes for a while, park them somewhere, and bring them back later. It works, but it is like clearing the whole table so you can eat at another table, then setting it again.
Git has had a solution for years that few people use, because it is hard to handle. It is called a worktree. It means something simple: a second folder on disk that points at the exact same history. Not a copy of the notebook — the same notebook. You keep the folder of your main work and a second one beside it, both alive, both tied to the same project.
worktrunk takes that ability and makes it as easy as a branch. A branch is a line of work inside the notebook: a series of changes that can take its own road and later join the others. Until now you worked one branch at a time, inside one folder, switching branches with a command. worktrunk gives you one folder per branch.
The move that does everything is one command. You type it, give it a name, and the tool creates the branch and the folder together. The branch starts from where you stand, and the folder sits next to the repository, named after the project plus the branch. You do not have to remember where it went. The second move is a table that shows every open branch, which folder each one lives in, how far ahead or behind the main branch it is, whether it has unsaved changes, and how old the last work on each one is.
And here is why the tool exists. Its description on GitHub says plainly that it is built for parallel AI agent workflows. Think about what happens today. You set an assistant to write code, you wait, and in the meantime you cannot touch the same project because the assistant has the files open. Put two assistants in one folder and they trample each other. worktrunk gives each assistant its own folder, its own branch, and the same history. They work side by side without colliding, and at the end you merge what you keep.
That is the whole thing. One program you call from the command line, a clean name for each job, and a table that shows you everything.
What it does not do
First and most important: it is not a server. It is not one of those programs you declare to an AI assistant to hand it new abilities. worktrunk adds no tools to anyone, and there is no list where you register it. It is a program you call from the shell — the window where you type commands. Any assistant that can run a command can use it; nobody has to declare it anywhere.
Second: it does not replace git and it does not hide git. The repository stays an ordinary repository. Everything you do with worktrunk you can do with plain git commands, just in more steps. If something goes wrong, you are not locked inside a special system.
Third: it does not merge branches for you and it does not decide for you. It does not resolve conflicts. When two branches have changed the same lines, the merge is still your job, as always.
Fourth: it does not give you free space. Every worktree is a real second folder with the files inside, not a shortcut. The tool claims it can share hidden build caches on some file systems — we keep that as a claim from the maker, because our own test never touched it. Either way, disk space is the price.
Fifth: it does not explain itself. There is no window, no buttons, no friendly message when something is missing. It is a bare command line. If you do not read what a command does, it will not guess for you.
Who it is for
For the person running several AI assistants at the same time and tired of refereeing them over one folder. That is the first reader, and the tool was built for them.
For the developer who gets two requests at once: a fix now, and a proper piece of work already in progress. worktrunk keeps both open, each in its own folder, without clearing and resetting the table.
For the person on a large project who wants to try a change without touching the serious work. The second folder becomes the workshop, with a clean way back if the experiment fails.
It is not for someone who always does one thing at a time and has never needed two versions alive. There, the folder is one, the branch is one, and the tool will look like an extra.
Installation
On Windows 11 you install it with the program installer. One command, from the shell:
winget install max-sixty.worktrunkAfter that you have two names for the same program: wt and git-wt. Keep the second one. There is a clash that will confuse you if you do not know it: Windows Terminal also has a command named wt. If you type wt and a terminal window opens instead of the tool, you did nothing wrong — the computer found the other program first. git-wt collides with nothing.
The setting that is often missing
This is the next step, and it is not optional if you want to land inside the new folder automatically. Without it, the tool creates the folder but leaves you where you were:
git-wt config shell installOne thing you will never need: there is nothing to download from npm, the JavaScript package registry, or from PyPI, the Python one. There is not a single dependency line to install. The tool ships as one ready-made program, a file that runs at once with nothing to set up around it.
If you want to build it yourself
Here you need the Rust toolchain, the language the program is written in:
cargo install worktrunkThat road is for anyone who wants to change the tool from the inside. For ordinary use, the first command is enough.
Using it with each LLM
Again, because this trips people up: worktrunk is not a server, and you do not declare it to any assistant. There is no list to add it to. All you do is give a command from the shell — and the assistant runs it with you or for you. The same applies everywhere, but each assistant receives the command differently, which is why the steps are split below.
Claude Code
Open Claude Code inside the project folder and ask it to prepare its own space before it starts working. It will run this:
git-wt switch --create claude-fixIf you have done the shell setup, it drops you into the new folder. Whenever you want to see where each job stands:
git-wt listCodex CLI
Same shape, a different name so you can tell the jobs apart. From the project folder, before it begins:
git-wt switch --create codex-fixAnd the same table to check:
git-wt listAsk it to run the first command as its own step, before it touches any files. That way its work never shares a folder with anything else.
Cursor
In Cursor you work inside the editor, so open the built-in terminal in the project folder and run:
git-wt switch --create cursor-fixThen open the new folder in Cursor as a separate window. Cursor’s assistant now works in its own space, and your main work stays untouched beside it.
Where it wins, where it loses
It wins on the very obstacle it removes. The hardest part of worktrees was never git; it was having to remember paths and names. Here one command does the job, with a fixed naming scheme, and a table tells you the rest.
It wins because it is weightless. It is a ready-made program, 17.46 MB for Windows, with no runtime dependency. It loads nothing into any assistant session, keeps no process in memory, and asks for no account.
It wins on transparency. It is not a closed system. Everything it does shows up in the commands, and everything it does can be redone with plain git.
It wins, too, on maturity speed. At 10,738 stars and 395 forks, with 41,290 downloads in total, this is a tool people use, not one person’s experiment.
It loses on first contact. Without the shell setup, it creates the folder and leaves you behind. A new user thinks it failed. It is a step at the start, not a bug, but it costs time.
It loses on space. On Windows, where copies share little or nothing, every worktree is genuinely a second set of files.
It loses, finally, on age. The project was born on 17 October 2025 and reached version 0.81.0 within a year. A version number that moves that fast means frequent changes; a tool moving this quickly asks for a little patience from anyone putting it into daily work. The 73 open issues on the repository say the same thing.
The test
I downloaded the official 0.81.0 build for Windows — the file is 17.46 MB and 1,407 people had downloaded it before me — unzipped it, and made my own git repository with one file inside, in a folder I created myself.
First check, the version:
git-wt --versionIt answered wt v0.81.0. Correct, the version comes out as it should.
Second check, the core function. I created a branch and a workspace in one move:
git-wt switch --create trap-wtThe tool created the branch trap-wt from the main branch and the folder beside the repository, named demo.trap-wt. It printed: “Created branch trap-wt from master and worktree @ …/demo.trap-wt”. That is the exact naming scheme: repository name, a dot, branch name.
And the same moment brought the failure worth knowing about. The tool printed “Cannot change directory — shell integration not installed”. In other words: without running the shell setup first, it creates the new folder correctly but does not move you into it. You stay in the original folder and walk in yourself. It is not a bug, it is a missing setting — but if you do not know it, you think nothing worked.
Third check, the table:
git-wt listIt printed a table with two rows, the main branch and the new one, with columns for branch, status, distance from the main branch, remote copy, path, last change and message. It works exactly as promised.
Those three are everything I measured. Anything else the maker’s documentation mentions, I report as their claim, not as a measurement.
What it costs
The tool. Zero money: worktrunk is dual-licensed, MIT or Apache-2.0 (we read that from the LICENSE file, because the GitHub API field says NOASSERTION). It needs no key, no account, no model call: it is a local program.
The context. It is not an MCP server, so it loads no tool schemas into any session: its token tax before you write a word is zero. Its weight is the program itself: 17.46 MB for the Windows archive (measured from the size field on the release), a static binary with no runtime dependencies. For comparison, a tool with heavy model dependencies runs to hundreds of megabytes.
The work. You pay nothing for use; you pay in disk space, because every worktree is a second copy of the repository. The tool itself offers savings through shared build caches, but only on APFS, btrfs and XFS file systems — not on NTFS, which means not on Windows. There the copies are real copies. And one cost in time that we measured: without git-wt config shell install it does not move you into the new folder; it creates the worktree and leaves you where you were.
Telemetry. There is none: it is a local program with no account and no network calls needed to run.
Verdict
It is worth it if you run several assistants on the same project at once. There worktrunk is not a convenience, it is the difference between one assistant and three. It gives each job its own folder, sharing the same history, and a table that shows everything without memorising paths.
It is not worth it if you do one thing at a time. You would pay disk space and a learning step for something you do not miss.
Two things to remember before you install it. First: run the shell setup straight away, or you will think the tool is broken. Second: it is new, it moves fast, and that means some commands will change. The project is healthy — 10,738 stars, 41,290 downloads, active development, a free licence — which is why I am not afraid of it. But you install it for the job it solves today, not to forget it for two years.
My own judgement: within a year, managing workspaces for parallel assistants will be as ordinary as branches are. worktrunk is one of the cleanest current examples of that turn, and the price — zero — makes it an easy bet.
Sources:
https://github.com/max-sixty/worktrunk