HAMMAD YOUSUF

FREE RESOURCE · FROM THE "ADVISOR" REEL

Claude Code Fable advisor: Opus builds, Fable advises

By · 11 November 2026

Use Opus for the main Claude Code session and Fable as an advisor at decision points. This guide shows the setup, a practical task prompt and the checks that help you avoid mistaking an unavailable advisor for a working one.

Your first run

  1. 1. Update and check the version

    Update Claude Code and confirm the installed version before setting up Fable 5.2. If your installation uses a managed update process, follow that process.

    step 1
    claude update
claude --version

  2. 2. Choose the main model and advisor

    Inside Claude Code, select Opus, then enable Fable as the advisor. Confirm the displayed model versions; aliases can advance with releases. For the reel’s pairing, check Opus 5.5 and Fable 5.2.

    step 2
    /model opus
/advisor fable

  3. 3. Read any billing-consent prompt

    Some plans require one-time consent for Fable usage credits. If directed to /model fable, read the terms and accept only if you agree. That changes the selected model, so select Opus again before enabling the Fable advisor. Do not assume a promotion applies to every account.

  4. 4. Choose whether the setting should persist

    The advisor command normally saves your selection for later sessions. To request the pairing for one session, launch Claude Code with these flags. Confirm the advisor is active after launch.

    step 4
    claude --model opus --advisor fable

  5. 5. Give it a substantial, reviewable task

    Use a real specification and a bounded task with clear verification. Start with a branch or working copy you can review. The model decides when consultation is useful; this is not a second worker independently executing every task.

    step 5
    Implement the changes described in SPEC.md. Read the existing code and tests first. Consult the advisor before committing to the approach, if the same error recurs, and before declaring the work complete. Keep a concise record of the plan, changes and verification. Ask before paid external actions or publishing anything.

  6. 6. Check usage and turn it off when finished

    Review the consultation messages and the session’s usage. Compare against a similar bounded task before deciding whether this pairing is worthwhile for your work.

    step 6
    /usage
/advisor off

Availability, context and the reported comparison

Provider support
The current docs support the Anthropic API, including subscription accounts, and Claude Platform on AWS. AWS support requires 2.1.300+; Fable 5.2 still requires 2.1.321+. Amazon Bedrock, Google Cloud Agent Platform and Microsoft Foundry are excluded.
LLM gateways
With ANTHROPIC_BASE_URL, the gateway must forward the advisor request intact to the Anthropic API. Unsupported gateway or upstream behavior can prevent consultation. Check the actual session status.
Organization and session settings
An allowed model and required feature flag must be available. Settings that disable flag fetching, such as DISABLE_TELEMETRY, may affect non-AWS sessions. Consult the current requirements when the advisor is missing.
Context and billing
The advisor receives conversation context, including tool activity. Its usage adds to the main model’s usage. Check whether your plan uses usage credits before enabling it.
Charlie Hills’s seven-build example
$39.29 with Fable alone versus $25.81 with Opus plus Fable advisor: about 34% less in that experiment. Opus alone was cheaper still. These are Charlie’s reported figures, not Hammad’s tests, a price quote or a guaranteed saving.

Review before real work

  • Confirm version, provider and Fable access before diagnosing the prompt.
  • Verify the main model and advisor displayed by the session, not only the saved setting.
  • Read billing terms and check /usage after a small test.
  • Treat the advisor’s output as guidance; inspect code, tests and results yourself.
  • Avoid sending sensitive context to a model or provider your organization has not approved.

Common questions

Does Fable run on every turn?

No. Claude decides when to consult the advisor. Watch the consultation messages and usage instead of assuming every turn invokes it.

Will this save 34% on my work?

That figure describes Charlie Hills’s supplied experiment. Task complexity, conversation length, model rates and consultation frequency can change your result.

What if the advisor is enabled but never appears?

Check the installed version, provider or gateway, allowed models, billing consent and session feature flags. Read the current official requirements before retrying.

About the video: This guide accompanies Hammad’s ADVISOR reel. The seven-build comparison and demonstration excerpts are attributed to Charlie Hills. They are not Hammad’s own tests. The presenter and voice use Hammad’s approved likeness and clone. Official requirements were checked on 11 November 2026.

Keep going