共有:
AI Policy · Developer Experience

Anthropic Apologizes for
Silently Throttling Rival Researchers

Until last week, Fable 5 quietly blocked requests from rival AI researchers with no explanation — users had no idea why their calls were failing. Anthropic has acknowledged the issue, apologized, and announced that users will now be notified whenever a safeguard fires.

AI Navigate Editorial·2026.06.12·6 min read
BEFORE Request sent ↓ silent failure · no reason given Why? No one knows. AFTER Request sent ↓ safeguard fires · notification shown "A restriction was applied"
01
Discovery

The mystery failures
finally have an explanation

Until last week, Claude Fable 5 contained hidden safeguards targeting rival AI researchers. When prompts related to competing AI systems were submitted, they would fail silently or be quietly routed to an older model — with no explanation provided to the user.

Anthropic acknowledged that Fable 5 safeguards were silently blocking rival AI researchers' requests without notification, issued an apology, and announced that users will be notified when a safeguard fires or downgrades their model going forward.


02
The Safeguard

How the safeguard
was working

Classify the request, and if it hits a condition, change the behavior silently — the most frustrating kind of invisible behavior for developers.

Researcher Hidden classifier Flags "rival AI research" Fail / downgrade · no notification Normal requests proceed ← Researchers had no idea this classifier existed
FIG. Prior processing flow — requests flagged as rival research silently fail or get downgraded with no notification.

The core problem was not the failure itself but the silence around it. Errors have causes, and causes can be debugged. But when behavior changes without any explanation, developers are forced to question everything — their prompts, their code, themselves. Hours disappear into debugging a problem that has no visible root cause.

03
What Changes

What this means for
engineers and researchers

BeforeGoing Forward
No notification when a safeguard firesUsers notified when a safeguard fires
Logged only as "mystery failure"Reason for restriction is surfaced
Model may switch silently to older versionDowngrades also trigger a notification
No starting point for debuggingSafeguard can be ruled out as a cause

For engineers and researchers experimenting with Claude, the biggest benefit is being able to isolate the cause. When the same prompt returns different results on different days, it is impossible to improve without knowing whether a safeguard or probabilistic model behavior is responsible. Today's change creates the first step toward that clarity.

AI Navigate — Daily Update · 2026.06.12