A prompt from previous chat is cached and displayed in the UI
Logs & Screenshots
Additional Information
No response
Originally created by @akras14 on GitHub (May 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13753
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
v0.6.8
### Ollama Version (if applicable)
_No response_
### Operating System
macOS
### Browser (if applicable)
Chrome
### 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
1. Refresh the URL, i.e. http://localhost:8080/?temporary-chat=true
2. Expect to see clear prompt to start a new chat
### Actual Behavior
1. Refresh the URL, i.e. http://localhost:8080/?temporary-chat=true
2. A prompt from previous chat is cached and displayed in the UI
### Steps to Reproduce
1. Refresh the URL, i.e. http://localhost:8080/?temporary-chat=true
2. A prompt from previous chat is cached and displayed in the UI
### Logs & Screenshots

### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-13 03:35:48 -05:00
If understand the code change correctly, the attempted fix prevents the input field to be prefilled in a temporary chat session. This is, however, not the issue.
The data is still written to local storage in a temporary chat here unconditionally. The read happens in a non-temporary chat and restores the previously written "temporary" value from local storage.
Edit: I just noticed that the bug describes the a temporary chat only scenario. I can open a new issue for this, if needed.
<!-- gh-comment-id:2930266997 -->
@kautsig commented on GitHub (Jun 2, 2025):
@tjbck I fear [ba69c](https://github.com/open-webui/open-webui/commit/ba69c751ca0ec489604bedfa4041fc71a49e304c) does not address the issue.
I can still reproduce it in `v0.6.13`.
If understand the code change correctly, the attempted fix prevents the input field to be prefilled in a temporary chat session. ~This is, however, not the issue.~
The data is still *written* to local storage in a temporary chat [here](https://github.com/open-webui/open-webui/blob/main/src/lib/components/chat/Chat.svelte#L2095) unconditionally. The read happens in a non-temporary chat and restores the previously written "temporary" value from local storage.
Edit: I just noticed that the bug describes the a temporary chat only scenario. I can open a new issue for this, if needed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @akras14 on GitHub (May 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13753
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.6.8
Ollama Version (if applicable)
No response
Operating System
macOS
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
Actual Behavior
Steps to Reproduce
Logs & Screenshots
Additional Information
No response
@tjbck commented on GitHub (May 10, 2025):
Addressed with
ba69c751cain dev@kautsig commented on GitHub (Jun 2, 2025):
@tjbck I fear ba69c does not address the issue.
I can still reproduce it in
v0.6.13.If understand the code change correctly, the attempted fix prevents the input field to be prefilled in a temporary chat session.
This is, however, not the issue.The data is still written to local storage in a temporary chat here unconditionally. The read happens in a non-temporary chat and restores the previously written "temporary" value from local storage.
Edit: I just noticed that the bug describes the a temporary chat only scenario. I can open a new issue for this, if needed.