github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

feat: support for passing non-standard sampling parameters (e.g. top_k) in OpenAI-like APIs #2092

New Issue
Closed
opened 2025-11-11 15:00:10 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 15:00:10 -06:00
Owner
Copy Link

Originally created by @esceptico on GitHub (Sep 16, 2024).

Is your feature request related to a problem? Please describe.
I’m currently using a custom OpenAI-like API along with open-webui. Everything works great, but there’s a limitation in the current support for the OpenAI-like API. Specifically, there’s no ability to pass non-standard sampling parameters (those not typically supported by the OpenAI interface) such as top_k. As I understand, this limitation is intentional.

Describe the solution you'd like
I would like to have the option to pass all sampling parameters (including non-standard ones) through the OpenAI-like API, similar to how they’re available in the UI. This would allow greater flexibility when interacting with custom APIs.

Describe alternatives you've considered
Currently, the only alternative is to use the parameters that are supported by the standard OpenAI API interface and hardcode the rest. However, this limits functionality for testing purposes :(

Additional context
None

Originally created by @esceptico on GitHub (Sep 16, 2024). **Is your feature request related to a problem? Please describe.** I’m currently using a custom OpenAI-like API along with open-webui. Everything works great, but there’s a limitation in the current support for the OpenAI-like API. Specifically, there’s no ability to pass non-standard sampling parameters (those not typically supported by the OpenAI interface) such as top_k. As I understand, this limitation is intentional. **Describe the solution you'd like** I would like to have the option to pass all sampling parameters (including non-standard ones) through the OpenAI-like API, similar to how they’re available in the UI. This would allow greater flexibility when interacting with custom APIs. **Describe alternatives you've considered** Currently, the only alternative is to use the parameters that are supported by the standard OpenAI API interface and hardcode the rest. However, this limits functionality for testing purposes :( **Additional context** None
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#2092
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?