I'm not sure if you are aware, but you have to approach prompting Fable slightly differently from a model like Opus.
It's important to include the reason aka the why of your task [1] in your prompt. You'll get more mileage if you verbalize your thought process when prompting Fable. Anthropic say you should think of Fable as a "thought partner".
A Google DeepMind researcher (Neel Nanda) was able to replicate their claims on an open weight model (Qwen 3.6 27B):
> We have replicated the core claims on Qwen 3.6 27B, and also share preliminary evidence of extending this work by finding abstract "interpretative meta-tokens", like Chinese characters for "what does this mean" that seem to activate and play a causal role on processing ambiguous sentences
See p33 of [1]
Anthropic also released companion code to go with their paper in [2] which also used Qwen. They state that their code should be broadly adaptable to other open weight models with HuggingFace decoders.
You are correct. Notwithstanding, people have been expressing the gp's sentiment for like a decade now [1] as is evident in this sub-thread [2], so it's a losing battle trying to prevent people from making such comparisons.
> If I want to speed things up, I remove people from the team. Everything gets easier.
How did you land on this approach? From someone you learned from or from a seminal book like Mythical Man Month [1]?
> This was true long before AI. With AI the difference is just a lot bigger. It exposes team inefficiencies quite mercilessly. We have a big glaring issue with the current AI tools not being to suitable for usage by multiple users. All interactions are one on one. Which means hand offs between tools and people are bottle necked on people communicating with each other. So, any issues there with people delaying, gate keeping, etc. become very visible.
Shopify has also struggled with this and their solution is two-fold: move everything inside a monorepo they call World [2]. The do a number of things to make things legible for AI agents like e.g. having a comprehensive CI/CD system in place, documenting tribal knowledge in AGENTS.md which in aggregate turn out to also be good for humans new to the monorepo.
Then, they built an internal AI agent on top of this monorepo process that is useable from Slack. They call the AI agent River [3] and in this system all chatbot exchanges are public by default.
1: Fred Books was one of the first to point out that adding another team member to speed up a late project will produce the inverse effect of making that project later (because of coordination tax).
For anyone that is confused like I was, the quoted text I'm replying to was copied from page 13 of the system card [1] and not the model announcement page, which this HN discussion is linked to.
Some hard numbers [1] as to why GitHub is struggling with stability issues, directly from GitHub's COO:
Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)
GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week.
So we're pushing incredibly hard on more CPUs, scaling services, and strengthening GitHub’s core features.
Exactly. Nothing hits home about what's about to hit you, now and in the foreseeable future, like when your livelihood today is materially affected by widespread availability of LLMs that can passably mimic your highly specialized skills.
> What do you offer as a solution? If theoretically some foreign state intelligence was exposed using Claude for security penetration that affected the stability of your home government due to Antropic's lax safety controls, are you going to defend Anthropic because their reasoning was to allow everyone to be able to do security research?
I don't have an answer.
But the problem is that with a model like Grok that designed to have fewer safeguards compared to Claude, it is trivially easy to prompt it with: "Grok, fake a driver's license. Make no mistakes."
Back in 2015, someone was able to get past Facebook's real name policy with a photoshopped Passport [1] by claiming to be “Phuc Dat Bich”. The whole thing eventually turned out to be an elaborate prank [2].
Being responsible with powerful technology starts with knowing who is using it. Identity verification helps us prevent abuse, enforce our usage policies, and comply with legal obligations.
We are rolling out identity verification for a few use cases, and you might see a verification prompt when accessing certain capabilities, as part of our routine platform integrity checks, or other safety and compliance measures.