[GH-ISSUE #24710] feat: Allow check actions in checkboxes in responses to be used as input in the next request #91122

New Issue

GiteaMirror · 2026-05-15T16:24:09-05:00

GiteaMirror commented

2026-05-15 16:24:09 -05:00

Originally created by @zaakiy on GitHub (May 14, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24710

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

I use the following promt:

...
Ask me any clarifying questions if required, though give me multiple choice options to make it easier for me to respond.
...

This produces a response like the following:

...
...

Q1 — What is the observable failure mode?

A. Scan results are wrong — pairs missed or false positives
B. Export is wrong — transfers emit to wrong accounts or malformed journal
C. API crashes / errors on transfer scan requests
D. Duplicate scanning — dedup keys not working, same pairs re-detected
E. Architecture mismatch — code references dropped fields/columns, ORM models out of sync with DB schema
F. Worker jobs stuck/crash on startup
G. Something else (describe briefly)

Q2 — Which layer(s) are affected?

A. All of them (detector + worker + API + export + frontend)
B. Backend only (detector, worker, or export)
C. Export only (beancount writer doesn't handle transfers correctly)
D. Scanner only (detector logic is wrong, API/routes OK)
E. Schema only (DB model mismatch)

Q3 — When did you notice this? Any recent changes?

A. Always been broken
B. After a recent refactor/phase merge
C. Noticed during testing/production use today
D. You haven't tested it yet, just spotted it in code review

...
...

If I check the boxes, nothing happens

Desired Solution you'd like

I want to be able to check the boxes and the system will then use my responses based on what I checked.

Alternatives Considered

No response

Additional Context

No response

Originally created by @zaakiy on GitHub (May 14, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24710 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description I use the following promt: ``` ... Ask me any clarifying questions if required, though give me multiple choice options to make it easier for me to respond. ... ``` This produces a response like the following: ... ... **Q1 — What is the observable failure mode?** - [ ] A. Scan results are wrong — pairs missed or false positives - [ ] B. Export is wrong — transfers emit to wrong accounts or malformed journal - [ ] C. API crashes / errors on transfer scan requests - [ ] D. Duplicate scanning — dedup keys not working, same pairs re-detected - [ ] E. Architecture mismatch — code references dropped fields/columns, ORM models out of sync with DB schema - [ ] F. Worker jobs stuck/crash on startup - [ ] G. Something else (describe briefly) **Q2 — Which layer(s) are affected?** - [ ] A. All of them (detector + worker + API + export + frontend) - [ ] B. Backend only (detector, worker, or export) - [ ] C. Export only (beancount writer doesn't handle transfers correctly) - [ ] D. Scanner only (detector logic is wrong, API/routes OK) - [ ] E. Schema only (DB model mismatch) **Q3 — When did you notice this? Any recent changes?** - [ ] A. Always been broken - [ ] B. After a recent refactor/phase merge - [ ] C. Noticed during testing/production use today - [ ] D. You haven't tested it yet, just spotted it in code review ... ... If I check the boxes, nothing happens ### Desired Solution you'd like I want to be able to check the boxes and the system will then use my responses based on what I checked. ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror commented

2026-05-15 16:24:10 -05:00

@owui-terminator[bot] commented on GitHub (May 14, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

🟣 #23468 feat: support structured follow-up questions/options in assistant output
This is the closest match: it asks for structured follow-up questions/options in assistant output and for clicking an option to send it as the next user input automatically. The new issue is specifically about checkboxes in responses being usable as the next request input, which is the same interaction pattern.
by ShirasawaSama
🟣 #14269 issue: How to add a selection box function
This older issue describes rendering model output as selectable options that, when clicked, are filled into the input box and can then be sent. It overlaps with the requested checkbox-to-input workflow, though it is framed more generally as a selection box.
by zmwstu · bug
🟣 #19596 feat: Improve Checkboxes on Prompt Variable Forms - allow placeholder
This is related only in that it concerns checkboxes in prompt/UI forms, but it is about checkbox labels/placeholders rather than using assistant-response checkboxes as interactive input. It is a weaker but still adjacent match.
by Classic298

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

@owui-terminator[bot] commented on GitHub (May 14, 2026):  🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#23468](https://github.com/open-webui/open-webui/issues/23468) **feat: support structured follow-up questions/options in assistant output** *This is the closest match: it asks for structured follow-up questions/options in assistant output and for clicking an option to send it as the next user input automatically. The new issue is specifically about checkboxes in responses being usable as the next request input, which is the same interaction pattern.* *by ShirasawaSama* 2. 🟣 [#14269](https://github.com/open-webui/open-webui/issues/14269) **issue: How to add a selection box function** *This older issue describes rendering model output as selectable options that, when clicked, are filled into the input box and can then be sent. It overlaps with the requested checkbox-to-input workflow, though it is framed more generally as a selection box.* *by zmwstu · `bug`* 3. 🟣 [#19596](https://github.com/open-webui/open-webui/issues/19596) **feat: Improve Checkboxes on Prompt Variable Forms - allow placeholder** *This is related only in that it concerns checkboxes in prompt/UI forms, but it is about checkbox labels/placeholders rather than using assistant-response checkboxes as interactive input. It is a weaker but still adjacent match.* *by Classic298* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#91122