anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE] Parallel Workflow Support via Git Worktrees and Tabbed Sessions #8936

New Issue
Open
opened 2026-02-16 18:11:13 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @dzianisv on GitHub (Feb 9, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Is your feature request related to a problem?

I am currently working on 3 separate issues in my project and would like to tackle them in parallel using subagents. However, running multiple agents in a single working directory causes several issues:

State Conflict: Agents may attempt to edit the same files or create conflicting Git states, leading to file lock issues or corrupted staging.

Lack of Control: There is currently no mechanism to follow up with or control individual subagents once they are spun up in the same session.

UI Clutter: Without a way to isolate and switch between active tasks, the workflow becomes difficult to track.

Describe the solution you'd like I propose an integrated system for managing parallel agent workflows through

Git Worktrees and a Tabbed Interface:

Worktree-based Session Isolation: A tool for opencode that automates the creation of a new session in a fresh Git worktree. This ensures that each agent has its own isolated file system and Git state, preventing environment interference.

Session Tabs (UI/TUI): A tabbed navigation system (for both Web and TUI) that allows users to switch between active worktree sessions. This would allow a user to monitor "Subagent A" in one tab while providing feedback to "Subagent B" in another.

Describe alternatives you've considered

Manual Worktree Management: Creating worktrees manually and opening new terminal instances, but this lacks the unified agent orchestration and UI integration that opencode aims to provide.

Sequential Processing: Working on one issue at a time, which is significantly slower for long-running autonomous tasks.

Additional context

I am highly interested in contributing to this feature! I wanted to check with the maintainers:

  • Does this align with the current project roadmap?
  • Are there existing patterns in the codebase for session isolation that I should leverage?
  • Is anyone else in the community currently working on similar parallel execution features?
Originally created by @dzianisv on GitHub (Feb 9, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request **Is your feature request related to a problem?** I am currently working on 3 separate issues in my project and would like to tackle them in parallel using subagents. However, running multiple agents in a single working directory causes several issues: State Conflict: Agents may attempt to edit the same files or create conflicting Git states, leading to file lock issues or corrupted staging. Lack of Control: There is currently no mechanism to follow up with or control individual subagents once they are spun up in the same session. UI Clutter: Without a way to isolate and switch between active tasks, the workflow becomes difficult to track. **Describe the solution you'd like I propose an integrated system for managing parallel agent workflows through** Git Worktrees and a Tabbed Interface: Worktree-based Session Isolation: A tool for opencode that automates the creation of a new session in a fresh Git worktree. This ensures that each agent has its own isolated file system and Git state, preventing environment interference. Session Tabs (UI/TUI): A tabbed navigation system (for both Web and TUI) that allows users to switch between active worktree sessions. This would allow a user to monitor "Subagent A" in one tab while providing feedback to "Subagent B" in another. **Describe alternatives you've considered** Manual Worktree Management: Creating worktrees manually and opening new terminal instances, but this lacks the unified agent orchestration and UI integration that opencode aims to provide. Sequential Processing: Working on one issue at a time, which is significantly slower for long-running autonomous tasks. **Additional context** I am highly interested in contributing to this feature! I wanted to check with the maintainers: - Does this align with the current project roadmap? - Are there existing patterns in the codebase for session isolation that I should leverage? - Is anyone else in the community currently working on similar parallel execution features?
yindo added the discussion label 2026-02-16 18:11:13 -05:00
yindo commented 2026-02-16 18:11:13 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This is an interesting feature request! I noticed there's already related work being discussed in #12548 regarding Chrome-style tabs for multi-session workflows. You may want to check that issue to see if there's overlap or potential collaboration opportunities.

Also note that #12759 documents existing worktree functionality that's currently being worked on, which may be relevant context for your proposal.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This is an interesting feature request! I noticed there's already related work being discussed in #12548 regarding Chrome-style tabs for multi-session workflows. You may want to check that issue to see if there's overlap or potential collaboration opportunities. Also note that #12759 documents existing worktree functionality that's currently being worked on, which may be relevant context for your proposal.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8936
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?