HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Fable 5.2 Verified
2026-11-13

Demo wall · launch week · checked 2026-11-15

What people built with Claude Fable 5.2

Short answer

Claude Fable 5.2 demos and examples from launch week include games, 3D worlds, physics papers, browser tools, audio experiments, research reconstructions and a prototype operating system. This page curates 45 projects worth opening and links every one to the creator's original work or repository.

Demos at a glance

FieldValue
Projects
45 curated demos
Selected from 165 live works tracked by the community index on 2026-11-15.
Categories
Games 17 · 3D worlds 22 · Science 9 · Systems 5 · Tools 10 · Visual 22 · Audio 2 · Research 2
Tags overlap; one project can sit in more than one category.
What is here
Browser games, 3D scenes, scientific visualisations, audio experiments, research reconstructions and tools
Every card names the creator and links to the original.
Added this round
15 games, worlds, tools, research pages and audio experiments
The community index moved from 133 live works on 13 November to 165 on 2026-11-15.
Evidence rule
Creator claims are labelled; no private benchmark is implied
A live link means the page opened for this review, not that the whole claim was reproduced.
Read
2026-11-15
The original source remains the authority.

How to read the wall: a live link means the demo opened on 2026-11-15. A repository link means the code or write-up is public. Numbers such as hours, tokens, cost or Elo are the creator's claims and are labelled as such; none of them is a benchmark we ran. The community index is a broader, CC0 list; this wall is the subset with enough evidence or novelty to open first.

What this wall does not prove

A good demo is a demonstration, not an evaluation. Several of these pages were made in one long session with no human edits; others were steered and debugged by their creators. The wall says what exists. It cannot tell you how often Fable produces something this good on your task, what the same prompt would do on Opus 5.5, or whether a project will still work next month. The repositories are linked for exactly that reason.

The strongest entries are the ones that show their tests: Earth's data audits, fable-five's test scripts, Formula to Pixel's 24 assertions and Sumi OS's preserved source. One Heartbeat and RoverKit extend that idea into medicine and hardware. That is the difference between a launch-week trick and a result another person can inspect.

Questions about the Fable 5.2 demos

What has been built with Claude Fable 5.2?

The launch week produced playable browser games, 3D scenes, scientific visualisations, audio experiments, research reconstructions, systems experiments and small tools. A community index tracked 165 live works by 2026-11-15. This page curates 45 and links each one to its creator's live work or repository.

Are these Claude Fable 5.2 demos independently verified?

The links and the work exist, but the performance and cost claims are not independently benchmarked here. Hours, token cost, Elo and similar numbers are labelled as the creator's figures. Open the source before quoting them as your own result.

Which Claude Fable 5.2 demo should I open first?

Start with Starry Nightrider for a visual idea turned into a playable world, Saltline for a complete browser shooter, House Bangers for an audio result, One Heartbeat for an inspectable medical explainer, Sumi OS for a systems project that publishes its source, or Formula to Pixel for numerical tests inside one HTML file. The right first click depends on whether you want entertainment, engineering evidence or a reusable pattern.

Were these demos made with one prompt?

Some projects were made in one long session with no human edits; others were steered, debugged or rebuilt by their creators. The card notes say which claim the creator made and where the support ends.

Understand the effort bill Turn a demo into a build recipe Compare with Opus 5.5 Read the full reference

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →