4 ms·
Assuming /effort max still gets the best performance out of the model (meaning "ULTRATHINK" is still a step below /effort max, and equivalent to /effort high),
by robeym 6mo ago
Assuming /effort max still gets the best performance out of the model (meaning "ULTRATHINK" is still a step below /effort max, and equivalent to /effort high), here is what I landed on when trying to get Opus 4.7 to be at peak performance all the time in ~/.claude/settings.json:
{
"env": {
"CLAUDE_CODE_EFFORT_LEVEL": "max",
"CLAUDE_CODE_DISABLE_BACKGROUND_TASKS": "1"
}
}
The env field in settings.json persists across sessions without needing /effort max every time.
I don't like how unpredictable and low quality sub agents are, so I like to disable them entirely with disable_background_tasks.
- gverrilla 6mo agoSubagents are very useful. But sometimes it uses sonnet or haiku. You can try something like "always use opus for subagents" if you want better subagents.
- robeym 6mo agoNot being able to reliably control subagent model is the main reason I have it off.
- silverwind 6mo agoSeems so silly that they won't support `effortLevel: "max"` while a env var is perfectly fine.
- vinhnx 6mo agoThey do now. /effort command is on the latest Claude Code version; run `claude update` and `claude /effort`.
- silverwind 6mo ago/effort is only per-session though, not persistent.