Open jay-fibi opened 5 months ago
CC @toolmantim thoughts? On one hand I agree. On the other hand an enterprise user can't do anything with this information and it's on the admin to configure.
What's our Enterprise LLM upgrade process? Do we reach out to admins, or rely on them to know if they should update the model? Visibility (for both admin and non-admin Cody users) would help with the latter.
I'd suggest the UI would be a 80% opacity label (no drop down) with a tooltip.
To add to this issue: From an enterprise prospective, this would be a helpful item to have. Consider the following situations: An Admin sets up LLM access to more than one provider, this can be done for 2 reasons, first - to allow for dev preferences, second, some LLM providers (like Azure) impose caps/rate limits on given model deployments, so with this option, devs can switch on the fly to avoid these caps.
Another example would be ollama installs, where available models can be numerous based on the ollama install.
Just some thoughts from another enterprise user.
This issue is marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed automatically in 5 days.
Bump
Version
v1.10.0
Describe the bug
Platform: MacOS
Steps to reproduce:
Observed behavior:
LLM dropdown is missing.
Expected behavior
It should be disabled but appear there so the user get aware of the LLM.
Additional context