Claude Fable 5 and Mythos 5 restored globally — with a new classifier and new fallback billing
claude-fable-5 and claude-mythos-5 are live again on the Claude API, Claude.ai, Claude Code, and Claude Cowork. Anthropic deployed a new cybersecurity classifier targeting the Amazon-documented jailbreak technique — it blocks that behavior in over 99% of cases. The trade-off: the classifier flags benign requests more often during routine coding and debugging. When Fable 5 refuses a request, it now automatically falls back to claude-opus-4-8 (billed at Opus 4.8 rates) rather than returning an error. Mythos 5 is partially restored for approximately 100 US critical-infrastructure organizations only. Third-party cloud access (AWS Bedrock, Google Cloud, Azure Foundry) is being re-enabled but is not yet live. Usage limits apply through July 7: Pro, Max, Team, and select Enterprise plans are capped at 50% of weekly usage; credits-only after that date.claude-fable-5 is back on the Claude API with a 99%+ jailbreak block rate, but coding/debugging false positives increased and refused requests now silently run on claude-opus-4-8 at Opus 4.8 pricing.usage.model or stop_reason in responses to detect which model actually ran. If you're running automated coding or debugging agents against Fable 5, expect a higher refusal rate than pre-suspension; add handling for stop_reason: "refusal" if you haven't already (see the stop_details.category field for the category — "cyber" vs. null). Do not assume Bedrock/GCP/Foundry access is restored yet — the platform note says "as quickly as possible," not "now." Also: usage credits apply starting July 8, so plan your Fable 5 call volume for the week against the 50% weekly cap.claude-fable-5 or claude-mythos-5 through the Claude API, or you have pending migrations from third-party clouds that were counting on Fable 5 being available there.EffortQuick (model is callable again); Moderate if you need to audit fallback billing and add stop_reason: "refusal" handling for coding pipelines.