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 #23183] issue: New chat inherits model from previous conversation instead of using default model on first switch #58579

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

Originally created by @ShirasawaSama on GitHub (Mar 28, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23183

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.12

Ollama Version (if applicable)

No response

Operating System

Mac

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

Action Selected Model Correct?
1st "New Chat" from historical conversation Model B (default) ✅
2nd "New Chat" Model B (default) ✅

Clicking "New Chat" from any context — including from a historical conversation — should always use the configured default model.

Actual Behavior

Action Selected Model Correct?
1st "New Chat" from historical conversation Model A (inherited from historical conversation) ❌
2nd "New Chat" Model B (default) ✅

Steps to Reproduce

  1. Set Model B as the default model.
  2. Open a historical conversation from the sidebar where the last message was generated using Model A.
  3. Click "New Chat" from that conversation.
  4. Observe the selected model in the new chat.
  5. Click "New Chat" again.
  6. Observe the selected model.

Logs & Screenshots

N/A

Additional Information

No response

Originally created by @ShirasawaSama on GitHub (Mar 28, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23183 ### 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.12 ### Ollama Version (if applicable) _No response_ ### Operating System Mac ### 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 | Action | Selected Model | Correct? | |---|---|---| | 1st "New Chat" from historical conversation | Model B (default) | ✅ | | 2nd "New Chat" | Model B (default) | ✅ | Clicking "New Chat" from any context — including from a historical conversation — should always use the configured default model. ### Actual Behavior | Action | Selected Model | Correct? | |---|---|---| | 1st "New Chat" from historical conversation | Model A (inherited from historical conversation) | ❌ | | 2nd "New Chat" | Model B (default) | ✅ | ### Steps to Reproduce 1. Set **Model B** as the default model. 2. Open a **historical conversation** from the sidebar where the last message was generated using **Model A**. 3. Click **"New Chat"** from that conversation. 4. Observe the selected model in the new chat. 5. Click **"New Chat"** again. 6. Observe the selected model. ### Logs & Screenshots N/A ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-05 23:28:45 -05:00
GiteaMirror commented 2026-05-05 23:28:47 -05:00
Author
Owner
Copy Link

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

this was raised a few days ago and closed as intended. so i think this will be closed too

<!-- gh-comment-id:4148434278 --> @Classic298 commented on GitHub (Mar 28, 2026): this was raised a few days ago and closed as intended. so i think this will be closed too
GiteaMirror commented 2026-05-05 23:28:48 -05:00
Author
Owner
Copy Link

@ShirasawaSama commented on GitHub (Mar 28, 2026):

this was raised a few days ago and closed as intended. so i think this will be closed too

In that case, I’ll close this issue, but personally, it really does seem like a bug to me.

<!-- gh-comment-id:4148444783 --> @ShirasawaSama commented on GitHub (Mar 28, 2026): > this was raised a few days ago and closed as intended. so i think this will be closed too In that case, I’ll close this issue, but personally, it really does seem like a bug to me.
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#58579
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?