-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
1. Why Do You NEED This Feature?
My main model could be a thinking model thats more powerful and expensive and that I want to steer. The research model can be less powerful but fast saving me on tokens.
2. What Is NOT Possible Right Now?
There can only be one model, and it can not be different for sage and muse.
3. What WILL Be Possible With This Feature?
I will be able to use different models for built-in agents
Proposed Solution (User Experience)
Add the following commands:
:config-sage-model
:config-muse-model
:config-forge-model
This should allow us to configure different model+provider configuration for different agent.
NOTE:
We already have a :model and :config-model both of them are only applicable to the active agent. When the user switches their agent, the activated model for that agent should also change.
Alternatives Considered
No response
Use Cases
SAGE can use a much faster model such as MiniMax via openrouter where as FORGE can continue on Opus.
Feature Category
Multi-Agent Workflows
Priority/Impact
High - Would significantly improve my workflow
Examples from Other Tools
No response
Implementation Ideas
No response
Contribution
- I'm willing to submit a PR to implement this feature
- I can help with testing
- I can help with documentation
Additional Context
No response
✅ Pre-submission Checklist
- I have clearly explained WHY I need this feature (not just that it would be nice)
- I have described what is NOT currently possible in detail
- I have explained what WILL be possible with concrete examples
- I have provided specific use cases and workflows
- I have searched existing issues to avoid duplicates