claude-code - 💡(How to fix) Fix Auto mode: classifier that picks model (Haiku/Sonnet/Opus) and thinking effort per task [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52050Fetched 2026-04-23 07:37:53
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Problem There are now 3 model tiers × 5 thinking-effort levels = 15 combinations. I don't have good intuition for when Sonnet-medium beats Opus-low, or when Haiku is enough. In practice I either over-spend (Opus for everything) or under-spend (Sonnet for something that needed Opus and then re-do it). The mental tax of picking the right config every turn is real.

Proposal An "auto" mode that classifies the incoming task (complexity, breadth, novelty, safety stakes) and picks the model + thinking level for that turn. Show the chosen config in the UI so I can learn from it and override when wrong. Ideally the classifier is itself a cheap Haiku call so it doesn't add meaningful latency/cost.

Why it matters Right now the "which model" decision is a friction tax on every non-trivial turn. Auto mode would remove that tax and also give new users a sensible default instead of making them read model comparison docs.

extent analysis

TL;DR

Implement an "auto" mode that uses a classifier to automatically select the model and thinking level based on task characteristics.

Guidance

  • Develop a classifier that can assess task complexity, breadth, novelty, and safety stakes to determine the optimal model and thinking level combination.
  • Integrate the classifier into the system, using a lightweight model like Haiku to minimize latency and cost.
  • Display the chosen configuration in the UI to allow users to learn from and override the auto mode when necessary.
  • Consider implementing a feedback mechanism to improve the classifier's accuracy over time.

Example

No code snippet is provided as the issue does not contain specific technical details.

Notes

The proposed solution relies on the development of an effective classifier, which may require significant testing and refinement to ensure accurate model selection.

Recommendation

Apply workaround: Implement the proposed "auto" mode with a classifier to simplify model selection and reduce user friction. This approach addresses the core issue of model selection complexity and provides a sensible default for new users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING