Claude Code lets you configure a primary model plus up to three fallbacks, tried in order when the primary is overloaded or unavailable. Your work keeps moving instead of stopping.
When you rely on a single model, you inherit its bad days. It gets overloaded at peak hours, or a service blips, and your work simply stops — mid-task, no progress, day stalled. That's not a model problem; it's a redundancy problem.
Any system you depend on needs a backup. One option is a hope, not a plan.
Claude Code added a fallbackModel setting: choose a primary, then up to three fallback models tried in order. The --fallback-model flag now applies to interactive sessions too, not just headless runs. It's a one-time configuration that covers you from then on.
Think of it as depth on the bench — you're not betting the whole day on one player staying healthy.
# configure primary + ordered fallbacks claude --fallback-model sonnet-4-6,haiku-4-5 # or set it in config so it always applies
When the primary is overloaded or unavailable, Claude moves to the next model in your list automatically. There's no error wall to clear and no restart — the job continues on the backup. You often won't even notice the handoff happened.
The system absorbs the disruption so your attention doesn't have to.
This is a small feature with an operator's lesson attached: you build the contingency before you need it. Soldiers, pilots, and good engineers all plan for the thing that breaks — not because they expect failure, but because they refuse to be stopped by it.
Set the fallbacks once and you stay operational under load instead of scrambling when it counts.
A copy-paste configuration plus a short decision guide for ordering your primary and backup models.