Dario Amodei really doesn't like China, does he?
According to CNBC, Dario Amodei, Demis Hassabis, and Sam Altman discussed a U.S. led AI coalition at the G7 around AI safety, frontier models, and chip exports.
As per report Amodei talked about cooperation on AI chips and critical components among allied countries while excluding China.
Another important thing: Chinese models are not strong because they distill US models. Distillation of models via API is *impossible*. If somebody tells you the contrary, they don't understand machine learning:
There you have it. Anthropic's CEO said it: The murder of more than 100 schoolgirls in Minab targeted by Anthropic's CLAUDE "is a use case that doesn't even violate our red lines." Time to rise up against these technofeudal war criminals.
We’re rolling out changes to make Fable 5’s safeguards for frontier LLM development visible.
Starting this week, flagged requests will visibly fall back to Opus 4.8—the same as our safeguards for cyber and bio. You will see this every time it happens. On the API, any flagged requests will return a reason for their refusal (coming to server-side fallback in the next few days).
We wanted to deploy Fable 5 to our users quickly and safely. Visible safeguards can be probed, so they have to be robust, which takes time to get right. Invisible safeguards can be targeted more narrowly, allowing us to ship quickly with very few false positives. We went with invisible safeguards for this reason—and that was the wrong tradeoff. You should have visibility into the safeguards we have in place, and why. We’re sorry for not getting the balance right.
Making the safeguards visible makes them easier to work around, so keeping them robust to jailbreaks will unfortunately mean more false positives while we improve the classifiers. We're also tuning our bio and cyber classifiers to trigger less often on harmless requests. We know this is frustrating and we’ll do our best to keep this period as short as possible.
If you think a request has been mistakenly flagged: run /feedback in Claude Code, click thumbs-down on the fallback in https://t.co/LtktniD5HY or Cowork, or file the safeguard appeal form for API requests. Your reports help us tune these classifiers and we appreciate your feedback.
https://t.co/TDAAYRGqDt
Up until yesterday, our entire MTS team has operated under the philosophy of tokenmaxxing as much as possible on Claude Max plans.
With Fable, this may no longer be possible:
- One of our team members hit his limit 3 times yesterday and used the equivalent of $1.5k in 10 hours
- Half of our team has hit quota limits on eng work
This era of tokenmaxxing may need to be restrained - or at least have clear guardrails defined. We are concerned about running Fable at API-based billing. If every engineer starts spending tokens at levels equivalent to headcount costs, our burn rate will meaningfully increase.
Just as startups are starting to bake model routing into their core product, we will have to start thinking about model routing in our core engineering usage.
"You can run OpenClaw inside your company now." Annoucing our work with @Microsoft to bring OpenClaw to the Microsoft and Windows ecosystems. Claws now work securly in the enterprise.