It Came Back. Just Not on the Same Terms.

Claude Fable 5 came back at the start of the month, and within the hour I had it pointed at the two most ambitious things I've ever tried to build.

The first is a clone of Wispr Flow - the little ten-dollar-a-month app that turns your voice into text everywhere on your machine - rebuilt as a native Mac and Windows client. The second is stranger. I'm remaking International Karate+, the 1987 fighting game I grew up on, inside Unreal Engine 5 - except I never open Unreal. I sit at this laptop and talk to Claude, which drives the editor on a Windows box in the next room through something called MCP - a protocol that lets a model reach out and operate real software instead of just describing it. We can already prompt a 3D world into being. Next we want the fighters: rigged models, cloth and physics, AI opponents, voice and music from our own pipeline. If it plays, it's the clearest proof I have of what this model can actually do.

I was glad for about an hour. Then I read the fine print on the homecoming.

Fable 5 didn't return the way it left. When the government switched it off in June, it was there one day and gone the next - same model, same deal. When it came back, the deal had changed. It's included for now, but capped at half my weekly limits, with a date hanging over it: after the cutoff, access flips to usage-based credits - you pay per use, metered, the way you pay for electricity, at ten dollars a million words in and fifty out. The waiting message was already sitting in a Claude Code update: you've used your Fable 5 usage for this week.

Here's what I didn't expect: the date won't hold still. The cutoff was July 7. Backlash pushed it to the 12th, then the 19th - each time with the same note, that the metering is temporary and Fable 5 goes back into normal plans once capacity allows. I rushed anyway. Half-limits and a deadline made me greedy, and I burned a week of tokens in two days just seeing what it could do - racing a cliff that then slid twice. I wasn't alone: my feeds filled with five things to do before you lose Fable 5 and one day left or pay thousands, a whole economy of urgency built on a deadline nobody could pin down.

Last time, the lesson I took was that access can vanish - that a vendor can be compelled and your tool is gone overnight. This is the other half of it. Access doesn't only disappear. It comes back on new terms - and sometimes the terms themselves won't sit still long enough to plan around. The meter I've been circling in the expensive-cheap piece and the wheel-credits one stopped being abstract the moment it landed on the one model I actually want to build on.

Losing the tool was one risk. Getting it back on rewritten terms is the one nobody names.

So here I am, building a karate game and a dictation app on a model that's rationed by the week, watching a usage bar the way you watch a fuel gauge on a long drive. I'll keep building - the work is too good to stop, and half-limits still beat the alternative I stared at for those 76 hours. But I build with one eye on the gauge now, and a fallback model warm in the next tab.