I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.31
Ollama Version (if applicable)
No response
Operating System
ubuntu 24.04
Browser (if applicable)
chrome 140.0.7339.128
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 AI edits an entire note, it should not cause the page to freeze completely.
Actual Behavior
When using AI to edit an entire note (e.g., translating the entire note), the web page may appear frozen. If you wait patiently for a period of time (the duration of which will depend on the note's content), the editing process will eventually complete. However, perhaps this feature could be presented more effectively? For example, with a progress bar or segmented display during editing?
Steps to Reproduce
Find any non-native language article, copy it into an Open-WebUI note, then use AI editing to translate it.
Logs & Screenshots
This issue is extremely easy to reproduce, hence no screenshots. As for logs, since the software itself does not report errors during translation, there are no logs either.
Additional Information
Strictly speaking, this issue is not a bug but rather a software performance problem. Even if it remains unresolved, it will not affect the use of core functionalities.
Originally created by @pureGavin on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17880
### 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 am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.31
### Ollama Version (if applicable)
_No response_
### Operating System
ubuntu 24.04
### Browser (if applicable)
chrome 140.0.7339.128
### 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 AI edits an entire note, it should not cause the page to freeze completely.
### Actual Behavior
When using AI to edit an entire note (e.g., translating the entire note), the web page may appear frozen. If you wait patiently for a period of time (the duration of which will depend on the note's content), the editing process will eventually complete. However, perhaps this feature could be presented more effectively? For example, with a progress bar or segmented display during editing?
### Steps to Reproduce
Find any non-native language article, copy it into an Open-WebUI note, then use AI editing to translate it.
### Logs & Screenshots
This issue is extremely easy to reproduce, hence no screenshots. As for logs, since the software itself does not report errors during translation, there are no logs either.
### Additional Information
Strictly speaking, this issue is not a bug but rather a software performance problem. Even if it remains unresolved, it will not affect the use of core functionalities.
GiteaMirror
added the bug label 2026-05-15 14:01:58 -05:00
Does closing this issue mean it won't be resolved? Or have you logged it in your internal development schedule?
<!-- gh-comment-id:3484384765 -->
@pureGavin commented on GitHub (Nov 4, 2025):
> Intended UI behaviour , we'll see what we can do.
Does closing this issue mean it won't be resolved? Or have you logged it in your internal development schedule?
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 @pureGavin on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17880
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.31
Ollama Version (if applicable)
No response
Operating System
ubuntu 24.04
Browser (if applicable)
chrome 140.0.7339.128
Confirmation
README.md.Expected Behavior
When AI edits an entire note, it should not cause the page to freeze completely.
Actual Behavior
When using AI to edit an entire note (e.g., translating the entire note), the web page may appear frozen. If you wait patiently for a period of time (the duration of which will depend on the note's content), the editing process will eventually complete. However, perhaps this feature could be presented more effectively? For example, with a progress bar or segmented display during editing?
Steps to Reproduce
Find any non-native language article, copy it into an Open-WebUI note, then use AI editing to translate it.
Logs & Screenshots
This issue is extremely easy to reproduce, hence no screenshots. As for logs, since the software itself does not report errors during translation, there are no logs either.
Additional Information
Strictly speaking, this issue is not a bug but rather a software performance problem. Even if it remains unresolved, it will not affect the use of core functionalities.
@tjbck commented on GitHub (Sep 29, 2025):
Intended UI behaviour , we'll see what we can do.
@pureGavin commented on GitHub (Nov 4, 2025):
Does closing this issue mean it won't be resolved? Or have you logged it in your internal development schedule?