fix(opencode): preserve command scope in subtask continuation message - #41874
jaysonvirissimo wants to merge 1 commit into
Conversation
Sorry, something went wrong.
After a subtask command completes, opencode injects a synthetic user message that says "continue with your task". The parent agent can read this as permission to act beyond the command scope. For example, it can start to fix findings from the review-only /review command. Change the message to name the command and defer further action to the user. Also restore the comment that explains why the message must exist. Fixes anomalyco#41866
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Sorry, something went wrong.
Issue for this PR
Closes #41866
Type of change
What does this PR do?
The synthetic user message injected after a user-invoked subtask command says "continue with your task".
But for the/review command, that strongly suggests the model should fix any findings the subtask reported.
This is unfortunate, since when you run that command you expect it to review a PR, not try to fix everything wrong with it.
The message itself cannot be removed.
PR #5650 added it because reasoning models like Gemini error when an assistant message has no user message after it.
So this PR keeps the message but changes its text.
The new text names the command that ran, asks for a summary of the output, and defers any further action to the user.
It also restores the code comment from #5650 that explains why the message must exist.
How did you verify your code works?
Screenshots / recordings
Not a UI change.
Checklist