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 #18877] issue: Chat title remains "New Chat" after regenerating response - no auto-title generation #34230

New Issue
Closed
opened 2026-04-25 08:08:16 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 08:08:16 -05:00
Owner
Copy Link

Originally created by @cjl-dayeonepark on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18877

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

Git Clone

Open WebUI Version

v0.6.32

Operating System

Windows 11

Browser (if applicable)

Chrome

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 regenerating a response in a new chat, the title should be automatically generated based on the conversation content after the regenerated response is completed.

Specifically:

  1. User starts a new chat (shows "새 채팅")
  2. User sends a message and gets a response
  3. User regenerates the response using "Regenerate Response"
  4. After the regenerated response completes, the chat title should automatically change from "새 채팅" to a meaningful title reflecting the conversation topic (e.g., "Artificial Intelligence Explanation")

This should happen automatically since:

  • Title Generation is enabled in Admin panel > Settings > Interface
  • Title Auto-Generation is enabled and working for regular new chats
  • Title generation prompts are functioning correctly in other scenarios

Actual Behavior

The chat title remains as "새 채팅" (New Chat) even after regenerating responses.

Specifically:

  1. User starts a new chat (shows "새 채팅")
  2. User sends a message and gets a response
  3. User regenerates the response using "Regenerate Response"
  4. The regenerated response completes successfully
  5. The chat title still shows "새 채팅(New Chat)" - no automatic title generation occurs
  6. User must manually click the pen icon and edit the title

The response regeneration does not trigger the automatic title generation function, despite:

  • Title generation being enabled in settings
  • Title auto-generation working correctly for regular new chats
  • All title generation infrastructure being functional

Steps to Reproduce

Prerequisites:

  • Admin panel > Settings > Interface > Title Generation is ENABLED

Reproduction Steps:

  1. Open Open WebUI in browser
  2. Click "New Chat" to start a new conversation
  3. Type any message (e.g., "What is artificial intelligence?")
  4. Wait for the AI response to begin generating
  5. Click the "stop" button to interrupt the response generation
  6. Click "Regenerate Response" button
  7. Wait for the new response to complete
  8. Observe that the chat title still shows "New Chat(새 채팅)" instead of an auto-generated title

Expected: Title should change to something like "Artificial Intelligence Explanation"
Actual: Title remains "New Chat(새 채팅)" despite Title Generation being enabled

Configuration used:

  • Default Open WebUI settings
  • No custom environment variables
  • Standard Docker setup
  • Title Generation is ENABLED
  • Title Auto-Generation is ENABLED and confirmed working for regular chats

Logs & Screenshots

“새 채팅” = “New Chat”
Image

Additional Information

This issue is particularly concerning because:

  1. Title Generation is explicitly ENABLED in the admin settings
  2. Title Auto-Generation is enabled and works correctly for regular new chats
  3. Title generation prompts are functioning properly in other scenarios
  4. The feature fails ONLY when the stop button is clicked during response generation
  5. It is unclear whether this behavior is caused by a bug in the regeneration trigger logic or if it is an intentional design decision (policy)

Confirmed working scenarios:

  • Creating a new chat and sending first message → Title auto-generates correctly
  • Title generation prompts respond properly when manually triggered
  • Title Auto-Generation setting is functional

Broken scenario:

  • Response regeneration does not trigger title generation despite all settings being enabled

This issue is similar to #18717, which reports title auto-generation failures, but since the conditions differ, it should be treated as a separate issue.

The problem suggests that:

  • Title generation infrastructure is working correctly
  • Response regeneration may not properly trigger the title generation function
  • There may be a missing event handler for regeneration scenarios

Workaround: Users can manually edit the title by clicking the pen icon next to "새 채팅" and entering a custom title.

This affects user experience as chat history becomes difficult to manage when all chats are named "새 채팅", especially when the title generation feature is confirmed to be working in other contexts.

Originally created by @cjl-dayeonepark on GitHub (Nov 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18877 ### 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 Git Clone ### Open WebUI Version v0.6.32 ### Operating System Windows 11 ### Browser (if applicable) Chrome ### 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 regenerating a response in a new chat, the title should be automatically generated based on the conversation content after the regenerated response is completed. Specifically: 1. User starts a new chat (shows "새 채팅") 2. User sends a message and gets a response 3. User regenerates the response using "Regenerate Response" 5. After the regenerated response completes, the chat title should automatically change from "새 채팅" to a meaningful title reflecting the conversation topic (e.g., "Artificial Intelligence Explanation") This should happen automatically since: - **Title Generation** is enabled in Admin panel > Settings > Interface - **Title Auto-Generation** is enabled and working for regular new chats - Title generation prompts are functioning correctly in other scenarios ### Actual Behavior The chat title remains as "새 채팅" (New Chat) even after regenerating responses. Specifically: 1. User starts a new chat (shows "새 채팅") 2. User sends a message and gets a response 3. User regenerates the response using "Regenerate Response" 4. The regenerated response completes successfully 5. The chat title still shows "새 채팅(New Chat)" - no automatic title generation occurs 6. User must manually click the pen icon and edit the title The response regeneration does not trigger the automatic title generation function, despite: - Title generation being enabled in settings - Title auto-generation working correctly for regular new chats - All title generation infrastructure being functional ### Steps to Reproduce Prerequisites: - Admin panel > Settings > Interface > **Title Generation is ENABLED** Reproduction Steps: 1. Open Open WebUI in browser 2. Click "New Chat" to start a new conversation 3. Type any message (e.g., "What is artificial intelligence?") 4. Wait for the AI response to begin generating 5. Click the "stop" button to interrupt the response generation 6. Click "Regenerate Response" button 7. Wait for the new response to complete 8. Observe that the chat title still shows "New Chat(새 채팅)" instead of an auto-generated title Expected: Title should change to something like "Artificial Intelligence Explanation" Actual: Title remains "New Chat(새 채팅)" despite Title Generation being enabled Configuration used: - Default Open WebUI settings - No custom environment variables - Standard Docker setup - **Title Generation** is ENABLED - **Title Auto-Generation** is ENABLED and confirmed working for regular chats ### Logs & Screenshots **“새 채팅” = “New Chat”** <img width="248" height="410" alt="Image" src="https://github.com/user-attachments/assets/21824f73-89fd-4c97-9e77-f2ad432399f3" /> ### Additional Information This issue is particularly concerning because: 1. **Title Generation** is explicitly ENABLED in the admin settings 2. **Title Auto-Generation** is enabled and works correctly for regular new chats 3. Title generation prompts are functioning properly in other scenarios 4. The feature fails ONLY when the stop button is clicked during response generation 5. It is unclear whether this behavior is caused by a bug in the regeneration trigger logic or if it is an intentional design decision (policy) Confirmed working scenarios: - Creating a new chat and sending first message → Title auto-generates correctly - Title generation prompts respond properly when manually triggered - **Title Auto-Generation** setting is functional Broken scenario: - Response regeneration does not trigger title generation despite all settings being enabled This issue is similar to #18717, which reports title auto-generation failures, but since the conditions differ, it should be treated as a separate issue. The problem suggests that: - Title generation infrastructure is working correctly - Response regeneration may not properly trigger the title generation function - There may be a missing event handler for regeneration scenarios Workaround: Users can manually edit the title by clicking the pen icon next to "새 채팅" and entering a custom title. This affects user experience as chat history becomes difficult to manage when all chats are named "새 채팅", especially when the title generation feature is confirmed to be working in other contexts.
GiteaMirror added the bug label 2026-04-25 08:08:16 -05:00
GiteaMirror commented 2026-04-25 08:08:19 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Nov 3, 2025):

Unable to reproduce, @silentoplayz confirmation wanted here.

<!-- gh-comment-id:3481344961 --> @tjbck commented on GitHub (Nov 3, 2025): Unable to reproduce, @silentoplayz confirmation wanted here.
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#34230
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?