-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: users can choose which model(s) to chat with #364
Comments
@louis-jan who is best to pick up this issue later? Can you help assign. I noticed you more or less have the core logic implemented, i.e. where you had 2 models simultaneously respond to 1 user query |
@namchuai can take ownership of this (assigned), and I will support the ability to enable/disable providers |
this enhancement will also address #386 (can just select active providers to chat with) |
Closing this as our UI is undergoing significant change. We can reopen in the future. |
Problem
Thanks to @louis-jan 's PR: #361
Users can chat with multiple models (gpt via API + a locally running model)
We should let users choose which model(s) they are chatting with
Success Criteria
See designs:
![image](https://private-user-images.githubusercontent.com/69952136/275445500-8e6398c9-110c-49c7-b58e-564f037b4347.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNjc1NzcsIm5iZiI6MTczOTA2NzI3NywicGF0aCI6Ii82OTk1MjEzNi8yNzU0NDU1MDAtOGU2Mzk4YzktMTEwYy00OWM3LWI1OGUtNTY0ZjAzN2I0MzQ3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDAyMTQzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhMjA4OTQ3ZTQ4MDI1NDQ3NWVhMjZlM2M4ZjQyNWI4NWZlNjI5M2QwNTg3ZThjZThkN2I0MjA5N2QyY2NlMmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.qcarTzaynT7ICVQU0LQZ8JEA0b830KbE4K4fpnZbBgA)
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: