github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-26 19:38:22 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #20658] feat: Global Model Defaults for Admin Configuration (Default Model Settings) #138979

New Issue
Closed
opened 2026-05-25 12:01:02 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-25 12:01:02 -05:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20658

Originally assigned to: @tjbck on GitHub.

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

  • As an administrator managing multiple models across different connections (Ollama, OpenAI, etc.), I currently need to manually configure model capabilities (vision, web_search, code_interpreter, etc.) and parameters (temperature, max_tokens, etc.) for each individual model. This is time-consuming and error-prone when new models are added to connections.

Desired Solution you'd like

  • Add a global (admin-level) configuration section in Admin Settings → Models that allows admins to:

  1. Set default capabilities that apply to all newly discovered models:

    • Vision, File Upload, File Context, Web Search, Image Generation, Code Interpreter
    • Citations, Status Updates, Usage tracking, Builtin Tools

  2. Set default parameters for new models:

    • Temperature, Top P, Top K, Max Tokens, Seed, etc.

  3. Apply to All existing models (optional bulk action):

    • A button to apply current global defaults to ALL existing models at once
    • With appropriate confirmation dialog warning this is a destructive action

  4. One-time initialization behavior:

    • Defaults are applied when models are first discovered from connections
    • Existing models are not automatically affected
    • Admins can still override per-model via the Model Editor

Alternatives Considered

  • Per-connection defaults (Ollama vs OpenAI specific)
  • Manual configuration per model - Current behavior but tedious for many models

Additional Context

  • This feature would significantly reduce administrative overhead for organizations with many models. It provides a centralized policies (e.g way to enforce organizational., disable code_interpreter by default, set specific temperature defaults) that automatically apply to new models.

Example mockups (to help churn ideas):

Image Image
Originally created by @silentoplayz on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20658 Originally assigned to: @tjbck on GitHub. ### 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 - As an administrator managing multiple models across different connections (Ollama, OpenAI, etc.), I currently need to manually configure model capabilities (vision, web_search, code_interpreter, etc.) and parameters (temperature, max_tokens, etc.) for **each individual model**. This is time-consuming and error-prone when new models are added to connections. ### Desired Solution you'd like - Add a global (admin-level) configuration section in **Admin Settings → Models** that allows admins to: 1. **Set default capabilities** that apply to all newly discovered models: - Vision, File Upload, File Context, Web Search, Image Generation, Code Interpreter - Citations, Status Updates, Usage tracking, Builtin Tools 2. **Set default parameters** for new models: - Temperature, Top P, Top K, Max Tokens, Seed, etc. 3. **Apply to All existing models** (optional bulk action): - A button to apply current global defaults to ALL existing models at once - With appropriate confirmation dialog warning this is a destructive action 4. **One-time initialization behavior**: - Defaults are applied when models are first discovered from connections - Existing models are not automatically affected - Admins can still override per-model via the Model Editor ### Alternatives Considered - Per-connection defaults (Ollama vs OpenAI specific) - Manual configuration per model - **Current behavior** but tedious for many models ### Additional Context - This feature would significantly reduce administrative overhead for organizations with many models. It provides a centralized policies (e.g way to enforce organizational., disable code_interpreter by default, set specific temperature defaults) that automatically apply to new models. Example mockups (to help churn ideas): <img width="693" height="540" alt="Image" src="https://github.com/user-attachments/assets/ad8a8cb3-fc2f-484c-a6c3-287ff9839659" /> <img width="2344" height="534" alt="Image" src="https://github.com/user-attachments/assets/d99de4ff-b5a0-419e-ae30-44cc5673820e" />
GiteaMirror commented 2026-05-25 12:01:06 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 13, 2026):

Related: https://github.com/open-webui/open-webui/pull/20589

<!-- gh-comment-id:3899103965 --> @tjbck commented on GitHub (Feb 13, 2026): Related: https://github.com/open-webui/open-webui/pull/20589
GiteaMirror commented 2026-05-25 12:01:08 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 13, 2026):

Related: #14326

<!-- gh-comment-id:3899304780 --> @tjbck commented on GitHub (Feb 13, 2026): Related: #14326
GiteaMirror commented 2026-05-25 12:01:10 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Feb 22, 2026):

Also related - https://github.com/open-webui/open-webui/pull/20503

<!-- gh-comment-id:3940014510 --> @silentoplayz commented on GitHub (Feb 22, 2026): Also related - https://github.com/open-webui/open-webui/pull/20503
GiteaMirror commented 2026-05-25 12:01:13 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 22, 2026):

Addressed in dev.

<!-- gh-comment-id:3941869027 --> @tjbck commented on GitHub (Feb 22, 2026): Addressed in dev.
GiteaMirror commented 2026-05-25 12:01:14 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 22, 2026):

HELL YEAH this is SICK

<!-- gh-comment-id:3941882379 --> @Classic298 commented on GitHub (Feb 22, 2026): HELL YEAH this is SICK
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#138979
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?