Closed flutterrausch closed 1 year ago
Unfortunately changing VS Code extension settings is not very straightforward. For backward compatibility there is some work that needs to be done in order to update how settings work today. Though I see your point. How about having a shortcut within the extension to directly open model or method settings? I had it in the home page a while ago but then removed it since it wasn't widely used. Changing models reset your conversation anyway, so opening a + New chat
and being able to click one button to switch model/method should be sufficient to address this issue.
Yep, a command (that can get a shortcut) to choose between some defaults would be nice. Maybe SelectDefault1, 2.. is better than ToggleDefault.
A button, that is only visible in "fresh" new conversations might be confusing, since it's not always available/visible. It makes sense, but the user doesn't know why. Maybe an "always there" button with a hint that it ends the current conversation?
Have a nice day :)
Describe the feature
The quality of responses of ChatGPT is still often much better than from the API, also more verbose and more room to "discuss" things.
I find myself quite often switching back and forth between the two. Default API, often switching to browser login for better answers. The dropdowns for "login method" and model are far apart, this is a bit suboptimal.
Here is an UI idea to solve that:
settings dropdown "default model for browser login"
settings dropdown "default model for API"
additinal dropdown "use login" / "use API" This would ideally be positioned in the sidebar, to quickly switch, if an API answer isn't satifying (or first option in settings to immediatly find it).
Context: I still use the free demo (API running out end of March). Maybe this all could be solved by paying for ChatGPT plus?