Alternatives
Products that do what Branch Workspaces does
VS Code editor state, restored on every git branch switch!
- 1IM
I use interactive rebase quite often, and particularly like the editor bundled with IntelliJ. But I do not always work with IntelliJ, and am not 'fluent' with Vim, so I tried to replicate roughly the same rebase experience within a TUI. I used a small TUI OCaml project i made last year. The notable features are: - Move commits up and down, fixup, drop - Rename commits from the editor (without having to stop for a reword during the rebase run) - Visualize modified files along commits - 'Explode' a commit ,creating a commit for each modified file (a thing I found myself doing quite often)…
2024 · github.com
- 2
- 3
- 4GA
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
- 5
- 6IC
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
- 7GI
Create, upload, edit (multiple) files on the fly, in the browser. Git branches and git commits allow to save your changes, create multiple "workspaces" and switch between them in one click. Repo: https://github.com/thomscoder/harmony
2022 · harmonyland.vercel.app
- 8
- 9
- 10RE
2017 · github.com
- 11GF
2016 · github.com
- 12IL
VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less. So I built my own IDE around that workflow. Terminals are a first-class citizen, every project stays alive in the background with visual statuses. Close the workspace and come back weeks later, everything is still in its place. I've been using it for weeks and it's a big productivity boost. The…
Jul 2026 · github.com
- 13GB
2013 · github.com
- 14
- 15BC
Hey HN, I'm Fedor (solo founder). After ~20 years of watching devs fight Git, I'm building Branching. Branching streams your local edits to teammates in real time - no manual push/pull. It's Git-compatible and works offline. Why you might care - Teams see each other's changes instantly instead of in PR-sized batches - Conflicts surface ASAP while context is fresh (LLM-assisted merge is experimental, off by default) - Same GitHub remote, so no migration Ships today - VSCode extension + desktop app (macOS / Windows / Linux) - 3 small product teams have been using it for 1–6…
2025 · branching.app
- 16
- 17LA
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
- 18D2
Mike, cofounder of DevSwarm here. I’ve been using Claude Code heavily for the last few months (multiple Max plans). Running sessions in parallel across git branches or worktrees is fast, but it breaks down quickly in practice because of sprawl. Terminals everywhere, editor windows everywhere, and you lose track of basics like which agent is on which branch and what is ready for review. DevSwarm is what we built to solve that. The core abstraction is simple: workspace equals branch. Each workspace runs its agent session(s) and keeps the state visible. In 2.0 we added a full VS Code IDE…
Feb 2026
- 19
- 20GN
Hey HN, I built a VS Code extension that lets you do Git things without memorizing Git commands. You know what you want to do, move this commit over there, undo that thing you just did, split this big commit into two smaller ones. Git Navigator lets you just... do that. Drag a commit to rebase it. Cherry-pick (copy) it onto another branch. Click to stage specific lines. The visual canvas shows you what's happening, so you're not guessing what `git rebase -i HEAD~3` actually means. The inspiration was Sapling's Interactive Smartlog, which I used heavily at Meta. I wanted that same experience…
Feb 2026 · gitnav.xyz
- 21GW
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…
Jan 2026 · github.com
- 22
Bootstrap every repo, sync every branch, for you and your AI
May 2026 · sync-worktrees.com
- 23
- 24GW
2020 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →