Why would I want to run this in the browser vs locally?

(I made this port) Fwiw I personally had no reason to do this port beyond using it as a benchmark of the agentic capability of Fable, where something of this shape is IMO a way better gauge than those dumb X.com 'I oneshot game with models X/Y/Z this is how it compares'

I published the actual prompts, and you can see quite clearly that vs Opus which is ok at implementing one big feature, Fable was really able to push through a good chunk of the port. That said it definitely didn't one-shot the port, it also didn't figure out a broken docker sbx sandbox by itself, and also later needed some gaslighting into thinking that the port is not really that hard (by any human measure it was quite hard given the scope of code involved.. The nearly 200MB wasm binary is mostly code afaict..). So there are some clear patterns of how the model was trained and also roughly the scope of task visible in those traces. What I see is that it likes prompts that would take an L4/L5 2-4 weeks to do with Cursor ~2 years ago, more needs some direction and deliberate prompting.

Browser can be local. What’s nice about browser based is that browser based programs can run on every device. Though it sounds like this one requires chrome which seems weird to me.

Probably nice to have for those with low income that only have a Chromebook.

Because then it doesn't matter what you're running locally, as long as you've got a supported browser (Chrome, I'm guessing). It means it doesn't have to make a difference if you have a Window 10 desktop or a MacBook Air or a Chromebook. Go to the web page and look at this CAD.