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]: Settings for queue execution order: sequential and parallel #4010

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

Originally created by @danielrosehill on GitHub (Dec 30, 2025).

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

(Text: mine but via STT so excuse the slightly robotic tone!)

Two ways to run tasks on a project using something like OpenCode in quick succession.

Option 1: Parallel Execution

In this method, each agent works on the codebase using Git work trees, etc.

  • Upside: This is the fastest way to crank through a bunch of changes quickly.
  • Downside: It carries the highest potential for agentic disaster through code overwrites and collisions.

Option 2: Slow and Steady

Wait for one task to finish. When the agent has given the completion signal, move on to the next one.

--

Feature Idea: Queue Execution Setting At The System or Project Level

I think it would be really cool to have a system-wide setting or project-wide setting in which the user could define their preferred mode or even change it dynamically to suit their level of risk tolerance and their appetite for debugging in a specific project.

Parallel execution: if user starts a new session, they can go at it.

Sequential execution: queue based task processing is enforced. Tasks are gated. One has to finish before another kicks off.

Potential cool AI add-on feature: small planning agent which sifts through the queue and sorts it into the most suitable order for the execution agent to work on (e.g. automatically puts existing bug fixes before new feature additions etc)

Originally created by @danielrosehill on GitHub (Dec 30, 2025). 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 (Text: mine but via STT so excuse the slightly robotic tone!) Two ways to run tasks on a project using something like OpenCode in quick succession. ### Option 1: Parallel Execution In this method, each agent works on the codebase using Git work trees, etc. * **Upside:** This is the fastest way to crank through a bunch of changes quickly. * **Downside:** It carries the highest potential for agentic disaster through code overwrites and collisions. ### Option 2: Slow and Steady Wait for one task to finish. When the agent has given the completion signal, move on to the next one. -- # Feature Idea: Queue Execution Setting At The System or Project Level I think it would be really cool to have a system-wide setting or project-wide setting in which the user could define their preferred mode or even change it dynamically to suit their level of risk tolerance and their appetite for debugging in a specific project. Parallel execution: if user starts a new session, they can go at it. Sequential execution: queue based task processing is enforced. Tasks are gated. One has to finish before another kicks off. Potential cool AI add-on feature: small planning agent which sifts through the queue and sorts it into the most suitable order for the execution agent to work on (e.g. automatically puts existing bug fixes before new feature additions etc)
yindo added the discussion label 2026-02-16 17:42:16 -05:00
yindo commented 2026-02-16 17:42:17 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 30, 2025):

This issue might be a duplicate of or closely related to existing issues. Please check:

  • #5887: [feat] True Async/Background Sub-Agent Delegation - Requests non-blocking sub-agent delegation with background execution, allowing main agents to continue interactive work while sub-agents run in parallel
  • #5895: [FEATURE]: On-idle background processing - Requests background task processing when TUI is idle, with queue-based execution patterns
  • #1970: Feature Request: Add Background Bash Execution - Requests background process execution similar to Claude Code's Ctrl+b, enabling long-running tasks without blocking
  • #5165: [FEATURE]: multi-tasking - Requests support for parallel execution of multiple commands to improve speed and resource utilization
  • #6375: [FEATURE]: Better active/background terminal and bash management - Proposes background terminal management with tools for controlling concurrent processes

These issues discuss related concepts around task execution modes, concurrency, and execution sequencing. Feel free to ignore if your specific use case for queue-based settings and planning agents differs from these.

@github-actions[bot] commented on GitHub (Dec 30, 2025): This issue might be a duplicate of or closely related to existing issues. Please check: - #5887: [feat] True Async/Background Sub-Agent Delegation - Requests non-blocking sub-agent delegation with background execution, allowing main agents to continue interactive work while sub-agents run in parallel - #5895: [FEATURE]: On-idle background processing - Requests background task processing when TUI is idle, with queue-based execution patterns - #1970: Feature Request: Add Background Bash Execution - Requests background process execution similar to Claude Code's Ctrl+b, enabling long-running tasks without blocking - #5165: [FEATURE]: multi-tasking - Requests support for parallel execution of multiple commands to improve speed and resource utilization - #6375: [FEATURE]: Better active/background terminal and bash management - Proposes background terminal management with tools for controlling concurrent processes These issues discuss related concepts around task execution modes, concurrency, and execution sequencing. Feel free to ignore if your specific use case for queue-based settings and planning agents differs from these.
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#4010
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?