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
When registering models via pipes(), only id and name are recognized. Other fields like profile_image_url, description, capabilities, and model_config are ignored and can only be configured manually through the Admin panel.
Desired Solution you'd like
Support additional model metadata fields and others information in pipes() return.
Alternatives Considered
No response
Additional Context
No response
Originally created by @CoronaAustralis on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22135
### 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
When registering models via pipes(), only id and name are recognized. Other fields like `profile_image_url`, `description`, `capabilities`, and `model_config` are ignored and can only be configured manually through the Admin panel.
### Desired Solution you'd like
Support additional model metadata fields and others information in pipes() return.
### Alternatives Considered
_No response_
### Additional Context
_No response_
needs discussion - current behaviour should probably be sufficient since you can configure it from the admin panel anyways
<!-- gh-comment-id:3985357875 -->
@Classic298 commented on GitHub (Mar 2, 2026):
needs discussion - current behaviour should probably be sufficient since you can configure it from the admin panel anyways
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.
Originally created by @CoronaAustralis on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22135
Check Existing Issues
Verify Feature Scope
Problem Description
When registering models via pipes(), only id and name are recognized. Other fields like
profile_image_url,description,capabilities, andmodel_configare ignored and can only be configured manually through the Admin panel.Desired Solution you'd like
Support additional model metadata fields and others information in pipes() return.
Alternatives Considered
No response
Additional Context
No response
@Classic298 commented on GitHub (Mar 2, 2026):
needs discussion - current behaviour should probably be sufficient since you can configure it from the admin panel anyways