Is your feature request related to a problem? Please describe.
It would be great to extend OpenWebUI by allowing users to create custom 'pages'/integrations. Currently, there’s no simple way to add personalized features or workflows directly into the interface. It would open a world of possibilities.
Describe the solution you'd like
Support for custom integrations, where users can upload a Python script that defines both the menu placement (e.g., in the profile, settings, or the context menu above the profile) and the functionality of the integration itself. Similar to "Functions," but designed to expose a page with custom functionality. This would enable features such as a custom usage tracker, specialized dashboards, or embedded tools.
Describe alternatives you've considered
Building standalone tools that interact with OpenWebUI via API, but this lacks integration.
Modifying the core codebase, which isn’t user-friendly or sustainable.
Additional context
For example, users could create a dashboard for managing billing or whatsoever, which could be especially valuable if the instance is shared.
This would make OpenWebUI much more flexible and personalized.
Originally created by @Fusseldieb on GitHub (Dec 3, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7573
# Feature Request
**Is your feature request related to a problem? Please describe.**
It would be great to extend OpenWebUI by allowing users to create custom 'pages'/integrations. Currently, there’s no simple way to add personalized features or workflows directly into the interface. It would open a world of possibilities.
**Describe the solution you'd like**
Support for custom integrations, where users can upload a Python script that defines both the menu placement (e.g., in the profile, settings, or the context menu above the profile) and the functionality of the integration itself. Similar to "Functions," but designed to expose a page with custom functionality. This would enable features such as a custom usage tracker, specialized dashboards, or embedded tools.
**Describe alternatives you've considered**
- Building standalone tools that interact with OpenWebUI via API, but this lacks integration.
- Modifying the core codebase, which isn’t user-friendly or sustainable.
**Additional context**
For example, users could create a dashboard for managing billing or whatsoever, which could be especially valuable if the instance is shared.
This would make OpenWebUI much more flexible and personalized.
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 @Fusseldieb on GitHub (Dec 3, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7573
Feature Request
Is your feature request related to a problem? Please describe.
It would be great to extend OpenWebUI by allowing users to create custom 'pages'/integrations. Currently, there’s no simple way to add personalized features or workflows directly into the interface. It would open a world of possibilities.
Describe the solution you'd like
Support for custom integrations, where users can upload a Python script that defines both the menu placement (e.g., in the profile, settings, or the context menu above the profile) and the functionality of the integration itself. Similar to "Functions," but designed to expose a page with custom functionality. This would enable features such as a custom usage tracker, specialized dashboards, or embedded tools.
Describe alternatives you've considered
Additional context
For example, users could create a dashboard for managing billing or whatsoever, which could be especially valuable if the instance is shared.
This would make OpenWebUI much more flexible and personalized.