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
Git Clone
Open WebUI Version
7.2
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22
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
I deployed OpenAI Codex and exposed it through a Web UI, where it is accessible and works correctly from the platform interface.
I am now trying to connect to the same Codex deployment from VS Code, using my API key via either the Codex VS Code extension or Continue.
It's working on CLI codex but cannot edit files ( when asked to edit or read files it doesn't answer and bugs )
Codex should respond normally in the VS Code extension,
And should bé able to call edit files tools on the Codex CLI (terminal)
Actual Behavior
Codex works correctly in the Codex CLI but cannot call tools of edit files or create /.delete files or even read files
In the VS Code extension, the request sometimes enters a “thinking” state but never returns a response, even after the thinking phase completes
Steps to Reproduce
The configuration in .config.toml of codex for instance :
model = "all model name"
model_provider = "customgpt"
[model_providors.customgpt]
name = "codex private"
base_url = "https://customgpt.company.com/api/v1"
env_key = "CUSTOMGPT_API_KEY"
And we added the key to env variables
Logs & Screenshots
The CUSTOMGPT_API_KEY environment variable is correctly set and available in the terminal
Since the CLI works with the same key and endpoint, this does not appear to be an API key or authentication issue
The problem seems specific to the response of the api call
Additional Information
No response
Originally created by @zechchair on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21147
### 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
Git Clone
### Open WebUI Version
7.2
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 22
### 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
I deployed OpenAI Codex and exposed it through a Web UI, where it is accessible and works correctly from the platform interface.
I am now trying to connect to the same Codex deployment from VS Code, using my API key via either the Codex VS Code extension or Continue.
It's working on CLI codex but cannot edit files ( when asked to edit or read files it doesn't answer and bugs )
Codex should respond normally in the VS Code extension,
And should bé able to call edit files tools on the Codex CLI (terminal)
### Actual Behavior
Codex works correctly in the Codex CLI but cannot call tools of edit files or create /.delete files or even read files
In the VS Code extension, the request sometimes enters a “thinking” state but never returns a response, even after the thinking phase completes
### Steps to Reproduce
The configuration in .config.toml of codex for instance :
```
model = "all model name"
model_provider = "customgpt"
[model_providors.customgpt]
name = "codex private"
base_url = "https://customgpt.company.com/api/v1"
env_key = "CUSTOMGPT_API_KEY"
```
And we added the key to env variables
### Logs & Screenshots
The CUSTOMGPT_API_KEY environment variable is correctly set and available in the terminal
Since the CLI works with the same key and endpoint, this does not appear to be an API key or authentication issue
The problem seems specific to the response of the api call
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-25 09:06:00 -05:00
@owui-terminator[bot] commented on GitHub (Feb 4, 2026):
🔍Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#21091issue: code execution is not working due to ansi colors by mchehab • Feb 01, 2026 • bug
#21034issue: arena doesnt work properly by thekinez • Jan 29, 2026 • bug
#20801issue: HTML Preview renders code blocks inside thinking blocks by IDEDARY • Jan 19, 2026 • bug
💡Tips:
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3846054537 -->
@owui-terminator[bot] commented on GitHub (Feb 4, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#21091](https://github.com/open-webui/open-webui/issues/21091) **issue: code execution is not working due to ansi colors**
*by mchehab • Feb 01, 2026 • `bug`*
2. [#21034](https://github.com/open-webui/open-webui/issues/21034) **issue: arena doesnt work properly**
*by thekinez • Jan 29, 2026 • `bug`*
3. [#20801](https://github.com/open-webui/open-webui/issues/20801) **issue: HTML Preview renders code blocks inside thinking blocks**
*by IDEDARY • Jan 19, 2026 • `bug`*
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
I have the same problem. I want to use the API with tools. "codex - continue ***"
Unfortunately, the API currently does not work correctly with the new models.
<!-- gh-comment-id:3846104725 -->
@zic04 commented on GitHub (Feb 4, 2026):
I have the same problem. I want to use the API with tools. "codex - continue ***"
Unfortunately, the API currently does not work correctly with the new models.
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 @zechchair on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21147
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
7.2
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
I deployed OpenAI Codex and exposed it through a Web UI, where it is accessible and works correctly from the platform interface.
I am now trying to connect to the same Codex deployment from VS Code, using my API key via either the Codex VS Code extension or Continue.
It's working on CLI codex but cannot edit files ( when asked to edit or read files it doesn't answer and bugs )
Codex should respond normally in the VS Code extension,
And should bé able to call edit files tools on the Codex CLI (terminal)
Actual Behavior
Codex works correctly in the Codex CLI but cannot call tools of edit files or create /.delete files or even read files
In the VS Code extension, the request sometimes enters a “thinking” state but never returns a response, even after the thinking phase completes
Steps to Reproduce
The configuration in .config.toml of codex for instance :
And we added the key to env variables
Logs & Screenshots
The CUSTOMGPT_API_KEY environment variable is correctly set and available in the terminal
Since the CLI works with the same key and endpoint, this does not appear to be an API key or authentication issue
The problem seems specific to the response of the api call
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Feb 4, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#21091 issue: code execution is not working due to ansi colors
by mchehab • Feb 01, 2026 •
bug#21034 issue: arena doesnt work properly
by thekinez • Jan 29, 2026 •
bug#20801 issue: HTML Preview renders code blocks inside thinking blocks
by IDEDARY • Jan 19, 2026 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@Classic298 commented on GitHub (Feb 4, 2026):
??? What does this have anything to do with Open WebUI
@zic04 commented on GitHub (Feb 4, 2026):
I have the same problem. I want to use the API with tools. "codex - continue ***"
Unfortunately, the API currently does not work correctly with the new models.