Draft

Add a Second Frontier Model to Claude Code with a Documented Fallback Path

  • Not yet verified
  • Versions not pinned
  • 1 min read

Task

What you will complete

Configure a second model and complete the same task via the fallback after a simulated failure.

Success criteria

  • Claude Code has a second frontier model configured, and the fallback path is written down before the failure is simulated.
  • The primary path fails on purpose, and the documented fallback is the path that then runs.
  • The same task completes on the fallback, with both attempts kept for the evidence section.

What this is not

Not a benchmark of the two models, and not a general introduction to Claude Code.

Prerequisites

  • Claude Code already completing one task on a primary model.
  • Access to a second frontier model you can name in Claude Code's configuration.
  • A way to force the primary path to fail without changing the task.

Environment

Not recorded. A verified revision will list the operating system, the tool builds, and the model identifiers that were present for the run.

1. Name the task the primary model already completes

Choose a task Claude Code already finishes on the primary model. Write the success check in one sentence so the fallback has to meet the same check, not a weaker one.

2. Add the second model

Configure the second frontier model in Claude Code using the mechanism you will document. Write the model ids in your notes. This page will not pin them until the run.

3. Write the fallback path before you need it

Describe, in the order Claude Code will follow, what happens when the primary path fails: the signal you treat as failure, the second model, and how you can tell which model produced the result.

4. Simulate the primary failure

Force the primary path to fail without changing the task. Confirm the fallback you wrote down is the path that actually ran. If a different path ran, the documentation is wrong and the tutorial is not done.

5. Complete the task on the fallback and keep both attempts

Finish the task through the fallback. Save the failed primary attempt, the fallback attempt, the model ids, and the configuration. The evidence section stays empty until those exist.

Evidence it actually ran

This is the shape of the stamp. It has not been earned, and the example date that follows is a placeholder, not a run: Ran on YYYY-MM-DD (Asia/Shanghai) with the pinned versions.

Command output
None recorded. A verified revision will quote the output from the run, not a sample written in advance.
Tests, CI, or Inspector
Not run for this draft.
Repository or config
No link recorded.

Failure modes

Anticipated only. None of these has been checked against a run of this tutorial.

  • Unchecked

    The simulated failure never triggers the fallback

    The primary path can error in a way your notes do not treat as the signal to switch.

  • Unchecked

    The fallback model runs and cannot use the same tools

    A second model that answers in prose while dropping tools has not completed the task.

  • Unchecked

    You cannot tell which model produced the result

    Without a record of the model id on each attempt, the fallback is not documented.

Other tutorials in Integrate.