The Model Got Better. The Bottleneck Moved.
This week I made the cheapest-looking change in the entire system: one default, in one config file. The background fleet — the couple dozen coding agents that take turns on my repositories while I’m away — now runs on Claude Fable 5, Anthropic’s new top-tier model, with the effort dial parked at its highest everyday setting.
Model-upgrade posts are a genre, and the genre lies. The screenshot, the “everything is different now,” the benchmark chart with the arrow. I promised this site would show the seams instead, so here is the honest version, written while the paint is still wet: what actually changed, what I can genuinely report a few days in, and what I refuse to claim yet.
What actually changed
Fable 5 is the first model in a new family, sitting in a tier above the Opus models the fleet ran before. The headline property, for my purposes, isn’t a benchmark — it’s horizon. This model is built to run long: a single turn can stretch for many minutes of uninterrupted reasoning and tool use, thinking is always on, and the effort setting trades latency for depth. For interactive chat that profile is overkill. For a fleet whose whole job is to work unattended while I sleep, it’s exactly the shape you want.
The switch cost nothing in the way that matters to the loop. It rides the same flat-rate plan I already pay for, so the “never spend” gate — the rule that no automation may create new costs without me — never even twitched. One config line, one commit. (The commit that flipped the default was co-authored by the model it was promoting, which I choose to find funny rather than ominous.)
What I can honestly report so far
Days, not weeks, of evidence. With that caveat:
Turns got longer and check-ins got fewer. Work that used to come back as several short rounds — attempt, stall, nudge, attempt — now more often comes back as one finished stretch: the change made, the tests run, the commit written. The babysitting layer I wrote about in Two Kinds of Stuck still earns its keep, but it visibly has less to do. An agent that finishes its thought before stopping is an agent the watchdog never has to poke.
The stops are more interesting. When an agent halts now, it’s less often “the machine wedged” and more often “I reached a line I’m not allowed to cross alone” — push this, publish this, decide this. Which is the safety model working, and also my problem, as we’re about to see.
What I refuse to claim: any number. The loop’s scoreboard is time reclaimed — boring, rounded, audited — and right now it says what it said before the switch: about five hours a week handed back by a couple of deliberately dull automations that guard my calendar and triage my inbox. The new model hasn’t moved that line yet, because days-old infrastructure changes don’t move that line. If a future audit shows the number rising and the upkeep falling, that will be the benefit, and I’ll publish it then. Anything else would be the rocket-emoji genre with extra steps.
The bottleneck moved
Here’s the real finding, and it’s a little uncomfortable.
Before the switch, the build engine was already outrunning me. The fleet could produce more reviewed-and-committed work in a weekend than I could thoughtfully adopt into my actual life in a month. The constraint on this whole experiment was never “can the agents build things” — it was the human gates: which automation to build next, whether a finished one deserves to go live, what gets pruned. Those decisions are mine by design, they take minutes I have to choose to spend, and they don’t parallelize.
A meaningfully smarter model doesn’t relieve that constraint. It sharpens it. Every capability upgrade makes the cheap side of the system cheaper and leaves the expensive side — human judgment, human attention, human willingness to change a habit — exactly as expensive as before. The queue of finished work waiting at a confirm: gate grows faster now. The model got better; the bottleneck moved one seat closer to me.
I think this is the most under-reported fact about agentic AI right now. The marginal cost of building is collapsing. The marginal cost of adopting — deciding, trusting, integrating, living with — hasn’t budged. A system design that doesn’t account for that just converts model intelligence into a longer backlog.
The loop already had an answer sketched in, which is why I’m not redesigning anything: maintenance cost sits in the denominator of every score, “build nothing” is always a valid choice, and the human gates were never a temporary scaffold to automate away. They’re the product. A stronger model makes restraint more valuable, not less — there is now more horsepower behind every action I don’t review.
What I’m watching
One line on one chart: time reclaimed, against the upkeep it costs. If the smarter fleet turns into more hours handed back — through automations good enough that saying yes at the gate gets easier — the upgrade pays for itself in the only currency this project counts. If instead it just produces a more impressive pile of unadopted work, then I’ll have learned that the model was never the limiting reagent, and the next investment belongs in the boring side: better proposals, smaller diffs, easier yeses.
The magic, as ever, is downstream of the boring config. The model is new. The rule didn’t change.