Describe the bug
The addon may switch API profiles without user interaction. It looks like it switches API profiles when switching modes, which may happen automatically (with consent). But when switching modes by instructing Zoo to do so during a chat, the user has no oppertunity to also switch the API profile back to where it was sat.
The broader point is: it should never switch API profiles for any reason, unless the user clicks on the little selector and makes a choice. I don't think there is any valid reason to, when switching modes, to also switch API profiles. Especially seeing that there's no option in the settings to tie modes to API profiles.
This issue is important for billing purposes, as we serve multiple customers, and we need to be able to confidently separate the cost for each.
To Reproduce
Steps to reproduce the behavior:
- Have multiple API profiles
- Start a chat in Architect mode
- At some point Architect will offer to switch to Code
- Carry on doing so, and notice how API profile switches as well
Workaround
The workaround is a bit naff, but it serves the purpose. Before starting to work on a different customer (which implies a different API profile) just select each mode and set the correct API profile for each. That way, switching modes (automatically or manually) will keep the correct API profile that I have selected.
Expected behavior
The API profile should never change unless the user selects one explicitly
What version of zoo are you running
i.e. 3.54.1
Additional context
This issue also existed in Roo, and it was almost fixed. There is a draft PR for it, but it is AI generated, so it needs to be carefully reviewed.
Describe the bug
The addon may switch API profiles without user interaction. It looks like it switches API profiles when switching modes, which may happen automatically (with consent). But when switching modes by instructing Zoo to do so during a chat, the user has no oppertunity to also switch the API profile back to where it was sat.
The broader point is: it should never switch API profiles for any reason, unless the user clicks on the little selector and makes a choice. I don't think there is any valid reason to, when switching modes, to also switch API profiles. Especially seeing that there's no option in the settings to tie modes to API profiles.
This issue is important for billing purposes, as we serve multiple customers, and we need to be able to confidently separate the cost for each.
To Reproduce
Steps to reproduce the behavior:
Workaround
The workaround is a bit naff, but it serves the purpose. Before starting to work on a different customer (which implies a different API profile) just select each mode and set the correct API profile for each. That way, switching modes (automatically or manually) will keep the correct API profile that I have selected.
Expected behavior
The API profile should never change unless the user selects one explicitly
What version of zoo are you running
i.e. 3.54.1
Additional context
This issue also existed in Roo, and it was almost fixed. There is a draft PR for it, but it is AI generated, so it needs to be carefully reviewed.