Re:Show HN: Git-lanes – Parallel isolation for AI coding age...
by bugrax on Saturday March 07, 2026 @03:16AM
(#47285637)
I built this because I was running Claude Code and Cursor on the same repo and they kept overwriting each other's files. git-lanes uses Git's native worktree feature to give each agent its own isolated workspace — no dependencies, just git.
Happy to answer questions about the approach or hear how others handle multi-agent workflows.
Re:Show HN: Git-lanes – Parallel isolation for AI coding age...
by parsak on Thursday March 19, 2026 @12:43PM
(#47442244)
i built this because i was running claude code and cursor on the same repo and they kept overwriting each other's files -- that sentence is exactly what motivated pane too.
git-lanes solves the isolation problem cleanly as a CLI layer. pane approaches it from the other direction -- the worktree isolation is baked into the UI model itself (one pane = one worktree), so there's nothing to run or remember. you just open pane, create a pane for your feature, and the worktree exists.
curious if you considered going the desktop app direction or if the CLI-only scope was intentional? there's something appealing about a zero-dependency shell tool.
github.com/Dcouple-Inc/Pane -- fully open source (agpl-3.0) if you want to compare approaches.
Happy to answer questions about the approach or hear how others handle multi-agent workflows.
git-lanes solves the isolation problem cleanly as a CLI layer. pane approaches it from the other direction -- the worktree isolation is baked into the UI model itself (one pane = one worktree), so there's nothing to run or remember. you just open pane, create a pane for your feature, and the worktree exists.
curious if you considered going the desktop app direction or if the CLI-only scope was intentional? there's something appealing about a zero-dependency shell tool.
github.com/Dcouple-Inc/Pane -- fully open source (agpl-3.0) if you want to compare approaches.