mirror of
https://github.com/router-for-me/Cli-Proxy-API-Management-Center.git
synced 2026-04-25 07:35:56 +03:00
[GH-ISSUE #20] QOL Feature Requests #14
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Cli-Proxy-API-Management-Center#14
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 @DevGuyRash on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/router-for-me/Cli-Proxy-API-Management-Center/issues/20
Hello, I've been using this for ages hosting it remotely on my homelab and then accessing it from work and other places with many API keys.
I've thought of some quality of life features that are not urgent or necessary. However, if any of these would fit within the vision of the project, I believe they would be good QoL! These are all for the web UI.
Feat 1: View Loaded Models in Web-UI
Feat 1: Background Context
From work, I usually run a
curlcommand on/modelsto get the list of models, but this can be a problem sometimes when I do not have access to terminal of any kind and have to rely on accessing the/management.htmlpage instead.It's also helpful for debugging to see if a model is available with the account you used (like gemini 3 pro) by seeing which models loaded.
Feat 1: Deliverable
During initial loading of the server, also capture all loaded models per auth file. In the Auths tab, when you click the I info button, also include all loaded models (with providers maybe) for that auth key.
Feat 2: Healthcheck
This is taken straight from Cherry Studio. Whether this is per auth file or per-model or per-api-key would be up to you. Just a button that runs a health check and checks one or all models (associated with either an api key, auth file, etc) by sending a blank string or a short string like "Hello; only reply with 'hello'" or similar. Would tell you if a model is working properly or not.
Feat 3: Search inside of Logs
Search box above logs for searching logs with a count of all found matches. Allow regex searches. Great for filtering logs, especially with auto-refresh on.
Feat 4: Check for update
Checks github repo (or dockerhub) for an update on button press. Adds an update banner, current version running, and new version to update to somewhere and it stays like that until it either updates or the user presses the button again (in which case it may replace it with an even newer one if applicable)
Feat 5: No set amount of lines to track in usage
User can hit add or remove and then it adds/removes so long as there are enough models being used to have a line per model usage.
@luispater commented on GitHub (Dec 3, 2025):
These features are all very practical and worth considering for scheduling.
The main maintainer of the web-ui is currently a high school senior who will be taking the Gaokao (similar to the SAT/ACT in the US for college entrance) in June 2026, so adding new features might be slow.
@LTbinglingfeng commented on GitHub (Dec 3, 2025):
All these suggestions are excellent. Thank you for your proposals. I will gradually implement some of the achievable functions in the subsequent versions
@DevGuyRash commented on GitHub (Dec 4, 2025):
Appreciate the hard work as always!
Study hard and wishing the best of luck during the Gaokao!
@LTbinglingfeng commented on GitHub (Dec 4, 2025):
Thank you for your blessing Feat 5: No set amount of lines to track in usage has been implemented in v0.5.4
@LTbinglingfeng commented on GitHub (Dec 4, 2025):
Feat 3: Search inside of Logs is currently pending release
@LTbinglingfeng commented on GitHub (Dec 6, 2025):
We've implemented all the features mentioned in this issue, though there were some trade-offs in certain functions. Please check the latest version v0.5.8 for details.