feature request: git worktree integration #408

Closed
opened 2026-02-16 17:26:38 -05:00 by yindo · 4 comments
Owner

Originally created by @rekram1-node on GitHub (Jun 30, 2025).

Originally assigned to: @adamdotdevin on GitHub.

I would love a way to be able to delegate work to a bunch of opencode agents without having to worry about making sure they are working with separate files. I wonder if there could be some git worktree (or alternative) to make the agents work on different things.

You also may not want to support this and just have the onus be on the user to create and manage the worktrees. Idk though I like the workflow of delegating small well defined tasks and then coming back to see what it did.

Originally created by @rekram1-node on GitHub (Jun 30, 2025). Originally assigned to: @adamdotdevin on GitHub. I would love a way to be able to delegate work to a bunch of opencode agents without having to worry about making sure they are working with separate files. I wonder if there could be some git worktree (or alternative) to make the agents work on different things. You also may not want to support this and just have the onus be on the user to create and manage the worktrees. Idk though I like the workflow of delegating small well defined tasks and then coming back to see what it did.
yindo closed this issue 2026-02-16 17:26:38 -05:00
Author
Owner

@apaslak commented on GitHub (Jul 11, 2025):

have the onus be on the user to create and manage the worktrees.

Related #891

@apaslak commented on GitHub (Jul 11, 2025): > have the onus be on the user to create and manage the worktrees. Related #891
Author
Owner

@jessevdp commented on GitHub (Aug 13, 2025):

@rekram1-node I noticed you closed this as completed. I’m curious: Was something like this added? (I can’t find any reference of it.) Or did you find a workaround?

@jessevdp commented on GitHub (Aug 13, 2025): @rekram1-node I noticed you closed this as completed. I’m curious: Was something like this added? (I can’t find any reference of it.) Or did you find a workaround?
Author
Owner

@nesl247 commented on GitHub (Nov 15, 2025):

I'm guessing it was closed by mistake as even the PR related to #891 wasn't fixed until after this was closed. Could the issue be reopened or should we open a new issue?

@nesl247 commented on GitHub (Nov 15, 2025): I'm guessing it was closed by mistake as even the PR related to #891 wasn't fixed until after this was closed. Could the issue be reopened or should we open a new issue?
Author
Owner

@rekram1-node commented on GitHub (Nov 15, 2025):

I closed this because some of my original thinking around it prior to me joining the team was different, we have since had conversations and I think the way this will end up working was different than my original idea

Still a lot in flux but more to come in time

@rekram1-node commented on GitHub (Nov 15, 2025): I closed this because some of my original thinking around it prior to me joining the team was different, we have since had conversations and I think the way this will end up working was different than my original idea Still a lot in flux but more to come in time
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#408