github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22669] issue: Excess Prompt-based chat title naming on regeneration/branching #58448

New Issue
Closed
opened 2026-05-05 23:11:00 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 23:11:00 -05:00
Owner
Copy Link

Originally created by @a4lg on GitHub (Mar 14, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22669

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.8.10 dev

Ollama Version (if applicable)

No response

Operating System

CachyOS (Arch Linux-based)

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When the chat is created and the title is named manually, no further automatic chat naming does not happen unless otherwise requested.

Actual Behavior

If "Title Auto-Generation" is disabled, prompt-based automatic naming occurs if the message count of the current thread is exactly two.

If this is the new thread, that's fine (because total message count in the chat would be also two). However, regenerating the first response and/or editing the first prompt also triggers this automatic naming after the AI responds (usually, total message count in the chat would be 3 or greater in these cases).

Steps to Reproduce

  1. On the User settings, make sure that "Interface → Title Auto-Generation" is disabled.
  2. Create a new chat (single turn) with a test prompt like "Hello." After the AI responds, the chat should have been renamed based on the prompt.
  3. Rename that chat manually.
  4. Return to that chat then either (a) press "Regenerate" button or (b) edit the first prompt and submit.
  5. After the AI responds, the chat is renamed based on the prompt, erasing user-named title.

Logs & Screenshots

Here's the screenshots after performing steps 2, 3 and 5.

Step 2 finished (total message count of that chat is 2):
Image

Step 3 finished (and right before the Step 4):
Image

Step 5 finished (total message count of that chat is 3):
Image

Additional Information

The direct cause is already identified (see #22754).

I already have a short-term fix (https://github.com/a4lg/open-webui/tree/fix-title-naming-on-first-response) but this is not a long-term fix. I would like to hear your thoughts before submitting my PR (both my test fix and this issue in general).

Originally created by @a4lg on GitHub (Mar 14, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22669 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.8.10 dev ### Ollama Version (if applicable) _No response_ ### Operating System CachyOS (Arch Linux-based) ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When the chat is created and the title is named manually, no further automatic chat naming does not happen unless otherwise requested. ### Actual Behavior If "Title Auto-Generation" is disabled, prompt-based automatic naming occurs if the message count *of the current thread* is exactly two. If this is the new thread, that's fine (because *total message count in the chat would be also two*). However, regenerating the first response and/or editing the first prompt also triggers this automatic naming after the AI responds (usually, *total* message count in the chat would be 3 or greater in these cases). ### Steps to Reproduce 1. On the User settings, make sure that "Interface → Title Auto-Generation" is disabled. 2. Create a new chat (single turn) with a test prompt like "Hello." After the AI responds, the chat should have been renamed based on the prompt. 3. Rename that chat manually. 4. Return to that chat then either (a) press "Regenerate" button or (b) edit the first prompt and submit. 5. After the AI responds, the chat is renamed based on the prompt, erasing user-named title. ### Logs & Screenshots Here's the screenshots after performing steps 2, 3 and 5. Step 2 finished (total message count of that chat is **2**): <img width="1156" height="615" alt="Image" src="https://github.com/user-attachments/assets/b7f9ee9b-095e-420e-9b2f-7d5a36bc2028" /> Step 3 finished (and right before the Step 4): <img width="1156" height="615" alt="Image" src="https://github.com/user-attachments/assets/fcffb594-7603-4b5a-b5c6-c7cb5ebf115c" /> Step 5 finished (total message count of that chat is **3**): <img width="1156" height="615" alt="Image" src="https://github.com/user-attachments/assets/91212a80-102d-4ec7-8369-ab7539bf87d2" /> ### Additional Information The direct cause is already identified (see #22754). I already have a short-term fix (https://github.com/a4lg/open-webui/tree/fix-title-naming-on-first-response) but this is not a long-term fix. I would like to hear your thoughts before submitting my PR (both my test fix and this issue in general).
GiteaMirror added the bug label 2026-05-05 23:11:00 -05:00
GiteaMirror commented 2026-05-05 23:11:04 -05:00
Author
Owner
Copy Link

@a4lg commented on GitHub (Mar 17, 2026):

Now, my PR for a short-term fix is submitted.

<!-- gh-comment-id:4073806427 --> @a4lg commented on GitHub (Mar 17, 2026): Now, my PR for a short-term fix is submitted.
GiteaMirror commented 2026-05-05 23:11:05 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Mar 21, 2026):

877bc23afc

<!-- gh-comment-id:4104925617 --> @Classic298 commented on GitHub (Mar 21, 2026): https://github.com/open-webui/open-webui/commit/877bc23afc2d0f6279ee9428a2efb388715680ea
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 bug
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#58448
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?