Feature: dynamic model switching by task type

Feature Request: Dynamic Model Switching by Task Type

Problem

Currently, Claude Code uses a single model for the entire session.
Users often want to use a more capable model (e.g., Opus) for coding/implementation
tasks, and a faster/cheaper model (e.g., Sonnet) for queries, planning, or conversation —
but switching requires manual /model commands each time.

Proposed Solution

Allow configuring automatic model switching based on task context, for example:

• Opus → when writing/editing code, running tools, implementing features
• Sonnet → when answering questions, planning, or casual conversation

This could be implemented as:

1. A settings.json config like "modelByTaskType": { "coding": "claude-opus-4-6", "query": "claude-sonnet-4-6" }
2. Or a hook-based mechanism that lets users define rules for model selection

Why This Matters

• Cost efficiency: Sonnet is significantly cheaper for non-coding tasks
• Performance: Opus gives better results for complex implementation
• Workflow: Removes friction of manual /model switching mid-session