Claude Code optimization: choosing models and effort levels

Anthropic engineer Lidia Halley released a guide on balancing costs between Fable, Opus, and Sonnet. The effort setting is passed as part of the prompt to control planning depth. When debugging at high effort, the model can rewrite its plan on the fly if an initial check yields immediate results.
Halley suggests a simple heuristic: if the model fails, determine if it lacks knowledge or effort. Increase effort for lack of diligence, but switch to a larger model for lack of knowledge. For simple tasks, a smaller model at high effort is often more efficient than a larger one.
Internal tests show that Opus 4.8 at a standard effort level outperforms Opus 4.7 while consuming the same number of tokens.
Up next
Abnormal responds to Anthropic’s trademark lawsuit
Abnormal’s founder says he learned of Anthropic’s July 1 trademark lawsuit from a reporter, despite being a major client. Abnormal argues it was founded in 2018, three years before Anthropic, and that Anthropic holds no trademark for the cybersecurity space.
Related stories
- Anthropic rewrites its context engineering rules for Claude 5
- Claude Code cut over 80% of its system prompt, scores held
- Delete “think carefully” from your Opus 5.5 prompts
- “Verify twice” wastes tokens on Opus 5, Anthropic says
- A hidden system prompt paragraph tells Claude Code to stop asking permission
- Anthropic cut roughly 80% of Claude Code’s system prompt
Comments
No comments yet. Be the first.
Join the conversation
Sign in to leave a comment. It appears after moderation.

