github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

feat: more categories for direct. #5212

New Issue
Closed
opened 2025-11-11 16:14:44 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 16:14:44 -06:00
Owner
Copy Link
Copy Source

Originally created by @D3rhami on GitHub (May 18, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

When using multiple APIs for models (e.g., client APIs, company APIs, personal OpenRouter, etc.), the current categorization system under "Direct" becomes unclear and hard to manage. After a while, it's difficult to tell which model belongs to which API source. The existing categories like "All", "Local", and "Direct" are too limited for power users who connect many APIs.

Desired Solution you'd like

I would like to have more descriptive and customizable categories or tags for "Direct" models, such as:

  • Client API
  • Company API
  • Personal OpenRouter
  • etc as subcategory

These tags could be either auto-assigned based on API name or user-definable. This would significantly improve model organization and usability for users managing many external APIs.

Alternatives Considered

No response

Additional Context

No response

Originally created by @D3rhami on GitHub (May 18, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description When using multiple APIs for models (e.g., client APIs, company APIs, personal OpenRouter, etc.), the current categorization system under "Direct" becomes unclear and hard to manage. After a while, it's difficult to tell which model belongs to which API source. The existing categories like "All", "Local", and "Direct" are too limited for power users who connect many APIs. ### Desired Solution you'd like I would like to have more descriptive and customizable categories or tags for "Direct" models, such as: - Client API - Company API - Personal OpenRouter - etc as subcategory These tags could be either auto-assigned based on API name or user-definable. This would significantly improve model organization and usability for users managing many external APIs. ### Alternatives Considered _No response_ ### Additional Context _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5212