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

[PR #14976] [CLOSED] Update follow ups handling to be more robust #62522

New Issue
Closed
opened 2026-05-06 06:42:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-06 06:42:22 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14976
Author: @skuovo
Created: 6/14/2025
Status: ❌ Closed

Base: dev ← Head: patch-1

📝 Commits (1)

  • f0831ce Update follow ups handling to be more robust

📊 Changes

1 file changed (+23 additions, -7 deletions)

View changed files

📝 backend/open_webui/utils/middleware.py (+23 -7)

📄 Description

Follow ups seem to be received in one of the 3 formats, depending on how the LLM responds.

  1. JSON dict as requested, with a "follow_ups" key and list value.
  2. JSON list value, without the dict.
  3. A numeric bullet-point delimited string, using 1. XXX\n2. XXX\n3. XXX

This change allows all 3 to be handled gracefully, increasing the chances the follow ups are displayed.

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/14976 **Author:** [@skuovo](https://github.com/skuovo) **Created:** 6/14/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`f0831ce`](https://github.com/open-webui/open-webui/commit/f0831ce64ab2a82d6b673c4285e485c8c886d763) Update follow ups handling to be more robust ### 📊 Changes **1 file changed** (+23 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/utils/middleware.py` (+23 -7) </details> ### 📄 Description Follow ups seem to be received in one of the 3 formats, depending on how the LLM responds. 1. JSON dict as requested, with a "follow_ups" key and list value. 2. JSON list value, without the dict. 3. A numeric bullet-point delimited string, using 1. XXX\n2. XXX\n3. XXX This change allows all 3 to be handled gracefully, increasing the chances the follow ups are displayed. ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-06 06:42:22 -05:00
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 pull-request
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#62522
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?