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

Suggestion: /code mode should use the editor-model instead of the main model #3087

Open
V4G4X opened this issue Jan 31, 2025 · 4 comments
Open

Comments

@V4G4X
Copy link

V4G4X commented Jan 31, 2025

Issue

I use the architect model by default most of the time, and I try to use a reasoning model as the main model and deepseek-chat or sonnet as my editor model.

Many a times, I have a simple instructions to give to the editor model that don't warrant my calling the slow and expensive reasoning models.
I hoped that running /code simple instructions would pass it to the editor model, thinking (code mode and editor sounds synonymous).
But that instruction goes to the main mode (reasoning model) wasting time and money before it went to the editor model.

Thoughts?

Version and model info

No response

@gitkenan
Copy link

As a related point, I would have thought there'd be an easy way to edit the editor-model within the aider session without having to exit aider or change the config file, but I've not found that yet. It'd be a good way to customize further the architect mode.

@kostrse
Copy link

kostrse commented Jan 31, 2025

It would be convenient if the model used in the editing phase of the architect mode and model used in code mode would be either the same thing or they both could be easily switchable in the session.

Or remove the concept of editor model and just use the main model for that?

@devjn
Copy link

devjn commented Feb 7, 2025

Quite often when reasoning model spits out lots of code sonnet 3.5 instead of implementing it too often says something like this: Would you like me to continue with the remaining files? I'll break this into multiple messages to keep it manageable and clear.. And you cannot answer it currently without calling main model.

@gitkenan
Copy link

gitkenan commented Feb 7, 2025

Quite often when reasoning model spits out lots of code sonnet 3.5 instead of implementing it too often says something like this: Would you like me to continue with the remaining files? I'll break this into multiple messages to keep it manageable and clear.. And you cannot answer it currently without calling main model.

You can see my issue for that - you can change the sentence to "please continue to edit the remaining files" and the editor model can take it from there.

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

4 participants