github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 23:21:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #14697] issue: Manually triggered generation of conversation-titles takes the wrong chat-ID for context. #17337

New Issue
Closed
opened 2026-04-19 23:04:32 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-19 23:04:32 -05:00
Owner
Copy Link

Originally created by @lineg-it on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14697

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.13-cuda

Ollama Version (if applicable)

No response

Operating System

Linux Debian 12

Browser (if applicable)

Edge (137.0.3296.52)

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

By double-clicking a chat within the chat-overview, a button appears on the right of the title, which generates titles using the selected task model.
By clicking, the corresponding task-model should generate a title based on the context of the chat that I clicked the title of.

Actual Behavior

The title is generated as if the context of another chat is taken into account.
Seems to me like an issue while iterating through chat-ids, selecting the right one .. or something similar maybe?

Steps to Reproduce

  1. Create 2 chats (at minimum, with very different topics)
  2. Doubleclick the first chat in the list to enter title-editing mode.
  3. Click on the Icon "Generate"
  4. A title appears, but represents the wrong topic / chat-context.

Logs & Screenshots

N/A

Additional Information

Just a quick draw.. sorry for inconsistent formatting etc.

Originally created by @lineg-it on GitHub (Jun 5, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14697 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.13-cuda ### Ollama Version (if applicable) _No response_ ### Operating System Linux Debian 12 ### Browser (if applicable) Edge (137.0.3296.52) ### 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 By double-clicking a chat within the chat-overview, a button appears on the right of the title, which generates titles using the selected task model. By clicking, the corresponding task-model should generate a title based on the context of the chat that I clicked the title of. ### Actual Behavior The title is generated as if the context of another chat is taken into account. Seems to me like an issue while iterating through chat-ids, selecting the right one .. or something similar maybe? ### Steps to Reproduce 1. Create 2 chats (at minimum, with very different topics) 2. Doubleclick the first chat in the list to enter title-editing mode. 3. Click on the Icon "Generate" 4. A title appears, but represents the wrong topic / chat-context. ### Logs & Screenshots N/A ### Additional Information Just a quick draw.. sorry for inconsistent formatting etc.
GiteaMirror added the bug label 2026-04-19 23:04:32 -05:00
GiteaMirror commented 2026-04-19 23:04:33 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jun 5, 2025):

Might be addressed with 0b84b22b4e in dev, testing wanted here

<!-- gh-comment-id:2945642225 --> @tjbck commented on GitHub (Jun 5, 2025): Might be addressed with 0b84b22b4eeaaf49f594553acccb00fb23757164 in dev, testing wanted here
GiteaMirror commented 2026-04-19 23:04:33 -05:00
Author
Owner
Copy Link

@v1-valux commented on GitHub (Jun 5, 2025):

As of latest (v0.6.13-cuda), it depends on where the chat is located in the list ..

I just took an old chat somewhere in the middle and re-generated the correct topic first try.
After that, the chat got pushed up (to "Today"), and every other title generation (of this chat) went wrong.
(reproducable)

I can't test dev yet

EDIT: Aside the actual problem, is pushing the chat up a known behaviour in llm UIs, if only the title got (accidentally) re-generated? This maybe just seems odd to me

<!-- gh-comment-id:2946140118 --> @v1-valux commented on GitHub (Jun 5, 2025): As of latest (v0.6.13-cuda), it depends on where the chat is located in the list .. I just took an old chat somewhere in the middle and re-generated the correct topic first try. After that, the chat got pushed up (to "Today"), and every other title generation (of this chat) went wrong. (reproducable) I can't test dev yet EDIT: Aside the actual problem, is pushing the chat up a known behaviour in llm UIs, if only the title got (accidentally) re-generated? This maybe just seems odd to me
GiteaMirror commented 2026-04-19 23:04:34 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Jun 16, 2025):

Commenting to say that I might've experienced the same (or a very similar) issue last month that OP has described in this issue thread. See the attached Discord messages screenshots for reference.

Image
Image

<!-- gh-comment-id:2974996827 --> @silentoplayz commented on GitHub (Jun 16, 2025): Commenting to say that I might've experienced the same (or a very similar) issue last month that OP has described in this issue thread. See the attached Discord messages screenshots for reference. ![Image](https://github.com/user-attachments/assets/2f26927e-bc3a-4c88-8e33-5e82353147d6) ![Image](https://github.com/user-attachments/assets/2e1bc074-35df-4fe0-86a4-5725b13e0474)
GiteaMirror commented 2026-04-19 23:04:34 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jun 16, 2025):

@v1-valux was this addressed with 0.6.14?

<!-- gh-comment-id:2975818519 --> @tjbck commented on GitHub (Jun 16, 2025): @v1-valux was this addressed with 0.6.14?
GiteaMirror commented 2026-04-19 23:04:34 -05:00
Author
Owner
Copy Link

@v1-valux commented on GitHub (Jun 16, 2025):

As of 0.6.14, I have not been able to reproduce the issues observed from above.
Seems to be fixed.

<!-- gh-comment-id:2976059288 --> @v1-valux commented on GitHub (Jun 16, 2025): As of 0.6.14, I have not been able to reproduce the issues observed from above. Seems to be fixed.
GiteaMirror commented 2026-04-19 23:04:35 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Jun 16, 2025):

As of 0.6.14, I have not been able to reproduce the issues observed from above. Seems to be fixed.

I agree. This is likely fixed as of v0.6.14, as I am unable to reproduce the issue any longer.

<!-- gh-comment-id:2976569648 --> @silentoplayz commented on GitHub (Jun 16, 2025): > As of 0.6.14, I have not been able to reproduce the issues observed from above. Seems to be fixed. I agree. This is likely fixed as of v0.6.14, as I am unable to reproduce the issue any longer.
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#17337
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?