Reframe the Provider and Agent configuration in settings

[vincentsong]

I am quite confused now, what's the hirachy of the settings?

When I changed the 'mode' in Agent settings, the active configuration profile was changed in Provider Settings as well. I thought the Agent mode is separated with Provider Settings.

What I expect is when I select one Agent mode, it should be applied to all of the providers which I have configured. Or is it a Bug?

@mrubens

[mrubens]

Sorry this is confusing! The mode remembers the last API configuration profile that was associated with it. The idea is that you can use something like o1 with Architect and Sonnet or Deepseek for Code, and when you switch between modes in the chat it will also switch the providers.

It's particularly confusing on the settings screen because of the hierarchy though... does what I'm saying make sense? Any ideas for how to make it better? Thank you!

[vincentsong]

Thank you @mrubens for the explaination. Now I understand. The confusion happend when I want to change current Provider's mode, since it will load another provider that was assositated with. So the order should be, 1 select the mode 2 select the provider for the mode. But users should have a chance to confirm they really want to change the provider's mode, just in case they selected wrong one.

Then I suggest if we could show the current provider's mode name besides the provider's name ,and give a confirm option to let the user know he is changing current provider's mode now (which also means it will override the old agent mode's provider). Something like this:

---

Configuration Profile (Code -> Ask ):

after user confirm, it becomes

Configuration Profile (Ask):

[nikhilmaddirala]

The settings screen is extremely confusing and I don't understand the hierarchy. It would be great to have a brief documentation page explaining how the hierarchy works.

[vincentsong]

@mrubens I see you removed the 'mode' from settings. So we can only change it from the dialogue view. I will close this.

[mrubens]

Thank you for the feedback!