> The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks.
Here's Fable 5, the strongest model. Actually try to use it to harden your code and it turns into Opus 4.8. You have seven days to use it, and only half of that time's worth in actual usage. Enjoy.
Looks like it's going to be a thoroughly frustrating experience, even worse than initial rollout. For subscription users, the situation is almost indistinguishable from the export ban.
I won’t even bother with it if they’ve made it even more frustrating. Instead, I’ve been using a combo of Opus 4.8, GLM 5.2 and DeepSeek v4 Pro. Then I have Opus synthesize and verify the reports from all 3 and make the fixes.
https://news.ycombinator.com/item?id=48466313
Just a code review of my own project. Downgraded to Opus 50% of the time while evaluating the critical I/O and memory safety parts, the exact thing I wanted it to do.
And now it's gonna be even worse.
I expect the strong cybersecurity model to help me strengthen the cybersecurity of my project.
> not allowed to cover security topics
They said it wouldn't be usable for offensive purposes. This is the opposite of that.
The cybersecurity model is Mythos, which was never made publicly available. It is only available to a list of US government approved companies.
> They said it wouldn't be usable for offensive purposes
No, they said Fable would refuse for cybersecurity and offensive purposes. You are conflating Fable with Mythos.
I guess the underlying issue is that there is this model that is very capable, but it's being hobbled because of a fear of abuse. It may well be justified, but for a legitimate user any restriction just makes it a worse product and after all the puffery around how good it is (and some practical experience of how good it is) it's a pretty shit experience. "Here's our best model, no you can't really use it".
That's what I was trying to use it for. Find bugs. Anthropic just refused to let it find the memory safety bugs in my C project.
Fable 5, harden my openssl project. Then you use the diffs/summary to find out what the bug is for your exploit.
This "only super special corporations get the model" nonsense is dividing society into haves and have-nots.
Anthropic was correct in their assessment and early warning of Mythos's capabilities, and they did this rollout pretty well. They were not hype marketing. They were being genuinely cautious and honest.
The Trump admin was largely unreasonable with the sudden export control. (Though not entirely unreasonable.) The export control also had not much to do with Anthropic's pre-release warnings. See: GPT-5.6 currently being held up by the federal government.
So what prevented them from putting in the sort of safeguards they ended up putting in without hyping it for months prior as being so good, it's too dangerous?
If they were truly honest in their beliefs of the potential risks of this model, how would their behavior have differed? I would expect exactly the behavior we see, if they were being honest in their belief.
Also note Dario here saying they shot themselves in the foot commercially with how they handled the rollout of the model - you can tell by his reflexive reaction how ridiculous he considers the accusation: https://youtu.be/v1wZwxY3CMg?t=2103
Instead they choose to hype for months about having a model that's simply 'too dangerous to release'.
In other words, why hype it beforehand instead of just quietly add the safeguards they ended up with anyways and release then?
Honestly, why bother with it? They are effectively just releasing the model in-name, but we just get Opus 4.8.
I think the Fable ban happened because Anthropic was first to release a capable enough model.
They almost definitely mean "you will notice even more false positives during seemingly routine coding/debugging tasks than you did at the initial launch". Which is not surprising, given the ordeal they've been put through. Hopefully it won't be too bad.
The main depressing thing for me is it's now only 7 days on the subscription, and then full API pricing, with no mention of even a plan to bring it back to the subscription in the future. (The initial launch mentioned two weeks of subscription, then API pricing, then a hope to return it back to the subscription not long after.)
What can you use it for? To run a breadth search on Erdos problems?
"In the near term" is doing some heavy lifting.
> The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks.> Fable 5 will be available starting tomorrow, Wednesday, July 1, to users globally on the Claude Platform, Claude.ai, Claude Code, and Claude Cowork. For Pro, Max, Team, and select Enterprise plans,1 Fable 5 will be included for up to 50% of weekly usage limits through July 7, after which it will be available via usage credits. We will re-enable access on AWS, Google Cloud, and Microsoft Foundry as quickly as possible.
Reading the full blog post, I think the summary was just poorly written (because it's hard not to read that sentence like all coding is redirected to Opus).
> The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks. As with all our safeguards, we’ll continue to refine this to better distinguish genuine misuse from legitimate requests and reduce false positives.