You fire up Claude Code in the Visual Studio terminal, select the newly released 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'.

Seeing this message for the first time makes your brain freeze for a second. "Is something wrong with Fable 5? Is my account locked? Did billing break?" Suspicion scatters in every direction.

The short answer: there's nothing wrong with Fable 5. The real culprit is a separate feature called the advisor​. This article unpacks what that is and walks through three ways to fix it in five minutes.

What Is an Advisor?

Since v2.1.98, Claude Code has shipped with an advisor feature. The idea is that the main model, when facing a hard decision, consults a stronger model once for a second opinion. For example, if your main model is Sonnet and it runs into a tricky architecture decision, it briefly asks Opus for its take, folds that answer in, and keeps working.

Think of a one-person dev shop at a small company: they handle everything themselves, but when a big decision comes up, they call in an outside expert for a single consult. Business as usual otherwise — help only arrives at the hard moments.

There's one rule here: whoever gives the advice has to be at least as capable as whoever's asking for it. That's straight from Claude Code's official docs: "The advisor must be a model of equal or greater capability than the main model. Requesting an invalid pairing causes the API to reject it with a 400 error."

Which is exactly what just happened.

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

Translated: "Opus 4.8 can't serve as Fable 5's advisor."

Fable 5 is the newest flagship model, a tier above Opus 4.8. But Claude Code's advisor is still set to Opus 4.8. A weaker model trying to advise a stronger one — so the API says "that doesn't make sense" and rejects it.

In plain terms, it's "a new hire trying to give the CEO business advice." The API simply won't accept that pairing.

Three Ways to Fix It

Pick whichever of the three fits your situation.

Fix 1: Turn Off the Advisor (Simplest)

If you want to use Fable 5 right now and haven't really been using the advisor feature anyway, this is the cleanest fix. Inside your Claude Code session, type one line.

/advisor

This command disables the advisor, and Fable 5 works immediately. Leaving the advisor off by default and switching it on only when you actually need it works fine too.

Fix 2: Bump the Advisor Model Up to Fable

If you want to keep using the advisor feature alongside Fable 5, just switch the advisor itself to Fable. Same tier, and the API accepts it. Note that Fable doesn't show up in the default list on the /advisor selection screen, so you'll need to type it in manually. You'll also need Claude Code v2.1.170 or later — update first if you're on an older version.

/advisor fable

claude update

Fix 3: Edit the Settings File Directly

If the slash commands aren't taking effect, or you'd rather lock the setting in permanently, edit the settings file directly. Open the file at this path.

~/.claude/settings.json

You'll find an "advisorModel" entry in there. Handle it one of two ways.

  • If you don't plan to use the advisor at all, delete the entire advisorModel line.
  • If you want to switch to Fable, change the value to "fable".

Save the file and restart the session for the change to take effect.

One More Trap Worth Flagging

You could stop here, but there's one more thing worth knowing — a spot that trips up more people than you'd expect.

If settings.json has fallbackModel turned on, the 400 error above never surfaces to the user at all. The instant the advisor conflict hits, Claude Code silently switches to another model (usually Opus), and all you see on screen is this.

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

This message is what confuses people. It reads like "Is Fable 5 broken?" or "Do I not have permission to use Fable?" In reality, the advisor conflict is the real cause — the fallback just papers over it, hiding the actual problem from view.

If the model keeps switching unexpectedly even after you've sorted out the advisor, check the fallbackModel entry in settings.json too. Temporarily removing the fallback lets the real error surface on screen, which makes tracking down the cause much easier.

This auto-fallback behavior is a known issue that's already been filed as a bug report on GitHub. Complaints that it hides the real cause from users have been piling up, so there's a good chance the behavior gets fixed in a future release.

To Recap

Here's the situation in one line.

Fable 5 is fine. 

Claude Code's configured advisor (Opus 4.8) is just weaker than Fable 5, 

so the API rejects that pairing. That's all this is.

Here's the order to work through the fix.

  1. Try this first — type /advisor to turn off the advisor. Fastest fix.
  2. If that doesn't work — run claude update to make sure you're current, then run /advisor fable to bump the advisor up to Fable.
  3. If it's still acting up — check both advisorModel and fallbackModel in ~/.claude/settings.json.

Follow this sequence and you'll have Fable 5 running normally within five minutes.