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
Docker
Open WebUI Version
v0.9.5
Ollama Version (if applicable)
No response
Operating System
MacOS Tahoe 26.4.1
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
0.9.5 API does not work for OpenAI-compatible endpoints with the pi-mono harness.
Actual Behavior
I'm using a pi-mono harness to access models via Open WebUI API. v0.9.4 works fine, v0.9.5 breaks with
Error: 400 status code (no body)
Context overflow recovery failed: Summarization failed: 400 status code (no body)
Steps to Reproduce
Access from pi-mono harness and Open WebUI API using OpenAI-compatible endpoints.
Logs & Screenshots
v0.9.4
v0.9.5
Additional Information
No response
Originally created by @radekg on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24749
### 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
Docker
### Open WebUI Version
v0.9.5
### Ollama Version (if applicable)
_No response_
### Operating System
MacOS Tahoe 26.4.1
### 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
0.9.5 API does not work for OpenAI-compatible endpoints with the pi-mono harness.
### Actual Behavior
I'm using a pi-mono harness to access models via Open WebUI API. v0.9.4 works fine, v0.9.5 breaks with
> Error: 400 status code (no body)
> Context overflow recovery failed: Summarization failed: 400 status code (no body)
### Steps to Reproduce
Access from pi-mono harness and Open WebUI API using OpenAI-compatible endpoints.
### Logs & Screenshots
v0.9.4
<img width="1870" height="723" alt="Image" src="https://github.com/user-attachments/assets/5eace131-c11f-4909-9ead-0d5ebc6abb00" />
v0.9.5
<img width="1200" height="781" alt="Image" src="https://github.com/user-attachments/assets/213e0a9b-9ee0-46f7-aead-fe31ebfa5fa9" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-21 03:10:00 -05:00
@owui-terminator[bot] commented on GitHub (May 15, 2026):
🔍Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣#24550bug: NoneType object has no attribute 'startswith' — all /api/v1/chat/completions calls return 400 (v0.9.5, direct connections) This is the closest match: it reports the same v0.9.5 regression where external/OpenAI-compatible API clients get HTTP 400 errors, specifically from /api/v1/chat/completions and a 'NoneType' object has no attribute 'startswith' failure. by ThefloorMiner
🟣#24554issue: Open WebUI v0.9.5 Broken Completions API This is the same regression from another client perspective. It explicitly says v0.9.5 breaks the completions API for external clients like OpenCode and Continue, which aligns with the reported API-client breakage here. by xcjs · bug
🟣#4812400 error in UI on context overflow This is related at the symptom level because it also describes a 400 error when context overflow recovery/summarization is triggered. While older and not about API clients specifically, the failure mode in the new issue mentions context overflow recovery and summarization failing with 400. by ddzina
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4458374345 -->
@owui-terminator[bot] commented on GitHub (May 15, 2026):
<!-- terminator-bot:related-issues-reply -->
🔍 **Related Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. 🟣 [#24550](https://github.com/open-webui/open-webui/issues/24550) **bug: NoneType object has no attribute 'startswith' — all /api/v1/chat/completions calls return 400 (v0.9.5, direct connections)**
*This is the closest match: it reports the same v0.9.5 regression where external/OpenAI-compatible API clients get HTTP 400 errors, specifically from `/api/v1/chat/completions` and a `'NoneType' object has no attribute 'startswith'` failure.*
*by ThefloorMiner*
2. 🟣 [#24554](https://github.com/open-webui/open-webui/issues/24554) **issue: Open WebUI v0.9.5 Broken Completions API**
*This is the same regression from another client perspective. It explicitly says v0.9.5 breaks the completions API for external clients like OpenCode and Continue, which aligns with the reported API-client breakage here.*
*by xcjs · `bug`*
3. 🟣 [#4812](https://github.com/open-webui/open-webui/issues/4812) **400 error in UI on context overflow**
*This is related at the symptom level because it also describes a 400 error when context overflow recovery/summarization is triggered. While older and not about API clients specifically, the failure mode in the new issue mentions context overflow recovery and summarization failing with 400.*
*by ddzina*
---
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4458408332 -->
@radekg commented on GitHub (May 15, 2026):
I can now see this is a duplicate of https://github.com/open-webui/open-webui/issues/24550.
<img width="1182" height="103" alt="Image" src="https://github.com/user-attachments/assets/98201f2b-bc33-48a4-bd9d-a75252a6f4e7" />
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 @radekg on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24749
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.9.5
Ollama Version (if applicable)
No response
Operating System
MacOS Tahoe 26.4.1
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
0.9.5 API does not work for OpenAI-compatible endpoints with the pi-mono harness.
Actual Behavior
I'm using a pi-mono harness to access models via Open WebUI API. v0.9.4 works fine, v0.9.5 breaks with
Steps to Reproduce
Access from pi-mono harness and Open WebUI API using OpenAI-compatible endpoints.
Logs & Screenshots
v0.9.4
v0.9.5
Additional Information
No response
@owui-terminator[bot] commented on GitHub (May 15, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #24550 bug: NoneType object has no attribute 'startswith' — all /api/v1/chat/completions calls return 400 (v0.9.5, direct connections)
This is the closest match: it reports the same v0.9.5 regression where external/OpenAI-compatible API clients get HTTP 400 errors, specifically from
/api/v1/chat/completionsand a'NoneType' object has no attribute 'startswith'failure.by ThefloorMiner
🟣 #24554 issue: Open WebUI v0.9.5 Broken Completions API
This is the same regression from another client perspective. It explicitly says v0.9.5 breaks the completions API for external clients like OpenCode and Continue, which aligns with the reported API-client breakage here.
by xcjs ·
bug🟣 #4812 400 error in UI on context overflow
This is related at the symptom level because it also describes a 400 error when context overflow recovery/summarization is triggered. While older and not about API clients specifically, the failure mode in the new issue mentions context overflow recovery and summarization failing with 400.
by ddzina
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@radekg commented on GitHub (May 15, 2026):
I can now see this is a duplicate of https://github.com/open-webui/open-webui/issues/24550.