[GH-ISSUE #13753] issue: previous prompt is cached when new chat starts #136745

Closed
opened 2026-05-25 05:20:01 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @akras14 on GitHub (May 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13753

Check Existing Issues

  • I have searched the existing issues and discussions.
  • 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

  • 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

  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

Image

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 ![Image](https://github.com/user-attachments/assets/e850d332-82d3-4046-b8e8-861a0b47160f) ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-25 05:20:01 -05:00
Author
Owner

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

Addressed with ba69c751ca in dev

<!-- gh-comment-id:2869072382 --> @tjbck commented on GitHub (May 10, 2025): Addressed with ba69c751ca0ec489604bedfa4041fc71a49e304c in dev
Author
Owner

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

<!-- 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#136745