Skip to content
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

Feature request - allow model to "stick" to chat (Per-Chat Model Selection) #643

Open
syberkitten opened this issue Sep 19, 2024 · 3 comments

Comments

@syberkitten
Copy link

Why

Different conversations often require different models for optimal performance. The current global model selection creates inefficiency, requiring users to switch models frequently when changing between chats.

Description

I propose implementing a per-chat model selection feature. This would allow users to assign specific models to individual chats, eliminating the need to change models when switching conversations.

Requirements

  1. Enable model selection for each individual chat.
  2. Persist model selection per chat across sessions.
  3. Allow changing a chat's model without affecting others.
  4. Display the current model for each chat in the interface.
  5. Set a default model for new chats, customizable by users.
  6. Provide an option for bulk model changes across multiple chats.
  7. Ensure the feature doesn't negatively impact app performance.

Expected Benefits

  • Improved user experience with reduced model switching.
  • Enhanced productivity when working across multiple chats.
  • Greater flexibility in model usage for various conversation types.
@JJsilvera1
Copy link

yes I vote for this also. A sticky box or something so not all are affected.

@enricoros
Copy link
Owner

Thanks @syberkitten @JJsilvera1 - by any chance are you guys on V2 already? The branch is still hot, but getting closer to a higher level of quality, and definitely night and day compared to V1.

Question for you. I had requests for different models, and it's hard to support all of them with minimal UI/Code complexity:

  1. global model, works poorly (current)
  2. one model per chat
    • when creating a new chat, the current (or last used, or smarter) model and personas get copied to the new
  3. one models per Persona
    • this way changing personas can change the system prompt and model
  4. one model per persona, but with a per-chat override
    • i.e. a Persona has its own default model (assigned in the persona editor), but on a per-chat basis one can override the model and just choose a different model

Please let me know if any of these (or a combination thereof, or something else) would be a productive pattern for you. And also consider a future in which we have multiple branches per chats (split screen, or different computers, and the persona-models are per-branch).

@JJsilvera1
Copy link

JJsilvera1 commented Sep 20, 2024

To be honest, I'm not exactly sure if I'm on what version. Do I just refresh the browser and it updates or do I have to do something more?

No, I'm on 1.16.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants