github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-11 00:04:08 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: Models not aware of any recent history (no context length) #4975

New Issue
Closed
opened 2025-11-11 16:08:35 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-11 16:08:35 -06:00
Owner
Copy Link

Originally created by @scscgit on GitHub (Apr 27, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.5

Ollama Version (if applicable)

0.6.7-rc0

Operating System

Windows 10

Browser (if applicable)

Firefox 137.0.1

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 listed steps to reproduce the bug in detail.

Expected Behavior

Models should remember the recent chat history from subsequent messages by default.

Actual Behavior

Models treat every message as if it were the first message. The UI doesn't provide any help.

Steps to Reproduce

I just upgraded open-webui Docker image to v0.6.5 from sha256:99102007e4959ea336faa9283a43a59b9ed9fb464580c7a7d7de8e4a18bf4170 (your download instructions make it difficult to tag the image). I kept the same volume, auto-upgrading the old database. I also upgraded Ollama Docker image to 0.6.7-rc0 from sha256:034f55fbbaedac6eaf82b55d3b8fdb1016edd206d43e72676fbddae8ec022b71. After experiencing a Vmmem RAM leak, I restarted the Docker. Then I went to test the chat. What I found out is that it's no longer possible for models to remember any history. I tested this on both old models that previously worked, and newly downloaded ones.

For example:
Q: do you understand an apple?
AI llama3.1:8b: ... (answer omitted)
Q: what color is it?
AI llama3.1:8b: This conversation has just started. I'm not aware of what "it" refers to. Could you please provide more context or clarify what you're asking about? I'll do my best to help!

Logs & Screenshots

My settings were kept as defaults:

Image

Here is the message detail:

Image

Browser Logs
open-webui Docker Log
ollama Docker Log

Additional Information

Please, also generally fix the UX of the context length, why is it not your top priority? :(

Originally created by @scscgit on GitHub (Apr 27, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.5 ### Ollama Version (if applicable) 0.6.7-rc0 ### Operating System Windows 10 ### Browser (if applicable) Firefox 137.0.1 ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior Models should remember the recent chat history from subsequent messages by default. ### Actual Behavior Models treat every message as if it were the first message. The UI doesn't provide any help. ### Steps to Reproduce I just upgraded open-webui Docker image to v0.6.5 from sha256:99102007e4959ea336faa9283a43a59b9ed9fb464580c7a7d7de8e4a18bf4170 (your download instructions make it difficult to tag the image). I kept the same volume, auto-upgrading the old database. I also upgraded Ollama Docker image to 0.6.7-rc0 from sha256:034f55fbbaedac6eaf82b55d3b8fdb1016edd206d43e72676fbddae8ec022b71. After experiencing a Vmmem RAM leak, I restarted the Docker. Then I went to test the chat. What I found out is that it's no longer possible for models to remember any history. I tested this on both old models that previously worked, and newly downloaded ones. For example: Q: do you understand an apple? AI llama3.1:8b: ... (answer omitted) Q: what color is it? AI llama3.1:8b: This conversation has just started. I'm not aware of what "it" refers to. Could you please provide more context or clarify what you're asking about? I'll do my best to help! ### Logs & Screenshots My settings were kept as defaults: ![Image](https://github.com/user-attachments/assets/acaa0d02-2d6a-4636-8065-5b345f1149e8) Here is the message detail: ![Image](https://github.com/user-attachments/assets/b5b043bd-ba20-4a1e-995e-7122ae59fd33) [Browser Logs](https://github.com/user-attachments/files/19931548/-browserlogs.txt) [open-webui Docker Log](https://github.com/user-attachments/files/19931551/-dockerlog.txt) [ollama Docker Log](https://github.com/user-attachments/files/19931555/-ollama-dockerlog.txt) ### Additional Information Please, also generally fix the UX of the context length, why is it not your top priority? :( * #573
GiteaMirror added the bug label 2025-11-11 16:08:35 -06:00
GiteaMirror commented 2025-11-11 16:08:37 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 28, 2025):

PLEASE check for existing discussions and issues, and at the very least read our documentation. This is caused by Ollama and not Open WebUI.

@tjbck commented on GitHub (Apr 28, 2025): PLEASE check for existing discussions and issues, and at the very least read our documentation. This is caused by Ollama and not Open WebUI.
GiteaMirror commented 2025-11-11 16:08:37 -06:00
Author
Owner
Copy Link

@scscgit commented on GitHub (Apr 28, 2025):

@tjbck I did not find this in any issue or discussion. Actually, even googling for the issue only brings my own issue. I don't know where do you expect me to look in the documentation, I surely can't read all of it (+ I'd suggest considering adding an in-app documentation for UX any time it's relevant), but I went through any Getting Started pages, there was no mention of this bug anywhere. Please, document the maximum supported Ollama version if they have a bug. I guess I should downgrade?

@scscgit commented on GitHub (Apr 28, 2025): @tjbck I did not find this in any issue or discussion. Actually, even googling for the issue only brings my own issue. I don't know where do you expect me to look in the documentation, I surely can't read all of it (+ I'd suggest considering adding an in-app documentation for UX any time it's relevant), but I went through any Getting Started pages, there was no mention of this bug anywhere. Please, document the maximum supported Ollama version if they have a bug. I guess I should downgrade?
GiteaMirror commented 2025-11-11 16:08:37 -06:00
Author
Owner
Copy Link

@scscgit commented on GitHub (Apr 28, 2025):

FYI, Ollama has reproduced this bug on 0.6.7-rc0 and is preparing a fix for the next version. Thanks!

@scscgit commented on GitHub (Apr 28, 2025): FYI, Ollama has reproduced this bug on `0.6.7-rc0` and is preparing a fix for the next version. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
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#4975
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?