github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #24522] issue: When continuing a conversation in the new version using a chat created in an older version, the system fails to send the full context to the model #107314

New Issue
Closed
opened 2026-05-18 06:04:17 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-05-18 06:04:17 -05:00
Owner
Copy Link

Originally created by @CookSleep on GitHub (May 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24522

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

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.4

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

When opening and continuing a chat history created in an older version using the latest release, the system sends the entire historical context to the model.

Actual Behavior

The system only sends a very limited amount of recent context to the model. The context window varies by conversation; some are restricted to the last three exchanges, while others can only include the single most recent turn.

Steps to Reproduce

After opening the latest version of OpenWebUI and selecting a chat history created in an older version, I tried to continue the conversation by asking the model about very specific and clear details mentioned earlier. The model completely forgot them, indicating that the chat history is not being sent in its entirety.

Logs & Screenshots

I'm very sorry, but I really couldn't find any error logs, and I'm also reluctant to post conversation content here that contains private information.

Additional Information

Maybe it's because the chat log structure was changed? I noticed this mentioned in the release notes.

Originally created by @CookSleep on GitHub (May 9, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24522 ### 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.4 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.4 ### 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 When opening and continuing a chat history created in an older version using the latest release, the system sends the entire historical context to the model. ### Actual Behavior The system only sends a very limited amount of recent context to the model. The context window varies by conversation; some are restricted to the last three exchanges, while others can only include the single most recent turn. ### Steps to Reproduce After opening the latest version of OpenWebUI and selecting a chat history created in an older version, I tried to continue the conversation by asking the model about very specific and clear details mentioned earlier. The model completely forgot them, indicating that the chat history is not being sent in its entirety. ### Logs & Screenshots I'm very sorry, but I really couldn't find any error logs, and I'm also reluctant to post conversation content here that contains private information. ### Additional Information Maybe it's because the chat log structure was changed? I noticed this mentioned in the release notes.
GiteaMirror added the bug label 2026-05-18 06:04:17 -05:00
GiteaMirror commented 2026-05-18 06:04:21 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 9, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

  1. 🟣 #22327 issue: Wrong chat history is sent to inference server
    This bug reports that the wrong chat history is sent to the inference server, which is directly adjacent to the reported problem of incomplete context being sent after resuming a conversation. Both concern context assembly for requests.
    by LostPhysx · bug

  2. 🟢 #19594 feat: Persistent "Invisible" Metadata Object within Chat History for Context Management / OR new DB Table for storing these
    This feature request is about storing persistent hidden metadata inside chat history for context management, which aligns with the user's suspicion that a chat log structure change may have altered how older chats preserve context.
    by Classic298

  3. 🟢 #23781 issue: Recover full conversation history (reasoning + tools inputs/outputs) inside a tool
    This issue is about missing prior tool-call history in later turns, another form of incomplete conversation context being provided to the model. It is related to context preservation, though specifically for tool execution.
    by ccdv-ai · bug

  4. 🟣 #20474 Chat infinitely loads when history.currentId points to orphaned/deleted message
    This closed issue shows that malformed or inconsistent chat history state can break chat loading due to history.currentId/orphaned message problems. It is related insofar as older chats or migrated structures can cause conversation state issues, though it is not specifically about model context.
    by MacJedi42 · bug

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

<!-- gh-comment-id:4413570097 --> @owui-terminator[bot] commented on GitHub (May 9, 2026): <!-- terminator-bot:related-issues-reply --> 🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#22327](https://github.com/open-webui/open-webui/issues/22327) **issue: Wrong chat history is sent to inference server** *This bug reports that the wrong chat history is sent to the inference server, which is directly adjacent to the reported problem of incomplete context being sent after resuming a conversation. Both concern context assembly for requests.* *by LostPhysx · `bug`* 2. 🟢 [#19594](https://github.com/open-webui/open-webui/issues/19594) **feat: Persistent "Invisible" Metadata Object within Chat History for Context Management / OR new DB Table for storing these** *This feature request is about storing persistent hidden metadata inside chat history for context management, which aligns with the user's suspicion that a chat log structure change may have altered how older chats preserve context.* *by Classic298* 3. 🟢 [#23781](https://github.com/open-webui/open-webui/issues/23781) **issue: Recover full conversation history (reasoning + tools inputs/outputs) inside a tool** *This issue is about missing prior tool-call history in later turns, another form of incomplete conversation context being provided to the model. It is related to context preservation, though specifically for tool execution.* *by ccdv-ai · `bug`* 4. 🟣 [#20474](https://github.com/open-webui/open-webui/issues/20474) **Chat infinitely loads when history.currentId points to orphaned/deleted message** *This closed issue shows that malformed or inconsistent chat history state can break chat loading due to history.currentId/orphaned message problems. It is related insofar as older chats or migrated structures can cause conversation state issues, though it is not specifically about model context.* *by MacJedi42 · `bug`* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
GiteaMirror commented 2026-05-18 06:04:22 -05:00
Author
Owner
Copy Link

@CookSleep commented on GitHub (May 9, 2026):

I tested conversations created in the new version and didn't encounter the issues mentioned above. Therefore, I'm inclined to believe that the system might have some compatibility issues when reading conversation content from older versions.

<!-- gh-comment-id:4413575106 --> @CookSleep commented on GitHub (May 9, 2026): I tested conversations created in the new version and didn't encounter the issues mentioned above. Therefore, I'm inclined to believe that the system might have some compatibility issues when reading conversation content from older versions.
GiteaMirror commented 2026-05-18 06:04:22 -05:00
Author
Owner
Copy Link

@CookSleep commented on GitHub (May 9, 2026):

I haven't enabled any functions for managing context.

<!-- gh-comment-id:4413576413 --> @CookSleep commented on GitHub (May 9, 2026): I haven't enabled any functions for managing context.
GiteaMirror commented 2026-05-18 06:04:23 -05:00
Author
Owner
Copy Link

@CookSleep commented on GitHub (May 9, 2026):

You can also tell from the model response logs when continuing a conversation from an older version that the actual number of tokens sent doesn't match the full context of the conversation at all.

<!-- gh-comment-id:4413578546 --> @CookSleep commented on GitHub (May 9, 2026): You can also tell from the model response logs when continuing a conversation from an older version that the actual number of tokens sent doesn't match the full context of the conversation at all.
GiteaMirror commented 2026-05-18 06:04:24 -05:00
Author
Owner
Copy Link

@CookSleep commented on GitHub (May 9, 2026):

I noticed that the old conversation with only one round of context was even more absurd—the very first message the model could see was actually its own last response, rather than my user message!

<!-- gh-comment-id:4413582253 --> @CookSleep commented on GitHub (May 9, 2026): I noticed that the old conversation with only one round of context was even more absurd—the very first message the model could see was actually its own last response, rather than my user message!
GiteaMirror commented 2026-05-18 06:04:25 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 10, 2026):

@CookSleep could you test the latest dev? it might already be addressed.

<!-- gh-comment-id:4415820434 --> @tjbck commented on GitHub (May 10, 2026): @CookSleep could you test the latest dev? it might already be addressed.
GiteaMirror commented 2026-05-18 06:04:26 -05:00
Author
Owner
Copy Link

@2259819800 commented on GitHub (May 10, 2026):

I also encountered the same problem

<!-- gh-comment-id:4415838019 --> @2259819800 commented on GitHub (May 10, 2026): I also encountered the same problem
GiteaMirror commented 2026-05-18 06:04:26 -05:00
Author
Owner
Copy Link

@CookSleep commented on GitHub (May 10, 2026):

@CookSleep Could you please test the latest dev version? This issue might have already been resolved.

Thanks a lot! I tried the dev version, and everything is working perfectly now!

<!-- gh-comment-id:4415895370 --> @CookSleep commented on GitHub (May 10, 2026): > [@CookSleep](https://github.com/CookSleep) Could you please test the latest dev version? This issue might have already been resolved. Thanks a lot! I tried the dev version, and everything is working perfectly now!
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#107314
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?