Wtdb gives each Git worktree its own isolated database
Wtdb is a tool that provisions a separate database for each Git worktree, preventing schema conflicts when running parallel agentic coding sessions.
Score breakdown
Wtdb removes the shared-database bottleneck that causes parallel agentic coding sessions to corrupt each other's schemas, enabling truly independent concurrent agent workflows on a single machine.
- 01Built to fix schema conflicts when running multiple agentic coding sessions in parallel, each in its own Git worktree.
- 02All worktrees previously shared a single local Postgres instance.
- 03A migration in one branch would change the schema for all other branches.
The author, posting under the handle "whh" on Hacker News, describes a workflow where multiple agentic coding sessions run simultaneously, each in its own Git worktree. The problem: all worktrees point at the same local Postgres instance, so a migration run in one branch immediately changes the schema for every other branch. This causes agents to conflict with each other and forces manual oversight of database "ownership" across branches.
Wtdb is the author's solution — a tool that gives every Git worktree its own dedicated database, removing the shared-schema conflict entirely.
Wtdb is the author's solution — a tool that gives every Git worktree its own dedicated database, removing the shared-schema conflict entirely. The project is published on GitHub and offered to others who may encounter the same parallel-agent workflow problem.
Key facts
- 01Built to fix schema conflicts when running multiple agentic coding sessions in parallel, each in its own Git worktree.
- 02All worktrees previously shared a single local Postgres instance.
- 03A migration in one branch would change the schema for all other branches.
- 04The tool provisions a separate database per Git worktree.
- 05Published as an open-source project on GitHub by author 'whh'.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 15, 2026 · 11:57 UTC. How this works →