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

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?