[Fix] Discord request_user_input pauses again after user answers#583
Merged
Conversation
Post structured prompts with option buttons in Discord, queue answers from text replies and button clicks, and deliver them to the harness so agents resume instead of re-asking after replies like "Minor".
Contributor
Author
Use a Slack-style Redis compare-and-set so concurrent Discord replies cannot both enqueue an answer and flip submitted state before the harness resumes.
mrubens
marked this pull request as ready for review
July 19, 2026 14:49
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 19, 2026 14:49
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
1 participant
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.
What changed
Discord now supports structured
request_user_inputthe way Slack does:minor/1/ option labels are parsed against the pending promptThis fixes the release-flow failure where answering “Minor” still left the agent paused waiting for the bump level.
Why this change was made
Discord had lifecycle tools and guidance for
request_user_input, but no end-to-end rendering/answer path. The harness stayed blocked on the OpenCode question tool while Discord only forwarded plain text, so the agent often re-asked after the user had already answered.Impact
On Discord-started tasks, structured questions can be answered in-thread via buttons or text and the run resumes, matching Slack’s behavior for the common single-question case. Multi-question prompts accept one answer per line of text; option buttons are limited to single-question prompts.