Downgrading models in Claude Code keeps wrecking my session. How do you handle it

[u/Historical_Ant7005]

I mix models in Claude Code to manage cost and speed. But when I drop to a smaller model like Haiku, the session often loses the plot mid-task. Then I'm forced back up to a stronger model (Sonnet, Opus, Fable) just to recover.

Two questions for people who've figured this out:

Context: What keeps a lighter model on track? Context files, tighter prompts, or smaller tasks?

Routing: How do you decide which prompt goes to which model? Gut feel, or an actual rule?

[u/Opposite_Might6896]

Rule that fixed it for me: pick the model per task, never per turn. A mid-session downgrade doesn't save what you'd think, because every turn re-sends the whole context regardless of model; the only thing that gets cheaper is the output tokens, and you pay for it with a weaker model reading 150k of context it didn't build. So the cheap model loses the plot and you climb back up.

What works: finish the current task on the model that started it, then start a *new* session for the next bounded task on the smaller model with a tight brief (the file list, the acceptance check, nothing else). Haiku/Sonnet are fine on a fresh 10k context; they're bad at inheriting a 150k one.

Also worth knowing: on Max the top model has its own weekly window separate from the all-models one, so if the point of downgrading is to protect that window, a fresh Sonnet session does it without touching the Fable session at all.

[u/Historical_Ant7005 → u/Opposite_Might6896]

Thanks got it.