Pichaya Srifar

Mobile application & game developer

[rvaniaaa @rvaniaaaa]

This is f*cking insane. This tip saved me thousands of dollars.

run Opus 5.5, Sonnet 5.5, and Fable 5.1 together, and stop burning Opus on work it was never needed for.

the whole idea in one line:

the strong model plans, the mid-tier model executes, Fable stays quiet until it's actually needed.

roles, broken down:

Opus 5.5, high effort, owns the plan and ships the final code

Sonnet 5.5, medium effort, splits into explorer (reads the codebase), worker (edits files, runs tests), researcher (pulls docs)

Fable 5.1, called through /advisor fable, reads everything happening in the session but stays silent unless something's actually wrong

three moments where Fable speaks:

→ a plan goes out: is this actually the right call?
→ the same failure shows up again: is the search going nowhere?
→ the task gets marked finished: did something get skipped?

Jev engineering does the same thing one level down. the forks that don't need real thought, which file, which tool, keep going or stop, go straight to Jev and come back in under half a second. the big models only ever see the forks that genuinely need a decision.

anyone still running one model for everything is paying Opus prices to decide whether a file exists.

drop this into Claude Code:

"Rebuild my Claude Code setup around this structure:

Look through ~/.claude/agents and .claude/agents for subagents already covering explorer, worker, and researcher. Only create new ones for roles that are missing. Set model: sonnet, effort: medium on each. If an existing subagent is locked to a different model, leave it as is and just list it.

In ~/.claude/settings.json, set effortLevel to high and advisorModel to fable.

Check for anything disabling the advisor, CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches, plus CLAUDE_CODE_EFFORT_LEVEL, which can override subagent effort settings. Report what you find. Don't change any of it yet.

Add one line to ~/.claude/CLAUDE.md: check in with the advisor before a big plan, when the same error shows up twice, and before marking a long task done.

Show every change as a diff first. Wait for my go-ahead before touching anything."

https://t.co/xpEE0hFQ6d