You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have configured various OpenAI, Groq and local Ollama models, and especially for the latter I regularly remove some and add others. Sometimes I forget the exact model name, or the alias I configured, especially when I have multiple sizes of the same model and I forget how many billion parameters a model had.
Then currently I have to mods --settings to open the YAML file, and scroll down to see the list.
I'd like to propose the introduction of a new command or flag to show the configured models in a list or table. For example a list could look like:
With the main goal to quickly see the aliases, to then use in the next command with mods -m claude for example.
One alternative could be an interactive model selection with fuzzy search, which might alleviate the need for this model list. But that could also be an additional feature, so I'll create a separate issue for that.
The text was updated successfully, but these errors were encountered:
I have configured various OpenAI, Groq and local Ollama models, and especially for the latter I regularly remove some and add others. Sometimes I forget the exact model name, or the alias I configured, especially when I have multiple sizes of the same model and I forget how many billion parameters a model had.
Then currently I have to
mods --settings
to open the YAML file, and scroll down to see the list.I'd like to propose the introduction of a new command or flag to show the configured models in a list or table. For example a list could look like:
With the main goal to quickly see the aliases, to then use in the next command with
mods -m claude
for example.One alternative could be an interactive model selection with fuzzy search, which might alleviate the need for this model list. But that could also be an additional feature, so I'll create a separate issue for that.
The text was updated successfully, but these errors were encountered: