mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #10368] Custom Plugin Framework / 3rd Party Add-ons #31400
Reference in New Issue
Block a user
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?
Originally created by @uwzis on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10368
Feature Request
Create a plugin system where developers can make their own plugins that aren't from the official main branch, but can be add-ons to OpenWebUI. I see so many PRs that are very useful and aren't going to be apart of the main branch. If these can be turned into plugins, then it allows anyone to add or even create custom plugins.
Not sure about implementing a repository for this plugin system like WordPress to only allow open source plugins on their repository but this would be a feature that could allow for much more innovation inside of the project.
@silentoplayz commented on GitHub (Feb 19, 2025):
That's what https://openwebui.com/ is for.
@uwzis commented on GitHub (Feb 19, 2025):
I apologize, I don't think I was clear on what I was proposing. This is for features either in development, or add-ons not pushed to main.
For Example:
In this PR https://github.com/open-webui/open-webui/pull/8576 implements a feature to allow more advanced feedback options. If this was based off a plugin then features that aren't going to be in the main can still be added to OpenWebUI if the user adds it manually.
Current Implementation:
Develop my own custom program that works with OpenWebUI and patch the project manually when deploying or after updating. These plugins are not on pushed to main due to some of them being very niche or early development.
Proposed Solution:
Develop my own plugin or use other open source plugins into OpenWebUI without patching it manually by editing programs and scripts but rather in the interface adding a custom plugin to get the features you are developing or implementing
I encourage you to reopen this for further discussion, I would love to help work on this.