Add Option to Disable Sticky Models in the Settings #3615
Description
What problem does this proposed feature solve?
Problem:
When using Boomerang Mode with multiple Gemini models (via OpenRouter and Google with different API keys), the "sticky models" behavior causes different models and keys to be used throughout a task. This leads to inconsistent behavior and contributes to failed requests, especially given Gemini's unreliability. The inability to opt out of sticky models exacerbates this issue.
Describe the proposed solution in detail
Proposed Solution:
Add a configuration option to disable sticky models in Boomerang Mode, allowing users to enforce a single model (or key) for the entire task unless explicitly changed. This would improve reliability and reduce failed requests caused by model switching.
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
Use Case:
Users relying on multiple Gemini models/keys need consistent model usage during tasks to avoid disruptions, especially when dealing with API unreliability.
Related Issue: #3391 (comment)
Proposal Checklist
- I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
- This proposal is for a specific, actionable change intended for implementation (not a general idea).
- I understand that this proposal requires review and approval before any development work begins.
Are you interested in implementing this feature if approved?
- Yes, I would like to contribute to implementing this feature.