-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Choose model for accepted plan for autopilot #2744
Copy link
Copy link
Open
Labels
area:agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsarea:modelsModel selection, availability, switching, rate limits, and model-specific behaviorModel selection, availability, switching, rate limits, and model-specific behavior
Metadata
Metadata
Assignees
Labels
area:agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsarea:modelsModel selection, availability, switching, rate limits, and model-specific behaviorModel selection, availability, switching, rate limits, and model-specific behavior
Type
Fields
Give feedbackNo fields configured for Feature.
Describe the feature or problem you'd like to solve
I frequently plan on a thinking model and prefer a non-thinking one for implementation
Proposed solution
Avoid wasting 3x due to the incredibly convenient default choice :)
The proposed solution would offer (on first run):
Important
On 1. the current model that would be used for autopilot should be clearly shown, since otherwise there's no way to see which one will do the coding
Upon choosing 2., the user would get the same model picker as if they had run
/model. This selection would be persisted as a preference (for going from Plan > Autopilot).Next time they run in plan mode, the options would now be:
Note
Now option 2., just like 1 before, shows the current model being used in plan mode as a fixed choice too for convenience.
In my case, I'd likely choose my desired autopilot model once and then go from Plan > Autopilot without thinking after that.
Example prompts or workflows
No response
Additional context
No response