[FEATURE] Clearer user-facing communication for access restrictions and restoration status

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When access to a model is suddenly restricted, affected users may have no clear way to understand whether they are impacted, why they are impacted, what scope the restriction applies to, or what they should realistically expect next.

In cases like the recent Fable/Mythos suspension, the public statement and status page provide high-level information, but they do not fully answer the practical questions users have during an interruption:

• who is affected
• whether access restoration is being pursued
• what conditions would need to change for restoration
• what timeline or next update users should expect
• whether there are any account-level or region/nationality-specific differences in impact

This creates confusion and disruption for users who rely on these models for ongoing creative or technical workflows. Even when a restriction is outside Anthropic’s direct control, the current communication flow leaves users without enough actionable clarity.

The problem I want to highlight is not only the restriction itself, but the lack of clear, user-facing communication and restoration guidance during these situations.

Proposed Solution

I would like Anthropic to provide a clearer user-facing incident communication flow for model access restrictions.

Ideally, this would include:

• a dedicated status/update page for access restrictions affecting specific models
• a plain-language summary of who is affected and what the scope is
• clearer explanation of whether restoration is being pursued
• explicit guidance on what users should expect next, including the next planned update even if there is no resolution yet
• account-facing messaging inside the product, so affected users do not have to rely only on external statements
• links to official statements, status updates, and any policy or eligibility information relevant to the restriction

The goal is not to require disclosure of sensitive legal or policy details. The goal is to give users a clearer and more actionable understanding of impact, status, and likely next steps when access changes suddenly.

Alternative Solutions

If a dedicated feature page is too heavy, a smaller solution would still help:

• clearer product banners for affected users
• a structured FAQ attached to status incidents
• a standard update template that always covers scope, expected next update, and restoration status

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

As additional context: I only had access to Fable for a few days, but I found it genuinely remarkable and deeply valuable. I am grateful for that experience.

If this restriction reflects a decision not to compromise on something important under external pressure, I also want to express respect for that choice. That is part of why clearer communication matters so much to affected users.

For reference:

• Official statement: https://www.anthropic.com/news/fable-mythos-access
• Status page: https://status.claude.com/

Related: anthropics/claude-code#68129, anthropics/claude-code#68148