You open Claude Code in a VS Code terminal, select the new Fable 5 model, and suddenly a red error appears.

API Error: 400 tools.18.model: 'claude-opus-4-8' cannot be used as an advisor when the request model is 'claude-fable-5'.

When you first see this message, your brain stalls for a second. Is something wrong with Fable 5? Is my account suspended? Did my billing lapse? Suspicion scatters in every direction.

Bottom line: there is nothing wrong with Fable 5. The real cause is a separate feature called the advisor. This article unpacks what it is and walks you through three ways to fix it in under five minutes.

What Is the Advisor?

Claude Code has had an advisor feature since v2.1.98. The idea is that the main model can consult a stronger model when it hits a difficult decision. For example, if the main model is Sonnet and it runs into a tricky architectural call, it briefly asks Opus for input, incorporates that answer, and then continues working.

Picture a solo developer at a small company who handles everything themselves — but for the really hard calls, they bring in an outside expert. That's the model: handle the day-to-day alone, reach for help only when it counts.

There is one hard rule: the advisor has to be at least as capable as — or stronger than — the model it is advising. As the official Claude Code documentation puts it: "The advisor model must be at least as capable as the request model. If you request an invalid pairing, the API will reject it with a 400 error."

That is exactly what happened here.

'claude-opus-4-8' cannot be used as an advisor when the request model is 'claude-fable-5'.

In plain English: "Opus 4.8 cannot serve as an advisor to Fable 5."

Fable 5 is the newest top-tier model — one tier above Opus 4.8. But Claude Code's advisor is still set to Opus 4.8. A weaker model is trying to advise a stronger one, and the API's response is essentially: "This doesn't add up."

Think of it as a new hire trying to give the CEO strategic advice. The API simply will not accept that combination.

Three Ways to Fix It

Pick whichever option fits your situation.

Option 1. Disable the Advisor (Simplest)

If you want Fable 5 right now and haven't really used the advisor feature, this is the cleanest fix. Inside your Claude Code session, type one command:

/advisor

This disables the advisor immediately, and Fable 5 starts working. Keeping the advisor off by default and enabling it only when you genuinely need it is a perfectly reasonable workflow.

Option 2. Upgrade the Advisor Model to Fable

If you want to keep using the advisor feature alongside Fable 5, just upgrade the advisor itself to Fable. Matching tiers are accepted by the API. Note that Fable does not appear in the default /advisor selection menu, so you will need to type it manually. You will also need Claude Code v2.1.170 or later — update first if you are on an older version.

/advisor fable

claude update

Option 3. Edit the Settings File Directly

If the command approach isn't sticking, or you want a permanent fix, edit the settings file directly. Open:

~/.claude/settings.json

You will find an advisorModel entry. Handle it one of two ways:

  • If you do not plan to use the advisor at all — delete the advisorModel line entirely.
  • If you want to switch to Fable — change the value to "fable".

Save the file and restart your session to apply the change.

One More Trap Worth Knowing

That's really all you need — but there is one more thing worth knowing, because it catches a surprising number of people off-guard.

If fallbackModel is enabled in settings.json, the 400 error above gets silently hidden from you. The moment an advisor conflict occurs, Claude Code automatically switches to a different model (usually Opus), and all you see on screen is something like:

Switched to Opus 4.6 (1M context) because Fable 5 returned an error that could not be retried

This message is what sows the confusion. People think: "Is Fable 5 broken? Do I not have access to it?" The advisor conflict is the real cause — but fallback buries it, so the actual error never surfaces.

If your model keeps switching unexpectedly even after you have fixed the advisor, also check the fallbackModel entry in settings.json. Temporarily removing fallback will surface the real error message and make root-cause diagnosis much easier.

This auto-fallback behavior is a known issue with open bug reports on GitHub. The complaint — that it hides the real cause from users — has been accumulating, and the behavior is likely to be addressed in a future update.

Quick Summary

Here is the whole situation in one sentence:

Fable 5 is perfectly fine. 

The advisor configured in Claude Code (Opus 4.8) is simply weaker than Fable 5, 

so the API refused that pairing.

Here is the fix sequence:

  1. Try first — type /advisor to disable the advisor. Fastest fix.
  2. If that doesn't do it — run claude update to get the latest version, then use /advisor fable to upgrade the advisor to Fable.
  3. If things still seem off — check both advisorModel and fallbackModel in ~/.claude/settings.json.

Follow this sequence and you will have Fable 5 running cleanly in under five minutes.