Skip to content

Choose model for accepted plan for autopilot #2744

@kzu

Description

@kzu

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 :)

Image

The proposed solution would offer (on first run):

1. Accept plan and build on autopilot (recommended) - Claude Opus 4.6
2. Accept plan and build on autopilot with another model
3. Exit plan mode and I will prompt myself
4. Suggest changes

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).

Image

Next time they run in plan mode, the options would now be:

1. Accept plan and build on autopilot (recommended) - [LAST SELECTED MODEL]
2. Accept plan and build on autopilot - Claude Opus 4.6
3. Accept plan and build on autopilot with another model 
4. Exit plan mode and I will prompt myself
5. Suggest changes

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsarea:modelsModel selection, availability, switching, rate limits, and model-specific behavior
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions