Skip to content

Request: Different model for different features #135

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

Open
ponpat opened this issue Feb 18, 2025 · 3 comments
Open

Request: Different model for different features #135

ponpat opened this issue Feb 18, 2025 · 3 comments

Comments

@ponpat
Copy link

ponpat commented Feb 18, 2025

As a versatile WritingTools user I want to be able to set different models for different features, so that I get the best kind of response (faster/less rate limited vs smarter and slower) for the different kinds of behavior like proofreading vs prompting.

Proposed solutions:

  • Expand the new edit and rearrange the feature into a category in the settings and allow an "advanced" edit for the model selection settings. So for example Gemini 2 flash lite could be used for proofreading but "thinking" for prompts and "pro" for "expanding".
@momokrono
Copy link
Collaborator

Hi,
I'm already working on this feature, but for now the idea was to let the user pick the model at runtime instead of tying a model to a particular option.

Basically, when you select some text and trigger the popup, you will be able to select the model to use for that particular request.

The idea of using an extra option field to specify the model, however, can be worth exploring, but this will only help when you're sure you're always going to use that option with that particular model.

I'll keep you updated.

@Lordlorio
Copy link

Hi, I'm already working on this feature, but for now the idea was to let the user pick the model at runtime instead of tying a model to a particular option.

Basically, when you select some text and trigger the popup, you will be able to select the model to use for that particular request.

The idea of using an extra option field to specify the model, however, can be worth exploring, but this will only help when you're sure you're always going to use that option with that particular model.

I'll keep you updated.

Hi, do you have any news about this option?

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