Draft
Conversation
krissetto
previously approved these changes
Jan 30, 2026
Signed-off-by: David Gageot <david.gageot@docker.com>
krissetto
approved these changes
Feb 3, 2026
|
|
||
| ### When to Consider Switching Models | ||
|
|
||
| **Switch to a faster/cheaper model when:** |
Contributor
There was a problem hiding this comment.
just one thing here.. how is a given model supposed to know what is faster/cheaper or better at some task? should we just rely on the users giving their model definitions reasonable name?
Comment on lines
+25
to
+34
| Use switch_model strategically: | ||
| - For simple tasks (formatting, basic Q&A, summaries), use the faster/cheaper model | ||
| - For complex tasks (code generation, analysis, reasoning), use the more powerful model | ||
| - The switch_model tool description shows available models and which one is current | ||
| - After completing a specialized task, consider switching back to the default model | ||
|
|
||
| Example workflow: | ||
| 1. User asks a simple question -> switch to 'fast' for efficiency | ||
| 2. User asks for complex code -> switch to 'powerful' for quality | ||
| 3. Task complete -> switch back to 'fast' |
Contributor
There was a problem hiding this comment.
do we expect the example work decently even without this extra prompting, given all the instructions included in the tool? if not maybe we can reduce the amount of instructions, to avoid potential conflicts between user prompts and built-in instructions the users don't see?
mostly thinking about context pollution with smaller/local models and conflicting prompts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.