A Somewhat Abrupt Shutdown
On June 13, Fable 5 (claude-fable-5) became unavailable. From its June 9 release to its removal was just a handful of days—an abnormally fast cadence. The specific reason and follow-up plans are per the official announcement—this kind of sudden takedown usually means either a problem was found that needs handling, or it's making way for a revised version.
An Old Discipline Confirmed Once More
More than asking "why was it stopped," what this time really deserves remembering is that plain engineering discipline: don't weld a critical workflow to a single model. Praised as the strongest flagship days ago, unusable days later; the more aggressively you cut everything over to it on day one back then, the harder the hit now. In the early days after a new model goes live, keeping room to roll back and switch is itself risk control.
For Those Already Integrated, Do This First
Switch your default model back to a stable Claude 4.X immediately (choose among Opus 4.8, Sonnet 4.6, Haiku 4.5 as needed), comb through your code for any hardcoded calls to claude-fable-5 and replace them, and run a round of regression to confirm your core tasks are fine. As for the rest, wait until the official word clarifies the replacement version and migration—don't rush to chase the next "latest"; steady your own pipeline first.