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

[GH-ISSUE #16095] feat: Add Toggle for “Reasoning” Parameter When Using OpenRouter in OpenWebUI #33311

New Issue
Closed
opened 2026-04-25 07:13:33 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 07:13:33 -05:00
Owner
Copy Link

Originally created by @PierrunoYT on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16095

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Currently, when using OpenRouter with OpenWebUI, setting the reasoning parameter must be done manually in custom parameters or configuration files. This process is not user-friendly, especially for users who need to frequently enable or disable reasoning for different tasks or experiments. There is no simple UI toggle, and manual editing increases the risk of error and disrupts workflow.

Desired Solution you'd like

Please add a toggle (checkbox or switch) to the OpenWebUI interface for models that support the reasoning parameter (such as OpenRouter).

The toggle should enable or disable inclusion of the reasoning parameter in API requests.

Ideally, the toggle should allow for selecting true/false or omitting the parameter entirely.

Optionally, allow toggling per message/conversation as well as globally per model/provider.

This will allow users to quickly switch reasoning on or off as needed, without editing configuration files or JSON by hand.

Alternatives Considered

Alternatives Considered

Manually editing the custom parameters section to add or remove the "reasoning" parameter as needed.

Creating separate model/provider configurations or presets, which is cumbersome and not ideal for frequent switching.

Additional Context

Some OpenRouter models use the reasoning parameter to control output quality and resource usage. Having an in-UI toggle would streamline user experience, especially for those experimenting with reasoning-enabled models.
OpenWebUI is very user-friendly, and adding this option would make it even more accessible for advanced users and beginners alike.

Thank you for all your hard work on this project!

Originally created by @PierrunoYT on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16095 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Currently, when using OpenRouter with OpenWebUI, setting the reasoning parameter must be done manually in custom parameters or configuration files. This process is not user-friendly, especially for users who need to frequently enable or disable reasoning for different tasks or experiments. There is no simple UI toggle, and manual editing increases the risk of error and disrupts workflow. ### Desired Solution you'd like Please add a toggle (checkbox or switch) to the OpenWebUI interface for models that support the reasoning parameter (such as OpenRouter). The toggle should enable or disable inclusion of the reasoning parameter in API requests. Ideally, the toggle should allow for selecting true/false or omitting the parameter entirely. Optionally, allow toggling per message/conversation as well as globally per model/provider. This will allow users to quickly switch reasoning on or off as needed, without editing configuration files or JSON by hand. ### Alternatives Considered Alternatives Considered Manually editing the custom parameters section to add or remove the "reasoning" parameter as needed. Creating separate model/provider configurations or presets, which is cumbersome and not ideal for frequent switching. ### Additional Context Some OpenRouter models use the reasoning parameter to control output quality and resource usage. Having an in-UI toggle would streamline user experience, especially for those experimenting with reasoning-enabled models. OpenWebUI is very user-friendly, and adding this option would make it even more accessible for advanced users and beginners alike. Thank you for all your hard work on this project!
GiteaMirror commented 2026-04-25 07:13:34 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Jul 28, 2025):

You can use Filters for this

<!-- gh-comment-id:3127977715 --> @Classic298 commented on GitHub (Jul 28, 2025): You can use [Filters](https://docs.openwebui.com/features/plugin/functions/filter) for this
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#33311
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?