Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
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 will lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request down below.
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:
BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work
Changelog Entry
Description
This PR introduces a "Bulk Model Capabilities" feature for admins, allowing them to efficiently update capabilities (e.g., Vision, Web Search) and default enabled features for all models at once. This streamlines the management of large model deployments where capability consistency is desired.
Added
Bulk Capabilities Modal: A new modal in Admin Settings > Models that allows toggling capabilities and default features for all models.
Backend Endpoint: Added PATCH /api/models/bulk/options to handle bulk updates of model metadata.
Frontend API Client: Added bulkUpdateModelOptions to call the new endpoint.
Select All / None: Helper buttons in the modal to quickly check/uncheck all capabilities.
Changed
Capabilities & DefaultFeatures: Updated these existing components to accept a showTitle prop, allowing them to be reused in the bulk modal without redundant headers.
Admin Settings: Added a "Bulk Capabilities" button to the Models tab toolbar.
Security
The new endpoint is restricted to users with the 'admin' role, ensuring only authorized personnel can make bulk changes.
Impact on Users
Global Effect: Changes applied via this bulk tool affect all users who have access to the modified models. For example, if "Web Search" is disabled for a model, it will be unavailable to both users and admins when using that specific model.
Access Levels: This feature does not modify model access control (who can see/use the model). It only modifies the capabilities available within those models.
Admin Override: Admins cannot bypass these model-level capability restrictions in the chat interface; they must re-enable the capability on the model (individually or via bulk update) to use it again.
Screenshots or Videos
This icon should likely be adjusted.
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.
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
🔄 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/20503
**Author:** [@silentoplayz](https://github.com/silentoplayz)
**Created:** 1/9/2026
**Status:** ❌ Closed
**Base:** `dev` ← **Head:** `feat/bulk-model-capabilities`
---
### 📝 Commits (1)
- [`ab43edd`](https://github.com/open-webui/open-webui/commit/ab43edd7f12eb04cd58f299b8fe7b488f83617d5) feat(admin): add bulk model capabilities modal
### 📊 Changes
**6 files changed** (+382 additions, -6 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/routers/models.py` (+95 -0)
📝 `src/lib/apis/models/index.ts` (+34 -0)
📝 `src/lib/components/admin/Settings/Models.svelte` (+24 -0)
➕ `src/lib/components/admin/Settings/Models/BulkCapabilitiesModal.svelte` (+217 -0)
📝 `src/lib/components/workspace/Models/Capabilities.svelte` (+6 -3)
📝 `src/lib/components/workspace/Models/DefaultFeatures.svelte` (+6 -3)
</details>
### 📄 Description
# Pull Request Checklist
### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
**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 will lead to immediate closure of the PR.**
- [x] **Description:** Provide a concise description of the changes made in this pull request down below.
- [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.
- [ ] **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:
- **BREAKING CHANGE**: Significant changes that may affect compatibility
- **build**: Changes that affect the build system or external dependencies
- **ci**: Changes to our continuous integration processes or workflows
- **chore**: Refactor, cleanup, or other non-functional code changes
- **docs**: Documentation update or addition
- **feat**: Introduces a new feature or enhancement to the codebase
- **fix**: Bug fix or error correction
- **i18n**: Internationalization or localization changes
- **perf**: Performance improvement
- **refactor**: Code restructuring for better maintainability, readability, or scalability
- **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- **test**: Adding missing tests or correcting existing tests
- **WIP**: Work in progress, a temporary label for incomplete or ongoing work
# Changelog Entry
### Description
This PR introduces a "Bulk Model Capabilities" feature for admins, allowing them to efficiently update capabilities (e.g., Vision, Web Search) and default enabled features for all models at once. This streamlines the management of large model deployments where capability consistency is desired.
### Added
- **Bulk Capabilities Modal**: A new modal in Admin Settings > Models that allows toggling capabilities and default features for all models.
- **Backend Endpoint**: Added `PATCH /api/models/bulk/options` to handle bulk updates of model metadata.
- **Frontend API Client**: Added `bulkUpdateModelOptions` to call the new endpoint.
- **Select All / None**: Helper buttons in the modal to quickly check/uncheck all capabilities.
### Changed
- **Capabilities & DefaultFeatures**: Updated these existing components to accept a `showTitle` prop, allowing them to be reused in the bulk modal without redundant headers.
- **Admin Settings**: Added a "Bulk Capabilities" button to the Models tab toolbar.
### Security
- The new endpoint is restricted to users with the 'admin' role, ensuring only authorized personnel can make bulk changes.
### Impact on Users
- **Global Effect:** Changes applied via this bulk tool affect all users who have access to the modified models. For example, if "Web Search" is disabled for a model, it will be unavailable to both users and admins when using that specific model.
- **Access Levels:** This feature does not modify model access control (who can see/use the model). It only modifies the capabilities available within those models.
- **Admin Override:** Admins cannot bypass these model-level capability restrictions in the chat interface; they must re-enable the capability on the model (individually or via bulk update) to use it again.
---
### Screenshots or Videos
<img width="693" height="540" alt="image" src="https://github.com/user-attachments/assets/468c3731-884f-48ed-af5f-a056fc891abe" />
<img width="144" height="111" alt="image" src="https://github.com/user-attachments/assets/65b33246-81fb-48e9-a329-c0d963d78f78" />
This icon should likely be adjusted.
### 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.
> [!NOTE]
> Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/20503
Author: @silentoplayz
Created: 1/9/2026
Status: ❌ Closed
Base:
dev← Head:feat/bulk-model-capabilities📝 Commits (1)
ab43eddfeat(admin): add bulk model capabilities modal📊 Changes
6 files changed (+382 additions, -6 deletions)
View changed files
📝
backend/open_webui/routers/models.py(+95 -0)📝
src/lib/apis/models/index.ts(+34 -0)📝
src/lib/components/admin/Settings/Models.svelte(+24 -0)➕
src/lib/components/admin/Settings/Models/BulkCapabilitiesModal.svelte(+217 -0)📝
src/lib/components/workspace/Models/Capabilities.svelte(+6 -3)📝
src/lib/components/workspace/Models/DefaultFeatures.svelte(+6 -3)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
Before submitting, make sure you've checked the following:
devbranch. Not targeting thedevbranch will lead to immediate closure of the PR.Changelog Entry
Description
This PR introduces a "Bulk Model Capabilities" feature for admins, allowing them to efficiently update capabilities (e.g., Vision, Web Search) and default enabled features for all models at once. This streamlines the management of large model deployments where capability consistency is desired.
Added
PATCH /api/models/bulk/optionsto handle bulk updates of model metadata.bulkUpdateModelOptionsto call the new endpoint.Changed
showTitleprop, allowing them to be reused in the bulk modal without redundant headers.Security
Impact on Users
Screenshots or Videos
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.