[GH-ISSUE #18717] issue: New chats fail to set a distinct chat title #57349

Closed
opened 2026-05-05 20:52:50 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @ITankForCAD on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18717

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.34

Ollama Version (if applicable)

No response

Operating System

Fedora 43

Browser (if applicable)

Zen Browser (Firefox 144)

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 title generation with a task model is disabled, the chat title should be set as the first few words of the user prompt.

Actual Behavior

New chats set the chat title as : New Chat. From the network requests, it seems that the call to api/v1/chats/new occurs before the chat completion, which sets the generic title of "New Chat". See the images below. I don't know if this is the desired behavior as it seems counter-intuitive.

Image Image

Saving a temporary chat sets the chat title correctly. From the network requests, it seems that saving a temporary chat calls api/v1/chats/new after chat completion, which is expected.

Steps to Reproduce

Reproduce issue:

  1. Run latest OWUI version
  2. Create a new chat with any model
  3. Use a simple test prompt like "hello" <--- Chat title is then expected to be "hello"
  4. Open the sidebar and note the chat title

Reproduce expected behavior:

  1. Run latest OWUI version
  2. Create a temporary chat with any model
  3. Use a simple test prompt like "hello" <--- Chat title is then expected to be "hello"
  4. Save the temporary chat
  5. Open the sidebar and note the chat title

Logs & Screenshots

Image

The chats with correct titles were temporary chats that were subsequently saved.

Additional Information

The first occurrence of this issue started around Oct. 9th which is right after release 0.6.33.

Originally created by @ITankForCAD on GitHub (Oct 29, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18717 ### 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 am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.34 ### Ollama Version (if applicable) _No response_ ### Operating System Fedora 43 ### Browser (if applicable) Zen Browser (Firefox 144) ### 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 title generation with a task model is disabled, the chat title should be set as the first few words of the user prompt. ### Actual Behavior New chats set the chat title as : New Chat. From the network requests, it seems that the call to api/v1/chats/new occurs before the chat completion, which sets the generic title of "New Chat". See the images below. I don't know if this is the desired behavior as it seems counter-intuitive. <img width="691" height="510" alt="Image" src="https://github.com/user-attachments/assets/da364ec0-b4e7-4c1d-a93f-71d70b2af906" /> <img width="1280" height="665" alt="Image" src="https://github.com/user-attachments/assets/541461bf-3875-4dd1-931a-0360ebd3bee1" /> Saving a temporary chat sets the chat title correctly. From the network requests, it seems that saving a temporary chat calls api/v1/chats/new after chat completion, which is expected. ### Steps to Reproduce Reproduce issue: 1. Run latest OWUI version 2. Create a new chat with any model 3. Use a simple test prompt like "hello" <--- Chat title is then expected to be "hello" 4. Open the sidebar and note the chat title Reproduce expected behavior: 1. Run latest OWUI version 2. Create a temporary chat with any model 3. Use a simple test prompt like "hello" <--- Chat title is then expected to be "hello" 4. Save the temporary chat 5. Open the sidebar and note the chat title ### Logs & Screenshots <img width="432" height="440" alt="Image" src="https://github.com/user-attachments/assets/981de916-4e6d-4e12-b9ec-aa7be071a02f" /> The chats with correct titles were temporary chats that were subsequently saved. ### Additional Information The first occurrence of this issue started around Oct. 9th which is right after release 0.6.33.
GiteaMirror added the bug label 2026-05-05 20:52:50 -05:00
Author
Owner

@silentoplayz commented on GitHub (Oct 29, 2025):

I am able to reproduce this issue on the latest dev commit of Open WebUI with Title Auto-Generation toggled off in the user Interface settings.

I've tested this issue twice to ensure it wasn't a fluke the first time.
Image

<!-- gh-comment-id:3462607835 --> @silentoplayz commented on GitHub (Oct 29, 2025): I am able to reproduce this issue on the latest `dev` commit of Open WebUI with `Title Auto-Generation` toggled off in the user `Interface` settings. I've tested this issue twice to ensure it wasn't a fluke the first time. <img width="255" height="164" alt="Image" src="https://github.com/user-attachments/assets/0ea45deb-9c8c-4464-86dd-963f1418419e" />
Author
Owner

@mlkt commented on GitHub (Oct 30, 2025):

Me too. I have already seen in the browser console that /api/v1/tasks/title/completions successfully returned a new title, but the web interface did not take effect, and the title remains as New Chat.

<!-- gh-comment-id:3470314142 --> @mlkt commented on GitHub (Oct 30, 2025): Me too. I have already seen in the browser console that `/api/v1/tasks/title/completions` successfully returned a new title, but the web interface did not take effect, and the title remains as `New Chat`.
Author
Owner

@acomarcho commented on GitHub (Oct 31, 2025):

Introduced a fix for the case reproduced by @silentoplayz in https://github.com/open-webui/open-webui/pull/18761 !

<!-- gh-comment-id:3474083907 --> @acomarcho commented on GitHub (Oct 31, 2025): Introduced a fix for the case reproduced by @silentoplayz in https://github.com/open-webui/open-webui/pull/18761 !
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#57349