← Back to context

Comment by bluepeter

3 hours ago

Fable 5 apparently can't be used for coding? (This is from Anthropic's announcement.)

> After a series of productive conversations with the US government, we're redeploying the model with a new set of classifiers to target and block more cybersecurity tasks. In the near term, some routine tasks like coding and debugging will fall back to Opus 4.8.

Edit: the above was from their tweet announcement at https://x.com/AnthropicAI/status/2072163884430229756 ... the associated blog post at https://www.anthropic.com/news/redeploying-fable-5 suggests it was just poorly written and coding can still be done with Fable, just with overeager bouncing of "some routine coding and debugging tasks" to Opus.

Yes, I am pretty sure it was simply poorly worded.

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.)

> 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.

> 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.

  • So fable will jump more often to Opus than it already did on original release? Working with fable felt like having to constantly fight against your work tool. Frustrating. Now they're making it even more frustrating.

  • they might as well not released it at all, what's the point of this theater and artificial scarcity

I wonder if they meant to draw a link between cybersecurity coding and debugging specifically or this really will apply to all coding and debugging. If it really is a more general restriction, then this is practically the same as it still being restricted.

"In the near term" is doing some heavy lifting.

In the press release, they 'kind of' clarify this:

   > The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks.

From the full announcement

> 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.

where did you find that? weird coz their post announcing this also mentioned Claude Code:

> 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.

https://www.anthropic.com/news/redeploying-fable-5