don't change current agent#564
Merged
backnotprop merged 1 commit intobacknotprop:mainfrom Apr 15, 2026
Merged
Conversation
agent_cycle is not the correct command as the user may have several agents defined, not only build and plan
Owner
|
There is a setting in the UI, does that not work for you? You can disable agent switching |
Contributor
Author
|
@backnotprop it's 2 different things. I want that option enabled, so that an approval triggers the build agent to implement the plan. Disabling the option disables the agent cycle but also the automatic implementation in |
Owner
|
I understand. That's an oversight on my part. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
agent_cycle is not the correct command as the user may have several agents defined, not only build and plan.
I do think that the changes introduced in #40 make sense, that is "not only run the plan with the build agent, but also switch the agent to build" - but in its current format, it is simply buggy as it assumes only a build and plan agent.
I checked the opencode sourcecode and I'm not sure what is the alternative. Cycle and validate that the current agent is the target agent, if not repeat?!