Alternatives
Products that do what Git-workty – I got tired of Git stash and built a worktree wrapper does
I context-switch a lot. Someone pings me about a bug while I'm mid-feature, and I either: 1. `git stash` (and forget what's in there forever) 2. Make a "WIP: stuff" commit (clutters history) 3. Ignore them until I'm done (not great) Worktrees solve this perfectly – each task gets its own directory, fully isolated. But the commands are clunky and I kept forgetting the syntax. So I built a small CLI wrapper. Now my workflow is: ``` wnew feat/login # creates worktree + cd into it # ...do work... wcd # fuzzy-pick another worktree, cd there wgo main # jump straight to main ``` Dashboard…
- 1GA
2019 · github.com
- 2LA
Inspired by lazygit, I have been working on a TUI to manage git worktrees easily, making some workflows for creating and managing worktrees a bit more straightforward. For example, creating a worktree from a PR/MR or from local changes. Executing commands on a worktree, or running a custom tmux session directly on a selected worktree. A lot of other tools are more CLI-oriented. I have tried to compile an honest comparison here: https://github.com/chmouel/lazyworktree/blob/main/COMPARAISO... Some of the code and documentation was written with an LLM if…
Jan 2026 · github.com
- 3IM
2018 · github.com
- 4GW
I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!
2025 · github.com
- 5GA
Hi Hacker news ! I’m Julien and I built an alternative CLI for Git : gut. Even if I haven’t been coding for a long time (I’m in the first year studying computer science), I’ve always found git to be frustrating. The command naming is inconsistent and git lets you easily shoot yourself in the foot. I made gut, another git porcelain, to solve these issues. It provides a consistent naming of command. To do so, syntax is based on subcommands. For example, to delete a branch, run gut branch rm rather than git branch -d, same to delete a remote (gut remote rm) and so on. Gut also prevents you from…
2023 · gut-cli.dev
- 6
- 7
- 8IC
Personally, I think the JJ VCS (https://github.com/jj-vcs/jj) hit a point some time in this past year where I find it hard to find a great reason to continue using git. Over the years I've cobbled together aliases and bash functions to try to improve my git workflow, but after using jj, which works with ~any git repo and integrates great with Github repos, all of the workflow issues I ran into with git are not only solved, but improved in ways I couldn't manage with simple scripts. One example is the op log, which lets you go to any point in your repo's time and provides…
Oct 2025
- 9
- 10
- 11IB
I finally got fed up with making work + personal Git repos work on my machine. Ever clone a work repository and accidentally make commits using your personal email? Or forget how to make your work repos use your work SSH key? Yeah... same. So I built the tool I've always wanted. GitPersona - a CLI tool for managing many git profiles on a single machine. Shoutout to my boy Codex for helping me finally ship this.
Mar 2026 · github.com
- 12WG
I run a lot of agentic coding sessions in parallel, each in its own git worktree. Every worktree points at the same local Postgres though, so the moment one branch runs a migration it changes the schema out from under the others. I'd end up with agents tripping over each other, or me babysitting which branch "owned" the DB at any given moment. I made this to fix it. I hope you might find it helpful too.
Jun 2026 · github.com
- 13AC
Jun 2026 · github.com
- 14
- 15BM
hey hn, i built beehive for myself mostly. it has gotten to the point where my work consists in supervising oc or cc labor at tasks for multiple issues in parallel. my set up used to be zellij with a couple tabs, each tab working in a separate dir and it was a pain to manage all that. i know i could use git worktrees but they're kind of complicated, if you don't know how to use them it is easy to mess up, and i just prefer letting agents run in separate dirs with their own .git and not risk it. while i like zellij and use it inside beehive, i dont like the tabs and i forget where i am half…
Feb 2026 · storozhenko98.github.io
- 16CC
We're two engineers that got fed up with context switching. Why do we need to do a git push, open a browser tab, wait for some task to actually start, bite nails (or read HackerNews) for 10 minutes or more while dependencies are being installed for the 100th time and finally end up with an invalid YAML error. And for some reason this usually happens in the final stage of the pipeline leading up to the inevitable git commits "Fixed", "Fixed again", "Test", "Really fixed this time". We can do better. We set out to build Zippy. A CI/CD system that works from your terminal. No context…
Mar 2026 · zippy.sh
- 17GZ
Feb 2026 · github.com
- 18BE
I realised I was working on more parallel tasks with coding agents, but git branches became a huge bottleneck. Tried Git Butler but it just complicated things further. Found git worktrees as a solution but the git API was a bit too complicated for day to day. So thought I'll vibe-code this simple CLI utility to manage the process. It technically works with any setup – claude/codex/gemini + cursor/vim/whatever. Just manages git worktrees inside your repo and sets up your dev environment how you like it. Nothing fancy, just something I built to scratch my own itch. Figured…
2025 · github.com
- 19
- 20AD
I’ve been tinkering with what a “multi-agent IDE” should look like if your day-to-day workflow is mostly in terminal (Claude Code, OpenAI Codex, etc.). The more I played with it, the more it collapsed into three fundamentals: * A good TUI: Terminal is the center stage, with other stuff (CodeEdit, Diff, Review) baked on the side. I don’t like piping Agent’s output through some electron wrapper, here you get to run CC/Codex/Droid/Amp/etc directly. * Isolation: agents shouldn’t step on each other’s toes. The simplest primitive I’ve found is Git worktrees. It is not as…
Jan 2026 · agentastic.dev
- 21SP
Hello HN. This is my first webapp. It works like a pastebin, in which you can visually keep track of the changes you and others make to it. I was a little reluctant about posting it here because I'm not sure it meets the HN quality standards, but, as a beginner, I would really appreciate to have some feedback and/or tips. The url is: http://srctree.net/ An example of usage: http://srctree.net/1 Thanks!
2012
- 22
- 23GG
2024 · github.com
- 24GG
Coming from the land of the mono-repo (ex-googler), I decided to embrace the multi-repo, plain-git style. Methought, “hey, submodules, what could possibly go wrong”. Well, how about everything: detached HEADs, impossibly tedious commit management, and just about everything else. "OKAY" I said, a simple Python script should be fine, right? Well, NO. It turns out to be more complex. So I thought "others have got this, right? My time in mono-repo land was long and someone will have solved this" — well, yeah NAH. I won't bore you (the longer, boring comparison is in the docs) but everything I…
Jul 2026
Ranked by how close each launch is in meaning, then by votes. Refine with a description →