mirror of
https://github.com/open-webui/community-platform.git
synced 2026-11-05 01:17:28 +00:00
[GH-ISSUE #21] feat: auto-migrate pre-0.5 tools/functions, or filter them from 'discovery' #17
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/community-platform#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @ThoughtPhotography on GitHub (Apr 20, 2025).
Original GitHub issue: https://github.com/open-webui/community-platform/issues/21
Check Existing Issues
Problem Description
Trying to discover new tools and functions on the website is endlessly frustrated because there's no sorting by date, or easy way to know which tools/functions are compatible with the version of open-webiu version you're using, etc.
Desired Solution you'd like
The ideal solution has 2 parts. Either alone would be a massive improvement.
1) If a user is clicking through to browse tools/functions from 0.5+, only show tools/functions that are actually compatible. It's anti-helpful to have a seemingly random 10 page list when half or more are unusable.
2) It's great there's a migration guide, but if the creator hasn't bothered to update, it's quite a lot to expect from the majority of users who aren't advanced enough to create tools/functions.
When incredible coding models like Gemini 2.5 Pro, DeepSeek R1/V3 etc. are accessible for free (or pennies) on OpenRouter, why is this an issue at all?
Every tool/function ever made could fit in the context window of Gemini and be converted in 1-2 shots, so if that's theoretically possible, surely they can be auto-migrated one at a time when a user tries to import them? 🤷♂️
Changes that essentially break everything are sometimes necessary, but so is fixing what you break. 😉
By adding this common sense functionality the experience is better for end users, creators in the Open-WebUI ecosystem, and even the core developers as they're more free to innovate without as much concern for backwards compatibility.
✌️
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Apr 20, 2025):
Upvote/Downvote + Comment features are WIP!
@tjbck commented on GitHub (Dec 7, 2025):
https://github.com/open-webui/community-platform/issues/28