[PR #19273] [CLOSED] feat: Admin model pinning #64010

New Issue

GiteaMirror · 2026-05-06T09:16:25-05:00

GiteaMirror commented

2026-05-06 09:16:25 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/19273
Author: @Classic298
Created: 11/18/2025
Status: ❌ Closed

Base: dev ← Head: admin-model-pinning

📝 Commits (1)

0b4372e Admin model pinning (#23) (#69)

📊 Changes

8 files changed (+136 additions, -84 deletions)

View changed files

📝 backend/open_webui/config.py (+4 -0)
📝 backend/open_webui/main.py (+4 -1)
📝 backend/open_webui/routers/configs.py (+4 -0)
📝 src/lib/components/admin/Settings/Models/ConfigureModelsModal.svelte (+33 -73)
➕ src/lib/components/admin/Settings/Models/ModelListSelector.svelte (+59 -0)
📝 src/lib/components/chat/ModelSelector.svelte (+1 -1)
📝 src/lib/components/layout/Sidebar.svelte (+1 -5)
📝 src/lib/components/layout/Sidebar/PinnedModelList.svelte (+30 -4)

📄 Description

Pull Request Checklist

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch may lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
Agentic AI Code:: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review and manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- feat: Introduces a new feature or enhancement to the codebase

Changelog Entry

Description

Adds an admin configuration option to set default pinned models for all users, following the exact same behavior pattern as the existing "default models" setting. Admins can now define which models should be pinned to the sidebar by default, improving the out-of-box experience for new users while preserving user autonomy.

Pattern Matching: This feature precisely mirrors the existing default models behavior:

Admins set defaults via Admin Settings > Models > Settings modal
New users automatically inherit admin-configured defaults
Once a user customizes their pinned models (pin, unpin, or reorder), the pinnedModelsCustomized flag is set
Users with the customization flag are never affected by future admin changes to defaults
Users maintain full control and can override admin defaults at any time

User-Friendly Behavior:

Non-intrusive: Defaults only apply to users who haven't customized their pinned models
Reversible: Users can immediately customize by pinning/unpinning any model
Transparent: Behaves identically to the well-established default models feature
Flexible: Admins can set multiple pinned models in a specific order

Existing Installations:

Fully backward compatible - no breaking changes
Existing user pinned models remain unchanged (implicitly have pinnedModelsCustomized: true)
Users with no pinned models will see admin defaults on next session
If no admin defaults are configured, current behavior is unchanged

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/19273 **Author:** [@Classic298](https://github.com/Classic298) **Created:** 11/18/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `admin-model-pinning` --- ### 📝 Commits (1) - [`0b4372e`](https://github.com/open-webui/open-webui/commit/0b4372ec31087785c1493df8d259db90cc279137) Admin model pinning (#23) (#69) ### 📊 Changes **8 files changed** (+136 additions, -84 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+4 -0) 📝 `backend/open_webui/main.py` (+4 -1) 📝 `backend/open_webui/routers/configs.py` (+4 -0) 📝 `src/lib/components/admin/Settings/Models/ConfigureModelsModal.svelte` (+33 -73) ➕ `src/lib/components/admin/Settings/Models/ModelListSelector.svelte` (+59 -0) 📝 `src/lib/components/chat/ModelSelector.svelte` (+1 -1) 📝 `src/lib/components/layout/Sidebar.svelte` (+1 -5) 📝 `src/lib/components/layout/Sidebar/PinnedModelList.svelte` (+30 -4) </details> ### 📄 Description # Pull Request Checklist **Before submitting, make sure you've checked the following:** - [X] **Target branch:** Verify that the pull request targets the `dev` branch. Not targeting the `dev` branch may lead to immediate closure of the PR. - [X] **Description:** Provide a concise description of the changes made in this pull request. - [X] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [X] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [X] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [X] **Testing:** Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description. - [X] **Agentic AI Code:**: Confirm this Pull Request is **not written by any AI Agent** or has at least gone through additional human review **and** manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [X] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [X] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **feat**: Introduces a new feature or enhancement to the codebase # Changelog Entry ### Description Adds an admin configuration option to set default pinned models for all users, following the exact same behavior pattern as the existing "default models" setting. Admins can now define which models should be pinned to the sidebar by default, improving the out-of-box experience for new users while preserving user autonomy. **Pattern Matching: This feature precisely mirrors the existing default models behavior:** - Admins set defaults via Admin Settings > Models > Settings modal - New users automatically inherit admin-configured defaults - Once a user customizes their pinned models (pin, unpin, or reorder), the pinnedModelsCustomized flag is set - Users with the customization flag are never affected by future admin changes to defaults - Users maintain full control and can override admin defaults at any time **User-Friendly Behavior:** 1. Non-intrusive: Defaults only apply to users who haven't customized their pinned models 2. Reversible: Users can immediately customize by pinning/unpinning any model 3. Transparent: Behaves identically to the well-established default models feature 4. Flexible: Admins can set multiple pinned models in a specific order **Existing Installations:** 1. Fully backward compatible - no breaking changes 2. Existing user pinned models remain unchanged (implicitly have pinnedModelsCustomized: true) 3. Users with no pinned models will see admin defaults on next session 4. If no admin defaults are configured, current behavior is unchanged ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-06 09:16:25 -05:00

GiteaMirror closed this issue

2026-05-06 09:16:27 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#64010