You fire up Claude Code in the Visual Studio terminal, pick the brand-new Fable 5 model, and suddenly a red error fills the screen.

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

The first time you see this message, your brain stalls for a second. "Is something wrong with Fable 5? Is my account blocked? Did a payment fail?" The suspicions scatter in every direction.

Let's start with the bottom line: there is nothing wrong with Fable 5. The real culprit is a separate feature called the advisor​. In this piece, we'll unpack what it is and walk through three ways to fix it in under five minutes.

So what is an advisor?

Claude Code has shipped with an advisor feature since v2.1.98. The idea is simple: when the main model faces a hard decision, it consults a stronger model once. Say your main model is Sonnet and it runs into a thorny architecture call — it briefly asks Opus for an opinion, folds that answer in, and keeps working.

Picture a one-person dev team at a small company calling in an outside expert before a big decision. Most of the time they handle things themselves; they only ask for help at the hard moments.

There's one rule, though. The one giving the advice has to be smarter than the one asking for it. Straight from the official Claude Code documentation: "The advisor must be at least as capable as the main model. Requesting an invalid combination will be rejected by the API with a 400 error."

And that is exactly what just happened.

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

Translated into plain English: "Opus 4.8 cannot serve as Fable 5's advisor."

Fable 5 is the newest top-tier model, one rung above Opus 4.8. But Claude Code's advisor was still set to Opus 4.8. A weaker model was about to give advice to a stronger one, and the API essentially said "that makes no sense" and refused.

Put simply, it's a new hire trying to give the CEO management advice. From the API's point of view, that combination is a non-starter.

Three ways to fix it

Pick whichever of the three fits your situation.

Option 1: Turn the advisor off (the simplest)

If you want Fable 5 right now and you've never used the advisor anyway, this is the cleanest route. Type a single line inside your Claude Code session.

/advisor

Disable the advisor with this command and Fable 5 starts working immediately. Keeping the advisor off by default and switching it on only when you genuinely need it works perfectly well.

Option 2: Upgrade the advisor to Fable

If you want to keep the advisor feature while also using Fable 5, just point the advisor at Fable itself. A same-tier pairing is one the API will accept. One caveat: Fable doesn't show up in the default /advisor picker, so you'll need to type it in manually. You'll also need Claude Code v2.1.170 or later — if you're on an older version, update first.

/advisor fable

claude update

Option 3: Clean it up in the settings file

If the commands don't take, or you want the setting locked in permanently, edit the settings file directly. Open the file at this path.

~/.claude/settings.json

Inside, you'll find an "advisorModel" entry. Handle it one of two ways.

  • If you won't be using the advisor at all, delete the entire advisorModel line.
  • If you're switching it to Fable, change the value to "fable".

Save the file, restart your session, and the change takes effect.

One more trap worth flagging

We could stop here, but there's one more thing you should know — and it's the spot that sends a surprising number of people down the wrong path.

If a fallbackModel setting is enabled in settings.json, the 400 error above gets hidden from view. The moment the advisor conflict occurs, Claude Code automatically switches to another model (usually Opus), and all you see on screen is a message like this.

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

This is the message that throws people off. It plants ideas like "Is Fable 5 broken?" or "Do I not have access to Fable?" In reality the advisor conflict is the true cause, but the fallback papers over it, so the real culprit never comes into view.

If your model keeps switching against your intent even after you've sorted out the advisor, check the fallbackModel entry in settings.json as well. Temporarily removing the fallback lets the real error surface on screen, which makes the root cause far easier to pin down.

This automatic fallback behavior is a known issue, with bug reports already filed on GitHub. Complaints that it hides the real cause from users keep piling up, so there's a good chance the behavior gets refined in an upcoming release.

Once more, the recap

Here's the whole situation in a single line.

Fable 5 is fine. 

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

so the API refused the combination. That's all.

And here's the order of operations.

  1. Try this first — type /advisor to turn the advisor off. It's the fastest fix.
  2. If that doesn't work — run claude update to get on the latest version, then upgrade the advisor with /advisor fable.
  3. If things are still off — check both advisorModel and fallbackModel in ~/.claude/settings.json.

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