Worktrees

[elmpp]

README.md says:

Isolate agent work in worktrees and creates checkpoints

Am i right in thinking that each issue of the graph is a separate worktree (+branch) and the generated commits are the HEAD of each branch?

If so, how do you see the reintegration / acceptance of the worktrees working. Are there workflows for this? Perhaps ability to add extra issues (although i see this could be tricky if separate branches). Virtual branches would be so 🤯 here

[alexngai]

I think of the code diffs an agent makes while implementing issue map cleanly to each issue, while the worktree itself exists as an ephemeral environment that can be built upon but isn't necessarily binding. We're adding support for stacked diffs (like sapling but built on top of git) that can cleanly encapsulate work streams and worktrees.

But yes, with the concept of a work streams and stacked diffs, it becomes easier to branch and merge different sets of issues like virtual branches so different coding agents can build on top of each others' work in parallel. Should be coming soon within the week! What branch/worktree managements do you like using currently? I found that this is definitely the biggest bottleneck for running a large number of agents in parallel