[GH-ISSUE #14003] feat: more categories for direct. #17101

Closed
opened 2026-04-19 22:51:22 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @D3rhami on GitHub (May 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14003

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). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14003 ### 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17101