github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 11:28:35 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22957] issue: "New Chat" inherits the current model instead of the configured default model on the first click #35380

New Issue
Closed
opened 2026-04-25 09:35:38 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 09:35:38 -05:00
Owner
Copy Link

Originally created by @hxs-sma on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22957

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

Docker

Open WebUI Version

0.8.10

Ollama Version (if applicable)

No response

Operating System

Amazon Linux 2023

Browser (if applicable)

Microsoft Edge Version 146.0.3856.62 (Official build) (64-bit)

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 clicking "New Chat", the system should always immediately select the configured default model (Admin/User preference), regardless of which model is currently being used in the active chat view.

Actual Behavior

Currently, Open WebUI allows configuring default models for new chats at both the Admin and User levels. However, there is a bug regarding how the model is selected when creating a new chat while currently viewing an active chat that uses a non-default model.

Instead of prioritizing the configured default model, the first click on "New Chat" inherits the model of the currently active chat.

Steps to Reproduce

  1. Configure a default model in either the Admin or User settings (Let's call it Model A).
  2. Start a chat and manually switch the model to a different one (Let's call it Model B).
  3. While inside the active chat using Model B, click the "New Chat" button.
  4. Notice that the new chat is now set to Model B (inherited from the previous chat).
  5. Click "New Chat" a second time.
  6. Notice that it now correctly selects the configured default model (Model A).

Logs & Screenshots

Additional Information

No response

Originally created by @hxs-sma on GitHub (Mar 23, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22957 ### 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 Docker ### Open WebUI Version 0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System Amazon Linux 2023 ### Browser (if applicable) Microsoft Edge Version 146.0.3856.62 (Official build) (64-bit) ### 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 clicking "New Chat", the system should always immediately select the configured default model (Admin/User preference), regardless of which model is currently being used in the active chat view. ### Actual Behavior Currently, Open WebUI allows configuring default models for new chats at both the Admin and User levels. However, there is a bug regarding how the model is selected when creating a new chat while currently viewing an active chat that uses a non-default model. Instead of prioritizing the configured default model, the first click on "New Chat" inherits the model of the currently active chat. ### Steps to Reproduce 1. Configure a default model in either the Admin or User settings (Let's call it Model A). 2. Start a chat and manually switch the model to a different one (Let's call it Model B). 3. While inside the active chat using Model B, click the "New Chat" button. 4. Notice that the new chat is now set to Model B (inherited from the previous chat). 5. Click "New Chat" a second time. 6. Notice that it now correctly selects the configured default model (Model A). ### Logs & Screenshots - ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 09:35:38 -05:00
GiteaMirror commented 2026-04-25 09:35:39 -05:00
Author
Owner
Copy Link

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

I think this is intended but not sure

<!-- gh-comment-id:4110841899 --> @Classic298 commented on GitHub (Mar 23, 2026): I think this is intended but not sure
GiteaMirror commented 2026-04-25 09:35:40 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 24, 2026):

Intended.

<!-- gh-comment-id:4116808073 --> @tjbck commented on GitHub (Mar 24, 2026): Intended.
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#35380
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?