The OP believes Sonnet 4.6 medium effort in Claude Code can already handle a large volume of daily and high-intensity tasks; the comment consensus is that simple execution can stay on Sonnet, while complex reasoning, planning, and high-pressure coding still require Opus for architecture first, then hand off to Sonnet for implementation.
Product: Claude Code (post flair: Question about Claude Code).
Configuration: The OP explicitly uses only Sonnet, and never above medium effort.
Comparison: "Larger models" in comments mainly refer to Opus / beast mode, not a controlled A/B.
Sample: Personal workflow + ~80 comments; the mod bot produced a discussion summary.
No public repository, task list, or token bills. The only explicit knob is: model = Sonnet 4.6, effort = medium.
OP: Daily and high-level tasks both completed, never above Sonnet medium; feels that smaller/less "smart" models are cleaner for small daily tasks.
ClaudeAI-mod-bot summary (after 80 comments): The community thinks the OP underestimates complex scenarios; a common workflow is Opus for high-level planning and architecture, then switching to Sonnet to execute well-defined subtasks. Relying on Sonnet alone for complex projects leads to more hallucinations, hidden errors, and a lack of independent thinking; time spent fixing mistakes may exceed the Opus cost savings.
Highly upvoted comments: Emphasize that Reddit is an echo chamber and most real users only use Claude to replace search or for simple tasks; engineers also note that cross-project, hard-to-reproduce issues are not solved by "better prompts alone."
An adjacent post from the same period (r/ClaudeCode, Prior-Meeting1645) discusses an official BrowseComp chart: comments claim Sonnet 5 medium is slightly worse than Sonnet 4.6 medium and cheaper, Sonnet 5 high is slightly better, and xhigh is clearly better but approaches/exceeds Opus pricing. That post body is almost title-only; the scores come from comments reading a chart not expanded in the post body. Treat this only as a clue, not as a BrowseComp raw table.
Sonnet 4.6 + medium is suitable as the default execution tier in Claude Code: daily code changes, small tasks, and already broken-down sub-steps. It is not suitable alone for "big projects not yet thought through." Reusable decisions:
Clear plan and acceptance criteria → Sonnet 4.6 medium.
Need architecture, cross-module reasoning, or high-risk coding → Opus (or a stronger model) plans first, then back to Sonnet.
Do not infer that medium equals a larger model on all engineering problems just because it already "feels fast."
No quantified accuracy, no token table, no blind test.
The mod bot summary smooths dissent; raw comments are more divided.
The OP self-identifies as not the heaviest user but also says they use Claude "deeper than most"; neither claim can be verified.
The BrowseComp chart reading comes from another post's comments, with no original chart or official table; do not upgrade it to an independent review conclusion.
Select 20 tasks with existing plans and 10 unplanned large tasks.
Run two groups on claude-sonnet-4-6 + effort=medium only; for a third group, use Opus first then Sonnet on unplanned tasks.
Record first-pass success, rework rounds, hallucinations/hidden bugs, tokens, and latency.
Use "whether rework eats the Opus savings" as the main economic metric, not a subjective "feels amazing."
Claude Sonnet 4.6
