You know the feeling. You just want to spin up a quick feature branch, keep your terminal clean, and work in parallel without nuking your current state. So you turn to a worktree manager. Ten minutes later, you’re trapped in a maze of configuration files, GUI dashboards, and opinions you didn’t ask for.
We’ve all been seduced by tools like Conductor, Paseo, or the Codex App. They promise to streamline your parallel development. But there’s a catch. The paradox of developer tools is that the more they try to help you, the more they get in your way.
Worktrees exist to give us simplicity. They let us bypass the mental gymnastics of stashing and switching. But the moment you introduce an over-engineered manager to handle them, you’re right back where you started: wrestling with abstraction instead of writing code. The solution becomes the problem.
Recently, a developer on Hacker News shared a project called ‘wt’. It’s a worktree management tool they built for themselves. It doesn’t have a slick UI. It doesn’t try to manage your entire environment or dictate your workflow. It just handles worktrees.
This is the twist we all need to hear: You don’t need a better worktree manager. You need less of one. The best tool isn’t the one with the most features; it’s the one that respects your terminal enough to get out of the way.
The Unix philosophy has survived for decades for a reason. Write programs that do one thing and do it well. When a tool fades into the background, you finally regain ownership of your workflow. You stop managing the manager and start shipping the code.
If you value terminal efficiency and minimalism, it’s time to ditch the bloated dashboards. Embrace the void. Let your tools do the heavy lifting silently, and keep your cognitive load exactly where it belongs: on the architecture, not the setup.
FAQ
Q: Isn't a feature-rich worktree manager better for complex projects?
A: No. Complexity in your project should be handled by your architecture, not your developer tools. A bloated manager just adds a new layer of configuration debt you have to maintain.
Q: What does a 'minimal' worktree tool actually do differently?
A: It strips away the GUI and the opinionated environment setups. It executes the core Git commands needed to create, list, and remove worktrees without adding a learning curve.
Q: Is the Unix philosophy really practical for modern development?
A: It's the only practical approach left. As AI and cloud environments pile on abstraction, owning a simple, terminal-first workflow is the last line of defense against losing control of your own machine.