[BUG] Fable 5 promotional notice compares against "Opus 4.8" - should be Opus 5 (current Opus)

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 3, 2026

Summary

The in-product "Fable 5 is now a standard part of your Max plan" notice compares Fable 5's usage draw-down against Opus 4.8, which is no longer the current Opus model. It should reference Opus 5.

Message text (verbatim, as shown in the Claude Code VS Code extension)

Fable 5 is now a standard part of your Max plan You can use up to 50% of your weekly usage limit on Fable 5. If you hit your limit, you can continue on Fable 5 with usage credits. Fable 5 draws down usage faster than Opus 4.8. Run /model and select Fable to use it. Learn more: https://support.claude.com/en/articles/15424964-claude-fable-5-promotional-access

Why this is stale

  • Opus 5 (claude-opus-5) is the current Opus-tier model; Opus 4.8 (claude-opus-4-8) is previous-generation.
  • Opus 5 is the active model in this session, so the notice compares Fable 5 against a model the user is not running.
  • Opus 5 and Opus 4.8 sit in the same API price tier ($5/$25 per MTok), so the ratio the sentence implies is not wrong, but naming the older model makes the comparison ambiguous. A user on Opus 5 cannot tell whether the line is (a) simply out of date, (b) implying Opus 5 draws down differently from Opus 4.8, or (c) implying they would be switched to 4.8.

Expected

The notice names the current Opus model, i.e. "Fable 5 draws down usage faster than Opus 5", and ideally resolves the model name dynamically so it does not drift again on the next Opus release.

Environment

  • Claude Code VS Code extension, v2.1.220
  • Windows 11 Pro 10.0.26200
  • Plan: Max
  • Active model: Opus 5

Notes

Scope is copy only, no functional impact observed. Filing because the same string will keep going stale on each Opus release unless it reads the current model name.

View original on GitHub ↗