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

[FEATURE]: tmux-based subagent spawning for observable parallel execution #4222

New Issue
Closed
opened 2026-02-16 17:43:05 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:43:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @werkamsus on GitHub (Jan 5, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

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

Describe the enhancement you want to request

Problem: Subagents run silently in-process. When running multiple parallel tasks, there's no way to observe them in real-time or debug a stuck agent.

Proposal: Optional tmux-based subagent spawning.

// opencode.json
{
  "subagent": {
    "spawn": "tmux"  // "inline" (default) | "tmux"
  }
}

When enabled, task tool invocations spawn in tmux panes/windows instead of inline:

  • Watch multiple subagents work simultaneously in split panes
  • Attach to a stuck subagent and intervene
  • Sessions persist if main terminal disconnects
  • Results still returned to parent via IPC (temp file, socket, etc.)

Why tmux: Battle-tested, already installed on most dev machines, handles pane layout automatically.

Open questions:

  • Pane vs window per subagent?
  • Layout strategy for 4+ parallel agents?
  • Fallback behavior when tmux unavailable?

Happy to help prototype if there's interest.

Originally created by @werkamsus on GitHub (Jan 5, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I's about to request hasn't been suggested before. ### Describe the enhancement you want to request **Problem**: Subagents run silently in-process. When running multiple parallel tasks, there's no way to observe them in real-time or debug a stuck agent. **Proposal**: Optional tmux-based subagent spawning. ```jsonc // opencode.json { "subagent": { "spawn": "tmux" // "inline" (default) | "tmux" } } ``` When enabled, `task` tool invocations spawn in tmux panes/windows instead of inline: - Watch multiple subagents work simultaneously in split panes - Attach to a stuck subagent and intervene - Sessions persist if main terminal disconnects - Results still returned to parent via IPC (temp file, socket, etc.) **Why tmux**: Battle-tested, already installed on most dev machines, handles pane layout automatically. **Open questions**: - Pane vs window per subagent? - Layout strategy for 4+ parallel agents? - Fallback behavior when tmux unavailable? Happy to help prototype if there's interest.
yindo closed this issue 2026-02-16 17:43:05 -05:00
yindo commented 2026-02-16 17:43:05 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #1247: Feature Request: Add tmux Support for Multi-Session Agent Testing - Proposes comprehensive tmux integration with similar goals of persistent sessions, parallel execution, and real-time monitoring
  • #6470: [FEATURE]: Settings for queue execution order: sequential and parallel - Related to managing parallel execution of multiple agents

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 5, 2026): This issue might be a duplicate of existing issues. Please check: - #1247: Feature Request: Add `tmux` Support for Multi-Session Agent Testing - Proposes comprehensive tmux integration with similar goals of persistent sessions, parallel execution, and real-time monitoring - #6470: [FEATURE]: Settings for queue execution order: sequential and parallel - Related to managing parallel execution of multiple agents Feel free to ignore if none of these address your specific case.
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
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#4222
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?