Possibility of hiding aliases from the WEB UI but allowing it on the API endpoints

As in production, many models might come and go, it's difficult to have tools (e.g.: https://continue.dev ) which rely on hardcoded names for the models/workers it wants to use.

For that, the use of aliases makes sense. You can set, for example, an alias to "Mistral" regardless of the mistral version in use (right now it's 0.2).

I set, for example, aliases for "fast", "code" and "large", which at some point in time might point to the current iteration of mistral, starcoder and llama2-70, for example.

But by setting aliases, one also duplicate the entries at the list of available models on the web UI.

What do you think about a way to not show an aliased model? Or the possibility to exclude some models from the UI?

I have been thinking of checking for a string, say "alias-code" and models with this name are simply ignored by the UI. Another way would be to have a command line parameter telling which ones to ignore, or a config file.

What's your opinion?

Start by tracing how model aliases are represented in the WEB UI and exposed through the API endpoints. The issue proposes hiding aliased or excluded models from the UI while keeping them available through the API, but leaves the configuration mechanism undecided; done would require an agreed behavior and an implementation that preserves API access.