github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #21142] feat: Store generated Follow up prompts with historical responses. #58062

New Issue
Closed
opened 2026-05-05 22:15:44 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-05 22:15:44 -05:00
Owner
Copy Link

Originally created by @jkassie on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21142

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

When using Open WebUI to explore a knowledge base I find the Follow up questions very useful but am frustrated they disappear as soon as you select one of them. I end up having to copy them to a separate document so I can manually iterate across multiple questions.

Desired Solution you'd like

Store generated Follow up questions with the answer as an expandable field (similar to how Sources works). Even if you have to manually copy and paste historical values below, it would still be useful to see what was generated for each response.

Alternatives Considered

No response

Additional Context

No response

Originally created by @jkassie on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21142 ### 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 When using Open WebUI to explore a knowledge base I find the Follow up questions very useful but am frustrated they disappear as soon as you select one of them. I end up having to copy them to a separate document so I can manually iterate across multiple questions. ### Desired Solution you'd like Store generated Follow up questions with the answer as an expandable field (similar to how Sources works). Even if you have to manually copy and paste historical values below, it would still be useful to see what was generated for each response. ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2026-05-05 22:15:45 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Feb 4, 2026):

⚠️ Invalid Issue Title

Hey @jkassie, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.

Please update the title to reflect the content of your issue.

⚠️ Missing Issue Title Prefix

@jkassie, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:3844732641 --> @pr-validator-bot commented on GitHub (Feb 4, 2026): # ⚠️ Invalid Issue Title Hey @jkassie, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues. Please update the title to reflect the content of your issue. --- # ⚠️ Missing Issue Title Prefix @jkassie, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-05-05 22:15:46 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Feb 4, 2026):

I'm almost certain you'd be happy to know that these toggles exist in the Interface settings tab within the user settings menu. Particularly, both Keep Follow-Up Prompts in Chat and Insert Follow-Up Prompt to Input options are what you want toggled On to have the behavior you desire within your Open WebUI instance for follow-up prompts.

Image

Also, shameless self-plug for my very recently created Regenerate Followups action button. You will likely want this added to your Open WebUI instance. Feel free to give it a try and let me know what you think!

<!-- gh-comment-id:3848113911 --> @silentoplayz commented on GitHub (Feb 4, 2026): I'm almost certain you'd be happy to know that these toggles exist in the `Interface` settings tab within the user settings menu. Particularly, both `Keep Follow-Up Prompts in Chat` and `Insert Follow-Up Prompt to Input` options are what you want toggled `On` to have the behavior you desire within your Open WebUI instance for follow-up prompts. <img width="1103" height="94" alt="Image" src="https://github.com/user-attachments/assets/a23c8998-ac48-4a55-84eb-4d449b707fe2" /> Also, shameless self-plug for my very recently created [Regenerate Followups](https://openwebui.com/posts/regenerate_followups_9b5ac6d6) action button. You will likely want this added to your Open WebUI instance. Feel free to give it a try and let me know what you think!
GiteaMirror commented 2026-05-05 22:15:46 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 4, 2026):

nice even i didnt know this

will add this to docs

<!-- gh-comment-id:3848683448 --> @Classic298 commented on GitHub (Feb 4, 2026): nice even i didnt know this will add this to docs
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58062
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?