For coding, Fable 5.1 does what Fable 5 did, and it’s easier to work with while it does it. Dan moved all of his coding tasks over from Codex. Mike sends all of his new projects to it.

Kieran asked it to rebuild Proof from a single prompt—the same test Fable 5 completed in June. Fable 5.1 also built a working version in one shot, but Kieran found it went deeper, adding useful details he hadn’t specified. He also saw more style and better judgment about what worked. As he put it, “What a time to be alive to get this in one shot.”

It also handled his LFG workflow, where the model plans, writes, reviews, and tests without a person in the loop. By the end of the week, he’d updated the compound engineering plugin with instructions tailored to it. “It’s the right balance of having an opinion and getting shit done versus pushing back,” he said.

Dan still uses ChatGPT far more for everyday work, but he’s delegating gigantic coding jobs to Fable 5.1 and letting them run. After he got access, Claude Code was making roughly five times as many requests to the model each day.

Mike asked it to move a blog off Webflow. It did it in one prompt. He then asked it to build a version of Stanford’s AI-town simulation, which follows AI characters through their daily routines to see how they form relationships and spread information. In one shot, it created 25 characters with memories and daily routines, who chatted and spread news about a party and a mayoral race happening in the town. “At this point, I’m not even sure what the model can’t do,” Mike said.

Dan ran security-related coding work that Fable had refused in June, when Fable’s safeguards sent those requests to Opus 4.8. Dan noted that refusals on the basis of security risks are “way down”—the model trusts the human’s judgment more on what does or does not constitute a security risk. Kieran also hit fewer false positives during normal engineering work, whereas Fable 5 sometimes mistook routine coding tasks for security work and blocked them. The one refusal Kieran hit: It wouldn’t log in with a test password during an automated testing loop, which he called “a bit extra.”

As for effort levels, Kieran ran the same kinds of tasks at every effort setting and found that Low, Medium, and High were all “super good.” Extra-high “rips” on long runs but hands off too much work to subagents. He’d rather not pick at all: “I just wish they don’t have effort levels and it will do this automatically.” Most of the team settled on High for work with which they stay in the loop.

This is the first Claude model in a year that the writers on our team want to draft with. It writes clear prose in the right order, and it takes an edit without arguing. Still, it needs a fact-checker on long jobs, it hasn’t displaced Opus 5 in our automated editing pipeline, and whether its style beats GPT-5.6 Sol’s is a matter of taste.

On Every’s writing bench, which tasks models with TK editorial tasks, the new model’s best work was the long-form ones, such as writing an introduction from scratch or filling in a missing section of an essay. On the missing passage assignment, which asks the model to define AI slop from Dan’s essay “After Automation,” it outscored every model we’ve run, Fable 5 included. Its passages used more of the particulars in the surrounding essay, built the argument so that each paragraph made one point, and stayed faithful to the source material where Fable 5 and Opus 5 tended to infer. Fable 5.1 outputs also carried fewer AI tells than any other model’s, and they read at a seventh-grade level, a grade below Fable 5 and two below Sol.

The X post is the one job where it trailed, landing near the bottom, above only Sonnet 5 while Sol led every Anthropic model. The bench has always split along this line: Anthropic models like to extend an argument, GPT models want to compress it. The new model is the strongest extender we’ve tested and a below-average compressor. Its X posts stack a second and third idea where the brief asked for one.

When you kick the effort level up, the model exercises better judgment about what to leave out. High and xHigh scored best. The gap between medium and high was widest on the paragraph-filling assignment, where the model has to read the surrounding argument and decide what belongs in the gap to make the argument complete, and higher settings wrote shorter: The same introduction ran 805 words at Medium and 657 at xHigh. As with previous models, I settled on High as the best option for drafting.

The same instinct that makes it a good drafter makes it a risky reporter. Given a tight brief and set of sources, it’s faithful. But if you give it long source documents and room to elaborate, it can get creative in the wrong ways: Mike asked it to produce a Vibe Check using eight to 12 exact quotes from the Every team. It produced 43 quotes, including several that were missing from the supplied text.

As an editor it’s fast and timid. Jannik had it edit 20 past Every drafts the way Kate Lee, Every’s editor in chief, had edited them. It found Kate’s exact edits about as often as Opus 5 in less than half the time, but threw away about half of what it had found; Opus 5 kept most of its own and Sol nearly all. It can see the edit; it just doesn’t trust itself enough to show you, which is the reverse of its drafting problem. Jannik’s call is that Opus 5 stays the model for that pipeline; Dan’s is that the Fable 5.1 is a little worse and a lot faster.

Give the new model a big consulting assignment and it finishes the whole thing, and on judgment-heavy tasks like slide decks and persona interviews, it beats GPT-5.6 Sol. Give it a brief with a word count, a theme count, or a quote count, and it goes over.

Mike’s EC (executive consulting) Bench covers 12 consulting tasks: dashboards, a training-needs synthesis, a workshop run sheet, a branded slide deck, a roleplayed interview, and others. Sol scored 100 on six of the structured building tasks, then 44 on the blog post and 33 on the roleplayed interview. The new model did the reverse. It scored 88 on persona answers, 93 on the slide deck, and 53 on the roleplay, which Mike still called “basically a fail” but which beat Sol. It lost points where it ignored explicit limits.

Mike asked the model to design three hands-on projects for an executive learning to build with AI, complete with prompts and realistic practice data. One was a dashboard tracking four company acquisitions. The model supplied spreadsheets, status emails, and Slack conversations, including warnings about a project delay that hadn’t yet reached the tracker. In just under 23 minutes, it produced a training pack Mike called “close to perfect.”

Limits are where it loses points. A hotel recommendation with a 1,000-word cap came back at 1,288 words. A training-needs synthesis that called for three to six themes came back with eight. A brief that allowed eight to 12 supporting quotes got 43. A request for markdown got HTML. Opus 5, on the same tasks, stayed inside every limit and timed out twice.

Design is the other weak spot. Mike asked it to build an app that lets people fill out forms by talking to an AI interviewer. The interview worked, but the app had a generic purple-on-black design, large stretches of empty space, and a stray “false” displayed beneath the controls. Fable produced the same purple screen in June. Opus 5 didn’t.

In automated pipelines like Slack assistants designed to execute longform tasks that require tool use, Fable 5.1 does the same work as Opus 5 on about half the tokens and in about 60 percent of the time. Left alone at the highest effort setting, it keeps working, keeps spawning subagents, and doesn’t always stop when you ask. The moral of the story: Set a budget before you start.

Marcus tested both models inside the Every Agent, our Slack-based AI assistant, using internal checks of its writing and ability to complete tasks with tools. Both ran at Medium effort, with instructions originally tuned for Opus 5. Marcus judged the models’ outputs to be comparable, but Fable 5.1 used less than half as many tokens and responded faster. In Jannik’s editing test, it finished in less than half the time of Opus 5.

Marcus’s caveat: Because it acts fast and spends few tokens, it “can perform worse on heavy multi-tool tasks.” If your pipeline needs a model to chain eight tool calls carefully, Opus 5 is still the safer pick.

Kieran ran long tasks at xHigh and found it “extremely thorough, maybe too much, especially delegating to subagents,” and said that “sometimes [it] does ignore me too.” His xHigh sessions “go for like a day at a time.” When he interrupted one to ask, “Can you explain what you’re doing?” he said it “just ignored me and continued to use a billion subagents.” Mike’s exercise pack ran more than twice his normal time. Kieran put 1.8 billion tokens through it in a single day. It is cheap per step and will take as many steps as you let it, and the effort setting is what decides how many that is.

Fable 5.1 is Fable with less waiting and better manners. It’s faster, writes more clearly, uses fewer tokens per step, argues less, and handles long jobs as well as Fable 5 did. Mike moved his new work to it. Dan moved his coding to it. Katie moved her writing to it, two months after deciding Fable wasn’t for her.

Dan and Kieran give it a gold star for the turnaround and the token efficiency. Mike is holding their gold for a price that lets more people afford Fable-grade work, and Anthropic hadn’t shared a price when we filed this piece. Kieran’s caveat on the comeback story: “Fable never sucked.” Anthropic’s bad months were about Fable being unavailable and two other models missing the mark, while GPT-5.6 came out.

Whether this is a 4.5 moment—the kind of release that helps a whole new group of people realize what AI makes possible—or just a very good Fable depends on packaging and pricing decisions Anthropic hadn’t shared as of this writing. Either way, the team is using Claude again.

Disclosure: Anthropic provided Every with pre-launch access to Fable 5.1. The company had no input on this review.