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

[GH-ISSUE #24310] issue: Chat-specific model/system prompt/settings are not persisted after switching chats in v0.9.2 #58925

New Issue
Closed
opened 2026-05-06 00:28:52 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-06 00:28:52 -05:00
Owner
Copy Link

Originally created by @Bennowan on GitHub (May 2, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24310

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

v0.9.2

Ollama Version (if applicable)

v0.22.1

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Chrome v147.0.7727.138

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

Chat-specific settings should persist after being changed, including:

  • Selected model
  • System prompt
  • Other per-chat settings / parameters

After switching to another chat and returning, the modified settings should remain saved.

Actual Behavior

Changed chat-specific settings are only applied temporarily in the UI.

After switching to another chat and returning:

  • Selected model resets
  • System prompt resets
  • Other chat-specific settings reset
    Backend logs indicate no persistence request is emitted when changing these settings.

Steps to Reproduce

  1. Start Open WebUI v0.9.2 via Docker Compose.
  2. Open any existing chat.
  3. Change one or more of the following:
    - Selected model
    - System prompt
    - Other chat-specific settings
  4. Observe that the UI reflects the change temporarily.
  5. Switch to another chat.
  6. Return to the original chat.
  7. Observe that all modified settings have reset.

Logs & Screenshots

Backend Log Observation

While changing chat settings:

No PATCH / PUT / POST request is emitted for chat persistence/update.

Only standard GET/other unrelated requests appear, such as:

  • auth/settings
  • active chats
  • timezone update
  • tasks

This suggests the frontend is not sending persistence requests at all when chat settings are modified.

Additional Information

Relevant possibly-related existing issues:

  • #24270 – Fresh install does not save System Prompts on chats
  • #24193 – System Prompt missing after reload

However, in this case the issue appears broader than system prompts:

It affects general chat-specific settings persistence, including:

  • Model selection
  • System prompts

docker-compose.yml

  • Other per-chat settings

Technical Assessment

Likely frontend regression in v0.9.2.

Evidence suggests:

  • Backend persistence endpoint is never called
  • Save/autosave handler may be broken or not triggered
  • Possible frontend state management regression
Originally created by @Bennowan on GitHub (May 2, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24310 ### 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 v0.9.2 ### Ollama Version (if applicable) v0.22.1 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Chrome v147.0.7727.138 ### 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 Chat-specific settings should persist after being changed, including: - Selected model - System prompt - Other per-chat settings / parameters After switching to another chat and returning, the modified settings should remain saved. ### Actual Behavior Changed chat-specific settings are only applied temporarily in the UI. After switching to another chat and returning: - Selected model resets - System prompt resets - Other chat-specific settings reset Backend logs indicate no persistence request is emitted when changing these settings. ### Steps to Reproduce 1. Start Open WebUI v0.9.2 via Docker Compose. 2. Open any existing chat. 3. Change one or more of the following: - Selected model - System prompt - Other chat-specific settings 4. Observe that the UI reflects the change temporarily. 5. Switch to another chat. 6. Return to the original chat. 7. Observe that all modified settings have reset. ### Logs & Screenshots Backend Log Observation While changing chat settings: No PATCH / PUT / POST request is emitted for chat persistence/update. Only standard GET/other unrelated requests appear, such as: - auth/settings - active chats - timezone update - tasks This suggests the frontend is not sending persistence requests at all when chat settings are modified. ### Additional Information **Relevant possibly-related existing issues:** - #24270 – Fresh install does not save System Prompts on chats - #24193 – System Prompt missing after reload However, in this case the issue appears broader than system prompts: It affects **general chat-specific settings persistence**, including: - Model selection - System prompts [docker-compose.yml](https://github.com/user-attachments/files/27299107/docker-compose.yml) - Other per-chat settings **Technical Assessment** Likely frontend regression in v0.9.2. Evidence suggests: - Backend persistence endpoint is never called - Save/autosave handler may be broken or not triggered - Possible frontend state management regression
GiteaMirror added the bug label 2026-05-06 00:28:52 -05:00
GiteaMirror commented 2026-05-06 00:28:55 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (May 4, 2026):

likely fixed by

86df8bf27e

testing wanted

<!-- gh-comment-id:4373659179 --> @Classic298 commented on GitHub (May 4, 2026): likely fixed by https://github.com/open-webui/open-webui/commit/86df8bf27e1b84abbe2eeedcc8650df59c7d23d6 testing wanted
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#58925
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?