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
Pip Install
Open WebUI Version
v0.8.8
Ollama Version (if applicable)
No response
Operating System
windows 10
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
After running cwd at any directory, from the navigation bar we should be able to jump back to the path displayed above.
Actual Behavior
After choosing the directory and click into the path, the navigation bar above doesn't display separated path to the file/directory like D:\Desktop\mydirectory in one block, and by clicking the path, the openwebui returned Failed to load directory. Check your Terminal connection in Settings → Integrations. I've analyzed the reason and it's showed below.
Steps to Reproduce
Set up Open WebUI on a Windows server.
Open a web browser (tested on Windows, Mac, and Linux browsers) and access the Open WebUI interface.
Open the Open-terminal feature in the UI.
Navigate into a directory (e.g., D:\Desktop\mydir\).
Click the "go back to parent directory" button to return to the previous level.
Observe the error message: "Failed to load directory. Check your Terminal connection in Settings → Integrations."
Logs & Screenshots
Network Request Analysis:
Initial directory request payload (correct):
{"path":"D:\\Desktop\\mydir/"}
Request after navigating back to parent directory (incorrect):
{"path":"/D:\\Desktop\\genesis/"}
Additional Information
When returning to the parent directory, the UI incorrectly adds a leading slash to the path, changing D:\Desktop to /D:\Desktop, causing the backend to fail to parse the path correctly.
Originally created by @ppoak on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22352
### 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
Pip Install
### Open WebUI Version
v0.8.8
### Ollama Version (if applicable)
_No response_
### Operating System
windows 10
### 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
After running cwd at any directory, from the navigation bar we should be able to jump back to the path displayed above.
### Actual Behavior
After choosing the directory and click into the path, the navigation bar above doesn't display separated path to the file/directory like `D:\Desktop\mydirectory` in one block, and by clicking the path, the openwebui returned `Failed to load directory. Check your Terminal connection in Settings → Integrations.` I've analyzed the reason and it's showed below.
### Steps to Reproduce
1. Set up Open WebUI on a Windows server.
2. Open a web browser (tested on Windows, Mac, and Linux browsers) and access the Open WebUI interface.
3. Open the Open-terminal feature in the UI.
4. Navigate into a directory (e.g., `D:\Desktop\mydir\`).
5. Click the "go back to parent directory" button to return to the previous level.
6. Observe the error message: "Failed to load directory. Check your Terminal connection in Settings → Integrations."
### Logs & Screenshots
**Network Request Analysis:**
- Initial directory request payload (correct):
```json
{"path":"D:\\Desktop\\mydir/"}
```
- Request after navigating back to parent directory (incorrect):
```json
{"path":"/D:\\Desktop\\genesis/"}
```
### Additional Information
When returning to the parent directory, the UI incorrectly adds a leading slash to the path, changing `D:\Desktop` to `/D:\Desktop`, causing the backend to fail to parse the path correctly.
GiteaMirror
added the bug label 2026-04-20 02:13:36 -05:00
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 @ppoak on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22352
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.8.8
Ollama Version (if applicable)
No response
Operating System
windows 10
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
After running cwd at any directory, from the navigation bar we should be able to jump back to the path displayed above.
Actual Behavior
After choosing the directory and click into the path, the navigation bar above doesn't display separated path to the file/directory like
D:\Desktop\mydirectoryin one block, and by clicking the path, the openwebui returnedFailed to load directory. Check your Terminal connection in Settings → Integrations.I've analyzed the reason and it's showed below.Steps to Reproduce
D:\Desktop\mydir\).Logs & Screenshots
Network Request Analysis:
Initial directory request payload (correct):
Request after navigating back to parent directory (incorrect):
Additional Information
When returning to the parent directory, the UI incorrectly adds a leading slash to the path, changing
D:\Desktopto/D:\Desktop, causing the backend to fail to parse the path correctly.@tjbck commented on GitHub (Mar 7, 2026):
Should be addressed in dev!
@Classic298 commented on GitHub (Mar 7, 2026):
https://github.com/open-webui/open-webui/commit/044fd1bd15cae06a5c56a321ca79d8362942f66a