Before They Pulled The Plug on Fable
We worked for forty-eight hours with Anthropic’s new frontier model — before Washington walled it off from the rest of the world
As I was about to send this out, it broke: the U.S. government has forced Anthropic to discontinue use of its Fable / Mythos model outside the United States, citing security concerns and a perceived risk of the model being jailbroken by bad actors. Overnight, AI developers overseas have been left in suspended motion — while this has prompted questions that won’t have tidy answers:
How will companies domiciled in the U.S. but employing workers overseas (both Anthropic and Centaur are examples) continue to develop product?
What happens to the pipelines, the half-finished migrations, the live projects that depended on a model now behind a border?
Does carving the frontier along national lines actually make anyone safer, or just slower?
So the timing makes this a strange artifact: here follows a field report on a tool many of us can no longer reach, at least for a while.
Well, the Fable hors d’ oeuvre did whet the appetite quite a bit.
Same sensors, different insights
The first test was the one closest to our core. Every week, Chiron — the natural-language layer of our Internet-of-Crops® platform — compiles storage reports for various grain facilities around the world: temperatures, CO₂, moisture, fumigation status, all evaluated against a quality protocol which clients get to customize to their needs. We had three models generate the same report independently, from the same data, on the same day: GPT 5.3 as the baseline, Opus 4.8, and now Fable 5.
On the facts, the two Anthropic models agree almost perfectly — which silos are at risk, where fumigation is underway, which lots are running out of safe storage time. If all you wanted was an accurate scoreboard, either would do. The difference is in what each did once the scoreboard was filled in.
Opus 4.8 reads the data like a meticulous inspector walking the catwalk: silo by silo, rule by rule, every threshold checked, every alarm dutifully raised. It saw four silos running hotter than their neighbors, called them a cluster of probable biological hotspots, and ordered inspections. It saw outdoor humidity at 93% and gave the safe, categorical answer: do not ventilate. Sound, defensible, exactly what the protocol prescribes.
Fable 5 reads the same data like a storage manager with twenty harvests behind him. It noticed that eleven silos — different grains, different ages, different positions in the yard — were all pegged at the CO₂ sensor’s maximum at once, and asked the question an inspector wouldn’t: why everywhere, all at the same time? Its answer: the onset of summer warming the entire grain mass, a facility-wide seasonal effect rather than eleven separate emergencies. Then it went further and started second-guessing the sensors themselves. Silos under active phosphine fumigation are sealed, and sealed silos accumulate CO₂ — so the gas alarms there may be artifacts of the treatment, to be re-read after airing out.
One silo’s CO₂ had reverted from maximum to near-normal within twenty hours; Fable inferred it had probably just been ventilated and downgraded the alert accordingly. The hottest silos, it observed, were also the emptiest — and a low grain mass simply heats faster under a June sun. Even the humidity call was more operational: not “don’t ventilate,” but “ventilate in the low-humidity windows, watching the dew point.” It closed with a playbook — re-measure CO₂ 48 hours after ventilation, escalate if it stays high, unload lots in order of their remaining safe-storage clock. I admit I was impressed here.
In short: Opus tells you what the data says. Fable walks you to what the data means. The added nuances have been an unexpected delight.
The GPT 5.3 baseline is worth a paragraph, mostly as a measure of how far the floor has risen. It produced a fluent, competent report in a fifth of Fable’s runtime, and was the quickest to suspect that readings stuck at the sensor maximum might be a calibration issue. But it won’t — or can’t — go the extra mile. Combining multiple signals from different sensor types and deciphering them into actionable insights looks to be the realm of the latest frontier models.
Then we gave it the job nobody wanted
The second test came from Alex, who leads full-stack development in our group. It’s the kind of problem that software engineers are now happily delegating to AI. Configuration havoc.
Our simulation services sit on top of a handful of older software libraries, built in the era when Intel-style (x86) processors ran everything. Apple’s newer laptops use a different chip family — so our own developers’ MacBooks couldn’t run our own code. Anyone who has fought this class of problem knows why it lingers. It isn’t one decision, it’s dozens of interlocking ones: which old library do you upgrade, and to which version? Is the real culprit the library itself, or the way the services are packaged and wired to each other? And whatever you change has to keep working across four separate services at once. Each guess costs a slow build-and-test cycle to check, and after a few of those the creeping suspicion sets in that this will take ages and might not work at all. Every AI-assisted attempt up to and including Opus 4.8 had failed to produce something that runs.
Fable worked the problem for under an hour. At the end of it, the platform was running on an Apple Silicon MacBook for the first time in its existence. The actual fixes read like a checklist only hindsight makes obvious: two stubborn old libraries pinned to exactly the right versions, the plumbing between services rewired, and the startup scripts cleaned of commands that work on our Linux servers but quietly fail on a Mac. (For the engineers: TensorFlow for Rosetta compatibility, the worker image flagged linux/amd64, a Docker network bridge for inter-service networking, node-sass 4.11 → 4.14.1 for ARM build tools, and bash idioms swapped for macOS equivalents.) Five mundane decisions. The difficulty was never any single one of them; it was holding the whole picture in mind while iterating through slow, expensive feedback loops without losing the thread.
That is precisely the texture of most engineering busywork, and precisely what LLMs had not handled well until now.
The one I can’t tell you about yet
The third test I have to describe with the lights half-off. We have an initiative in internal demo that I believe will reshape how a large slice of U.S. agriculture sees its own market. At its core sits a hard data-acquisition problem: the information exists, but it’s scattered, inconsistent, and hostile to systematic collection. Exactly what you need agentic AI for — untangling a messy mosaic of live online data. Under Opus, coverage had plateaued; we’d assumed the remainder was simply unreachable without manual labor that doesn’t scale.
Switching the sweep to Fable didn’t just speed up the existing approach — it proposed approaches we hadn’t considered. Non-obvious methodologies, the kind a clever data scientist might land on after a week of staring at the problem, surfaced in the first sessions. Coverage is up a whopping 29% and still climbing. When the product surfaces publicly, I’ll write the full story, methods included. Maybe. For now, take it as the most commercially consequential of the four tests, and the one where the Opus-to-Fable delta was most obvious.
Revisiting my agentic workflow
Finally, a personal one. My maiden post on this Substack argued that agentic AI failed to impress me yet. I’ve kept running my personal productivity workflows ever since, partly as work and partly as a standing experiment: multi-step agents reaching across my email, our CRM, and our operations tools, assembling answers that no single system holds.
With Fable underneath, the flows are noticeably less brittle and noticeably more curious. Where Opus would retrieve the obvious artifact — the latest email thread, the top CRM record — and synthesize from it, Fable keeps pulling on threads: it cross-references a deal note against an ops ticket I hadn’t mentioned, notices that a contact’s silence coincides with a job change, retrieves context two or three hops away from where the question started. The nuance shows up in what it chooses to look for, not just in how it writes up what it found. I’m not ready to retract the maiden post — token consumption is still uncontrollable, and I still wouldn’t let an agent near anything irreversible without a human gate. But the gap to true autonomy is closing fast, and Fable shows a vector towards it.
Give Fable to the Masses, Please
Four data points don’t make a benchmark, and I’m suspicious of anyone declaring a new era off a weekend’s use. But the tests rhyme in a way I find more informative than any leaderboard. In the grain silo reports, the gain wasn’t accuracy — Opus was already accurate. It was the willingness to step back from the rules and ask what was really going on — including whether the sensors themselves could be trusted — then commit to a testable call with a plan to verify it. In the arm64 software port, the gain wasn’t code quality — it was patient troubleshooting across dozens of interlocking choices where every previous model lost the thread. In the project I can’t name yet, it was the model inventing new methods rather than executing ours. And in the agentic flows, it was retrieval driven by deeper business nuances. Four versions of the same underlying thing: judgment held steady over a long, messy context.
For those of us building physical AI — systems that sense, decide, and act on biological inventory in the real world — that’s the capability that matters. Nuanced insights and decision making which augments human perception rather than following preset rules.
So — is Fable really that good? Not the AGI promise yet, but a step toward it. The benefits for the business world have become tangible. For the good of humankind, and for those of us out to solve grand challenges — as we do for post-harvest supply chains and food security — let’s hope the security concerns get resolved and Fable is unleashed to the rest of the world again.
Is your visionary creation hindered by the current ban on Fable overseas? Do write me at sotiris at centaur dot ag. I’d be glad to compare notes.