I have an initial AI agent that outputs a widget which presents the user with two choices. How can I detect what option the user chose in order to continue the flow from there (branching depending on choice)? The flow simply continues without waiting for the user's choice. Using Agent Builder.
#How can I extract user choice from a widget inside the agent builder to branch the flow's logic?
elfin flare
wraith onyxBOT
Hi @elfin flare. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
The knowledge sources indicate that what you want is not yet supported in Agent Builder.
An official support reply on this exact question says that OpenAI is “working to build a mechanism to get state information about widget” and that this capability is planned but not yet publicly available.[Widget state forum]
Because of that:
- The workflow cannot currently read checkbox / button state from a widget inside Agent Builder.
- You therefore cannot branch logic directly based on a user’s widget choice in the way you describe.
- The flow will indeed just continue, as you’re observing, because there is no built‑in way yet for the workflow to “wait for” and consume widget state.
If you need this behavior now, you’d have to implement it outside of Agent Builder (for example, handling widget actions on your own backend and then deciding what to call next), but the provided knowledge sources do not document a supported pattern for doing this inside Agent Builder itself.
So, with the current documented capabilities, what you’re trying to do is not yet possible directly in Agent Builder.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
elfin flare
@wraith onyx so it's impossible to make the flow wait for the user input? let's cover that.
wraith onyxBOT
Let me check the knowledge base for you again. One moment! :books:
Based on the available information, Agent Builder currently cannot read widget state or branch on it, and that’s the core blocker for “waiting” on a widget choice inside the same workflow.
An official support response on this exact topic says they are “working to build a mechanism to get state information about widget” and that this will be launched later, implying that the mechanism does not exist yet.[Widget state forum]
What this means for your case:
- You can have an agent output a widget with choices.
- But the workflow cannot currently access which option the user picked, so:
- You cannot branch logic based on that choice inside Agent Builder.
- You also cannot make the flow “pause” and then resume with different branches depending on the widget selection, because there is no way for the workflow to consume that selection as input.