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

[FEATURE]: QOL improvement of plan -> build #2995

New Issue
Open
opened 2026-02-16 17:38:11 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:38:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @aymuos15 on GitHub (Nov 20, 2025).

Originally assigned to: @rekram1-node 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

When we plan something and it finishes, we have to switch to the build agent and then type in something to actually let it build. I find this unintuitive. Claude code for example gives the option to continue planning or start to build with a simple multiple choice. This I feel should be the way. I doubt anyone is switching to any other agent bar build after planning.

Would this be something within the pipeline?

Originally created by @aymuos15 on GitHub (Nov 20, 2025). Originally assigned to: @rekram1-node 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 When we plan something and it finishes, we have to switch to the build agent and then type in something to actually let it build. I find this unintuitive. Claude code for example gives the option to continue planning or start to build with a simple multiple choice. This I feel should be the way. I doubt anyone is switching to any other agent bar build after planning. Would this be something within the pipeline?
yindo added the discussion label 2026-02-16 17:38:11 -05:00
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

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

Yeah we are gonna fix this

@rekram1-node commented on GitHub (Nov 20, 2025): Yeah we are gonna fix this
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@TreeOfLearning commented on GitHub (Nov 20, 2025):

Please let this be a choice. One of the things I vastly prefer with opencode vs claude code is that I can type something to initiate the switch.. For example, sometimes the plan will just need a tiny tweak, and I can just write "begin implementation, but ensure that XYZ does {something slightly different to the plan}"

Vastly more token efficient than claude code and for me, a much more expressive and powerful workflow.

@TreeOfLearning commented on GitHub (Nov 20, 2025): Please let this be a choice. One of the things I vastly prefer with opencode vs claude code is that I _can_ type something to initiate the switch.. For example, sometimes the plan will just need a tiny tweak, and I can just write "begin implementation, but ensure that XYZ does {something slightly different to the plan}" Vastly more token efficient than claude code and for me, a much more expressive and powerful workflow.
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@aymuos15 commented on GitHub (Nov 21, 2025):

In my experience I feel the degrade (mostly minor) for this very reason because it causes an unwanted stir even with simple prompts to the build agent. It is only a "nice to have" for me, so not something breaking. If more people prefer what you said, the norm now should stick then.

@aymuos15 commented on GitHub (Nov 21, 2025): In my experience I feel the degrade (mostly minor) for this very reason because it causes an unwanted stir even with simple prompts to the build agent. It is only a "nice to have" for me, so not something breaking. If more people prefer what you said, the norm now should stick then.
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@kylerm42 commented on GitHub (Nov 21, 2025):

IMO this should be a configurable permission on all agents, whether to ask, allow, or deny switching to other agents. This would greatly improve the ability to create custom agent workflows.

# simple config
permission:
  call_agent: allow # or ask, deny

# advanced config
permission:
  call_agent:
    build: allow
    review: ask
    "*": deny
@kylerm42 commented on GitHub (Nov 21, 2025): IMO this should be a configurable permission on all agents, whether to ask, allow, or deny switching to other agents. This would greatly improve the ability to create custom agent workflows. ```yaml # simple config permission: call_agent: allow # or ask, deny # advanced config permission: call_agent: build: allow review: ask "*": deny ```
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#2995
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?