Skip to content

Feature Request: Auto model selection based on task complexity #16620

Description

@yootaebong

Feature Request

Description

Add an "auto" model setting that automatically selects the appropriate model based on task complexity:

  • Use Haiku for simple questions and quick queries
  • Use Sonnet for standard coding tasks
  • Use Opus for complex reasoning and architectural decisions

Current Behavior

Users must manually switch between models using /model commands or configure a single default model in settings. The opusplan setting only switches between plan mode and execution mode, not based on query complexity.

Proposed Behavior

Add a new model setting option:

{
  "model": "auto"
}

When set to "auto", Claude Code would:

  • Analyze the user's query complexity
  • Automatically select the most cost-effective and appropriate model
  • Provide transparency by showing which model was selected (e.g., "Using Haiku for this query")

Use Case

  • Users want to optimize costs by using Haiku for simple queries
  • Users want quality for complex tasks without manual switching
  • Reduces friction in daily workflow

Alternative Solutions Considered

  • Using opusplan - Only switches in plan mode
  • Manual switching with /model - Requires constant user intervention
  • Setting default to Haiku - Sacrifices quality for complex tasks

Benefits

  • Better cost optimization
  • Improved user experience
  • Automatic quality/cost balance

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions