github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 10:34:13 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #19908] feat: Supports OpenAI-Response format API and related parameters #73640

New Issue
Closed
opened 2026-05-13 06:03:30 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-13 06:03:30 -05:00
Owner
Copy Link

Originally created by @daxiass on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19908

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Dear Author,

We have now entered the era of reasoning-model AI. However, our OpenWebUI still does not provide proper basic support for OpenAI’s reasoning models: we can’t view the reasoning process or the thinking time, and we also can’t configure verbosity.

At the moment, I’m only able to achieve this by hooking in an external function, which is very inconvenient. Therefore, I kindly request that you add support for OpenAI’s official Responses API.

Desired Solution you'd like

support for OpenAI’s official Responses API.

Alternatives Considered

No response

Additional Context

No response

Originally created by @daxiass on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19908 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Dear Author, We have now entered the era of reasoning-model AI. However, our OpenWebUI still does not provide proper basic support for OpenAI’s reasoning models: we can’t view the reasoning process or the thinking time, and we also can’t configure verbosity. At the moment, I’m only able to achieve this by hooking in an external function, which is very inconvenient. Therefore, I kindly request that you add support for OpenAI’s official Responses API. ### Desired Solution you'd like support for OpenAI’s official Responses API. ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2026-05-13 06:03:32 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Dec 12, 2025):

🔍 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. #15356 feat: Support OpenAI responses API to enable new model compatibility
    by PeterDaveHello • Jun 27, 2025

  2. #11758 feat: Support for OpenAI's new Responses API
    by PierreMesure • Mar 17, 2025

  3. #11893 feat: support openai responses api
    by goguryeo1 • Mar 20, 2025

  4. #12583 feat: Model Content Protocol
    by fishcharlie • Apr 07, 2025

  5. #10312 ApiEndpoint support open ai functions call
    by mingyangzhu • Feb 19, 2025

Show 5 more related issues

  1. #18575 feat: Support for OpenAI gpt-5-pro
    by i-rme • Oct 24, 2025

  2. #13101 feat: Add Support for Adjusting Reasoning Intensity in OpenAI-Compatible Mode
    by L0stInFades • Apr 21, 2025

  3. #9093 feat: support include_reasoning parameter
    by coxde • Jan 29, 2025

  4. #12682 feat: Support ReAct
    by xlxxcc • Apr 10, 2025

  5. #9300 Could OpenAI API Connections has thought process? the same as deepseek R1
    by sixyang • Feb 03, 2025

💡 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:3645572616 --> @owui-terminator[bot] commented on GitHub (Dec 12, 2025): 🔍 **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. [#15356](https://github.com/open-webui/open-webui/issues/15356) **feat: Support OpenAI responses API to enable new model compatibility** *by PeterDaveHello • Jun 27, 2025* 2. [#11758](https://github.com/open-webui/open-webui/issues/11758) **feat: Support for OpenAI's new Responses API** *by PierreMesure • Mar 17, 2025* 3. [#11893](https://github.com/open-webui/open-webui/issues/11893) **feat: support openai responses api** *by goguryeo1 • Mar 20, 2025* 4. [#12583](https://github.com/open-webui/open-webui/issues/12583) **feat: Model Content Protocol** *by fishcharlie • Apr 07, 2025* 5. [#10312](https://github.com/open-webui/open-webui/issues/10312) **ApiEndpoint support open ai functions call** *by mingyangzhu • Feb 19, 2025* <details> <summary>Show 5 more related issues</summary> 6. [#18575](https://github.com/open-webui/open-webui/issues/18575) **feat: Support for OpenAI gpt-5-pro** *by i-rme • Oct 24, 2025* 7. [#13101](https://github.com/open-webui/open-webui/issues/13101) **feat: Add Support for Adjusting Reasoning Intensity in OpenAI-Compatible Mode** *by L0stInFades • Apr 21, 2025* 8. [#9093](https://github.com/open-webui/open-webui/issues/9093) **feat: support `include_reasoning` parameter** *by coxde • Jan 29, 2025* 9. [#12682](https://github.com/open-webui/open-webui/issues/12682) **feat: Support ReAct** *by xlxxcc • Apr 10, 2025* 10. [#9300](https://github.com/open-webui/open-webui/issues/9300) **Could OpenAI API Connections has thought process? the same as deepseek R1** *by sixyang • Feb 03, 2025* </details> --- 💡 **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.
GiteaMirror commented 2026-05-13 06:03:33 -05:00
Author
Owner
Copy Link

@daxiass commented on GitHub (Dec 12, 2025):

🔍 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. #15356 feat: Support OpenAI responses API to enable new model compatibility
    by PeterDaveHello • Jun 27, 2025
  2. #11758 feat: Support for OpenAI's new Responses API
    by PierreMesure • Mar 17, 2025
  3. #11893 feat: support openai responses api
    by goguryeo1 • Mar 20, 2025
  4. #12583 feat: Model Content Protocol
    by fishcharlie • Apr 07, 2025
  5. #10312 ApiEndpoint support open ai functions call
    by mingyangzhu • Feb 19, 2025

Show 5 more related issues
6. #18575 feat: Support for OpenAI gpt-5-pro
by i-rme • Oct 24, 2025
7. #13101 feat: Add Support for Adjusting Reasoning Intensity in OpenAI-Compatible Mode
by L0stInFades • Apr 21, 2025
8. #9093 feat: support include_reasoning parameter
by coxde • Jan 29, 2025
9. #12682 feat: Support ReAct
by xlxxcc • Apr 10, 2025
10. #9300 Could OpenAI API Connections has thought process? the same as deepseek R1
by sixyang • Feb 03, 2025

💡 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 think the sheer number of voices calling for this further confirms the urgency of this need—and I'm not the only one who feels this way.

<!-- gh-comment-id:3645587156 --> @daxiass commented on GitHub (Dec 12, 2025): > 🔍 **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. [#15356](https://github.com/open-webui/open-webui/issues/15356) **feat: Support OpenAI responses API to enable new model compatibility** > _by PeterDaveHello • Jun 27, 2025_ > 2. [#11758](https://github.com/open-webui/open-webui/issues/11758) **feat: Support for OpenAI's new Responses API** > _by PierreMesure • Mar 17, 2025_ > 3. [#11893](https://github.com/open-webui/open-webui/issues/11893) **feat: support openai responses api** > _by goguryeo1 • Mar 20, 2025_ > 4. [#12583](https://github.com/open-webui/open-webui/issues/12583) **feat: Model Content Protocol** > _by fishcharlie • Apr 07, 2025_ > 5. [#10312](https://github.com/open-webui/open-webui/issues/10312) **ApiEndpoint support open ai functions call** > _by mingyangzhu • Feb 19, 2025_ > > Show 5 more related issues > 6. [#18575](https://github.com/open-webui/open-webui/issues/18575) **feat: Support for OpenAI gpt-5-pro** > _by i-rme • Oct 24, 2025_ > 7. [#13101](https://github.com/open-webui/open-webui/issues/13101) **feat: Add Support for Adjusting Reasoning Intensity in OpenAI-Compatible Mode** > _by L0stInFades • Apr 21, 2025_ > 8. [#9093](https://github.com/open-webui/open-webui/issues/9093) **feat: support `include_reasoning` parameter** > _by coxde • Jan 29, 2025_ > 9. [#12682](https://github.com/open-webui/open-webui/issues/12682) **feat: Support ReAct** > _by xlxxcc • Apr 10, 2025_ > 10. [#9300](https://github.com/open-webui/open-webui/issues/9300) **Could OpenAI API Connections has thought process? the same as deepseek R1** > _by sixyang • Feb 03, 2025_ > > 💡 **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 think the sheer number of voices calling for this further confirms the urgency of this need—and I'm not the only one who feels this way.
GiteaMirror commented 2026-05-13 06:03:34 -05:00
Author
Owner
Copy Link

@Mcayear commented on GitHub (Dec 12, 2025):

OpenWebUI has deviated from its original commitment to "comply with the OpenAI API."

<!-- gh-comment-id:3645936033 --> @Mcayear commented on GitHub (Dec 12, 2025): OpenWebUI has deviated from its original commitment to "comply with the OpenAI API."
GiteaMirror commented 2026-05-13 06:03:36 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 12, 2025):

@Mcayear @daxiass

Incorrect. Tim has said that Open WebUI will only support OpenAI Chat Completions API - aka the original OpenAI API that is also widely adopted where multiple providers (such as Google, Openrouter and even Anthropic) offer official production or at least Beta endpoints that are OpenAI completions API compatible.

The Responses API is a new API, that basically no provider supports except OpenAI themselves and much of the functionality is not even replicable the same way OpenAI provides it - i.e. server sided chat management, web search, the built-in function calling with server sided functions and more - all the extra quirks that the Responses API support are, in the way they are supported, exclusive to OpenAI's offering - thus making the Responses API something not every provider can just support as a universal standard like the chat completions API.

This was addressed MULTIPLE times in DOZENS of issues and discussions.
I urge you both to search for those before opening yet another issue.

As you can see there are many existing issues, the bot found them, and Tim clarified multiple times what I am just repeating here.
Asking for Responses API support is like asking for Anthropic API or Gemini API support. These are (semi) proprietary APIs that are exclusive to that provider, wheras the OpenAI completions API is the de-facto universal standard.

<!-- gh-comment-id:3646230476 --> @Classic298 commented on GitHub (Dec 12, 2025): @Mcayear @daxiass Incorrect. Tim has said that Open WebUI will only support OpenAI Chat Completions API - aka the original OpenAI API that is also widely adopted where multiple providers (such as Google, Openrouter and even Anthropic) offer official production or at least Beta endpoints that are OpenAI completions API compatible. The Responses API is a new API, that basically no provider supports except OpenAI themselves and much of the functionality is not even replicable the same way OpenAI provides it - i.e. server sided chat management, web search, the built-in function calling with server sided functions and more - all the extra quirks that the Responses API support are, in the way they are supported, exclusive to OpenAI's offering - thus making the Responses API something not every provider can just support as a universal standard like the chat completions API. This was addressed MULTIPLE times in DOZENS of issues and discussions. I urge you both to search for those before opening yet another issue. As you can see there are many existing issues, the bot found them, and Tim clarified multiple times what I am just repeating here. Asking for Responses API support is like asking for Anthropic API or Gemini API support. These are (semi) proprietary APIs that are exclusive to that provider, wheras the OpenAI completions API is the de-facto universal standard.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#73640
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?