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
The LLM model field in the settings interface exhibits inconsistent behavior depending on the selected provider.
For OpenAI, the field must be left empty to function correctly. Conversely, the MistralAI provider fails to function if the model field is left empty, leading to errors or failed connections.
Expected Behavior
The default LLM model value should be auto-populated when selecting an AI provider.
Current Behavior
Possible Solution
Implement default value auto-population for the LLM model field based on the selected AI provider. Fix the default behaviour for OpenAI and MistralaAI.
Steps to Reproduce
Go to the settings interface.
Select the OpenAI provider and enter an appropriate LLM model name.
Observe that the provider only works when the model field is empty.
Select the MistralAI provider and leave the model field empty.
Observe that the provider fails to function, leading to errors or failed connections.
Context (Environment)
Application
VSCode (All versions)
Detailed Description
Possible Implementation
The text was updated successfully, but these errors were encountered:
Bug Report 🐛
The LLM model field in the settings interface exhibits inconsistent behavior depending on the selected provider.
For OpenAI, the field must be left empty to function correctly. Conversely, the MistralAI provider fails to function if the model field is left empty, leading to errors or failed connections.
Expected Behavior
The default LLM model value should be auto-populated when selecting an AI provider.
Current Behavior
Possible Solution
Implement default value auto-population for the LLM model field based on the selected AI provider. Fix the default behaviour for OpenAI and MistralaAI.
Steps to Reproduce
Context (Environment)
Application
Detailed Description
Possible Implementation
The text was updated successfully, but these errors were encountered: