Alternatives
Products that do what Wtdb – give every Git worktree its own database does
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.
- 1
- 2
- 3SG
2014 · github.com
- 4
- 5GW
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
- 6
- 7BE
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
- 8
- 9
- 10
- 11PB
2019 · github.com
- 12LA
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
- 13
- 14
- 15GV
2016 · github.com
- 16D2
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
- 17BC
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
- 18T2
2020 · github.com
- 19IM
Hello HN, I've just released a new migration tool for Go that mimics the functionality of Ruby on Rails migrations. It's designed to help Go developers manage database schema changes with ease. This allows you several benefits: - Write type-safe migrations - Auto down of migrations whenever it's possible - Easy backfill even with business logic because it's Go code - Painless integration with existing schema - sql.DB compatible and driver agnostic (it uses your driver) I have a pretty complete API to manage Postgres schema and I am working on the SQLite one (a little more complicated due to…
2024 · github.com
- 20
- 21SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 22CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 23GA
Hello HN! These last few months I've been working on my first open source project: an embedded database written in pure-go. That took me some months, as I had to learn how to deal with such large packages. Until then, all packages I had made were quite small an did not require much. I usually did not have to worry about things like allocation optimization and instance pools until This project. It started when I wanted to make a port of a tool to a TUI environment. I'm actually used to working with TUIs in golang, so that was my language of choice. The tool I wanted to port is written in…
Feb 2026
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →