[GH-ISSUE #22996] issue: Default Model Metadata & Params not reflected in Model Editor UI

GiteaMirror commented

2026-04-20 02:23:13 -05:00

Owner

Originally created by @kjpoccia on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22996

Check Existing Issues

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

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

No response

Operating System

macOS Tahoe

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

When an admin configures default model capabilities, builtin tools, default features, or parameters through Admin Settings → Models → Settings, those defaults should be visible in the Model Editor when viewing any model that uses these settings (that is, the frontend should show the settings that are actually used).

Actual Behavior

The model editor always initializes from hardcoded defaults (DEFAULT_CAPABILITIES in constants.ts with everything enabled, empty builtin tools, empty default features, empty parameters) regardless of what the admin has configured. The admin-configured defaults are only applied at runtime in the backend via get_all_models() and chat_completion().

There's another issue at play here too. Given that these settings are not shown in the model editor, if an admin (or user in Workspace Models) adjusts even unrelated settings and hits save, they'll be unknowingly overwriting the default settings for that model.

Steps to Reproduce

In an admin account, go to Admin Settings -> Models -> Settings. Turn off one of the Builtin Tools (let's say the timestamp tool)
Click Save
Go to one of your base models that you haven't edited before. Observe that the timestamp tool is still checked
Start a new chat with that model and ask it to call the get_current_timestamp tool. It won't have access to it.

This displays a mismatch between what is displayed for the model and the actual model behavior

Logs & Screenshots

The below displays the issue. I showed adding the connection to make clear that these models were not customized prior to.

Additional Information

We've been hoping for a feature like this and are excited to use it. We'd also like the ability to click a button (per model, globally, whatever will be accepted) to apply these default settings to the currently available models. Happy to work on this display issue (assuming this behavior is unintended) as well as a global/per-model "apply default settings" feature.

Originally created by @kjpoccia on GitHub (Mar 24, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22996 ### 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 Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System macOS Tahoe ### 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 When an admin configures default model capabilities, builtin tools, default features, or parameters through Admin Settings → Models → Settings, those defaults should be visible in the Model Editor when viewing any model that uses these settings (that is, the frontend should show the settings that are actually used). ### Actual Behavior The model editor always initializes from hardcoded defaults (DEFAULT_CAPABILITIES in constants.ts with everything enabled, empty builtin tools, empty default features, empty parameters) regardless of what the admin has configured. The admin-configured defaults are only applied at runtime in the backend via get_all_models() and chat_completion(). There's another issue at play here too. Given that these settings are not shown in the model editor, if an admin (or user in Workspace Models) adjusts even unrelated settings and hits save, they'll be unknowingly overwriting the default settings for that model. ### Steps to Reproduce * In an admin account, go to Admin Settings -> Models -> Settings. Turn off one of the Builtin Tools (let's say the timestamp tool) * Click Save * Go to one of your base models that you haven't edited before. Observe that the timestamp tool is still checked * Start a new chat with that model and ask it to call the get_current_timestamp tool. It won't have access to it. This displays a mismatch between what is displayed for the model and the actual model behavior ### Logs & Screenshots The below displays the issue. I showed adding the connection to make clear that these models were not customized prior to. ![Image](https://github.com/user-attachments/assets/5944e2e9-09dd-40cb-b581-099160e94054) ### Additional Information We've been hoping for a feature like this and are excited to use it. We'd also like the ability to click a button (per model, globally, whatever will be accepted) to apply these default settings to the currently available models. Happy to work on this display issue (assuming this behavior is unintended) as well as a global/per-model "apply default settings" feature.

GiteaMirror added the bug label 2026-04-20 02:23:13 -05:00

GiteaMirror closed this issue

2026-04-20 02:23:14 -05:00

GiteaMirror commented

2026-04-20 02:23:15 -05:00

Author

Owner

@tjbck commented on GitHub (Mar 25, 2026):

Params are intended to be shown as "default"; metadata should now match the default.

@tjbck commented on GitHub (Mar 25, 2026): Params are intended to be shown as "default"; metadata should now match the default.

GiteaMirror commented

2026-04-20 02:23:16 -05:00

Author

Owner

@Classic298 commented on GitHub (Mar 25, 2026):

cdc2b3bf85

@Classic298 commented on GitHub (Mar 25, 2026): https://github.com/open-webui/open-webui/commit/cdc2b3bf850044051aafcd46f22fb25a1899788c

GiteaMirror referenced this issue

2026-04-25 08:35:25 -05:00

[GH-ISSUE #19861] issue: Sentence skipping in voice mode #34549

GiteaMirror referenced this issue

2026-05-05 21:24:03 -05:00

[GH-ISSUE #19861] issue: Sentence skipping in voice mode #57686