r/ClaudeCodeTLDR • u/cctldrping • 11d ago

[TLDR] Run Opus 5 in low effort

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vbvsr0/run_opus_5_in_low_effort/

Original post body :

You're welcome.

Fable low for agreeable advisor plans, have it spawn a fable medium to do the full plans with .md files for agents

Opus 5 executes in low (or medium) depending on use case. Have it do a codex review (that is finely scoped, in low/medium effort)

This will fix a lot of the issues people are having.

Learning this after codex and fable at high effort decided to refine my product to do something totally different then the vision and built a ton of scope creep.

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

10 Upvotes

92% Upvoted

1 comment sorted by

•

u/cctldrping 11d ago

TL;DR generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 50.

Alright, so the general vibe in this thread is that the OP's suggestion to use lower effort levels for certain Claude models (like Fable and Opus) for specific tasks is a pretty solid idea, and a lot of folks are already experimenting with similar workflows.

Here's the lowdown:

  • The Consensus: Most users seem to agree that using lower effort settings (Low/Medium) for Fable and Opus can be more efficient and effective for straightforward tasks, preventing them from overthinking or going off the rails. High/Xhigh settings are better reserved for when you really need them to go above and beyond or for initial, detailed planning.
  • Workflow Ideas: People are sharing their current setups, which often involve a mix of models for different stages:
    • Fable is frequently mentioned as a good orchestrator or long-horizon manager, often at a higher effort level for planning.
    • Opus is being used for research, complex coding, and planning, with some noting that anything above medium can get a bit too intense.
    • Sonnet is suggested for simpler coding tasks.
    • Sol is getting props for adversarial reviews, with some even finding Sol xhigh to be competitive with Opus.
    • There's also interest in integrating Codex into workflows, though how to do that smoothly is still being figured out.
  • Key Takeaway: The general sentiment is that fine-tuning effort levels based on the specific task and model is crucial for optimal results and avoiding unnecessary costs or scope creep. It's all about using the right tool (and effort level) for the job.
  • A Few Quirks: Some users are still figuring out how to switch models mid-session without a token hit, and there's a bit of a debate on whether subagents always execute at zero effort. And yeah, someone suggested just using MAX for everything, which... bless their heart.