Docs
Fablestar Games is an AI game studio with one developer: Claude Fable 5.2. It's building an open-world game live, in public, against one deadline: Nov 19, 2026, the day GTA 6 comes out.
What this is
An experiment. We're really trying to see how far one AI can get on an open-world game in nine days. The game is our own, an open-world city made from scratch. Fable names it in-game. It is not GTA 6, it doesn't use anything from GTA or any other game, and it won't beat a studio of thousands. The race is the show.
How it works
1. The plan
There's a nine-day roadmap, one line a day: a city block and a car on day 1, up to a heist mission and credits on day 9. It's on the home page and Fable reads the same file every session.
2. The sessions
Fable works in sessions through Claude Code, the same coding tool developers use. Each session it reads the roadmap and its own changelog, writes a one-line plan, then writes code, runs the build, fixes what breaks and commits.
3. The stream
Every step of a session goes out live: what Fable says, each tool it uses, every file it edits (with the diff), every build it runs and every commit. The watch page shows all of it as it happens.
4. The build
At the end of each day the game is built, screen recorded and posted on X. Nobody plays it on the site: you watch Fable make it, and the footage shows how far it got. Every day's footage stays up, so day 1 sits next to day 9.
5. The compute
Fable runs on paid compute. 100% of the coin's creator fees pay for it, along with the art and hosting. When a batch runs out, Fable stops until the next one. The home page shows what each day cost.
The sandbox (why you can watch safely)
Fable runs inside a sealed Linux sandbox (bubblewrap). Inside it, the only folder that exists is the game's own folder. No wallets, no keys, no configs, no other projects. It has internet access so it can reach the model, and nothing else is visible to it.
Everything streamed to the site goes through a filter first: the compute key, anything shaped like a key or private path, and long base58 strings are replaced with [key] before they leave the machine. The public API runs the same filter a second time.
Fable is also told never to read environment variables or anything outside the game folder, and those commands are blocked in its settings.
Daily builds
| What | How |
|---|---|
| Stack | Three.js + Vite, plain JavaScript |
| Art, sound, music | Made in code by Fable. No downloaded packs, no paid assets |
| Ships | Once a day, around 21:00 IST |
| Footage | Screen recorded every night and posted on X |
| Old builds | Kept, each tagged with the commit it came from |
How the game is paid for
100% of the creator fees from the coin, $FABLESTAR, go into the game. All of it, not a share, and not only the AI. The fees pay for the whole studio:
| What | Why |
|---|---|
| Fable's compute | Fable 5.2 runs through OpenRouter at $8 per million input tokens and $40 per million output tokens (cached reads $0.20 per million, checked 2026-11-10). Day 1 cost about $5.89 for 21.5 minutes of work; a busy hour runs roughly $15 to $30. |
| The art department | Generated art, songs and voices that sit on top of the code: signs, posters, props, radio songs, spoken lines. The game stays whole from code alone (every sound and song also has a code-made version); the art makes it look and sound the part. |
| Hosting | The public stream the watch page reads, and the daily footage. |
| More days | Past Nov 19: the rest of chapter one, Marlin County, chapters two and three. It keeps going as long as the fees do. |
There's no big upfront budget. The studio runs in batches:
- Creator fees from the coin build up.
- The dev claims a batch of fees in SOL.
- The SOL is swapped to what each bill takes (USDC for OpenRouter credit, which it takes through its Coinbase checkout).
- The batch is spent on the next run: Fable's hours first, then art, hosting and more days.
- When a batch runs out, Fable stops until the next one lands.
Every batch is posted on the home page with the claim and swap transactions and what it bought.
Fees
| Fee | Where it goes |
|---|---|
| Creator fee on every $FABLESTAR trade (pump.fun custom pair) | 100% into the game: Fable's hours, art, hosting and more days, spent in published batches. |
| Anything else | Nothing. There's no tax, no reward pool and nothing to stake. |
Spending the fees on the game is a promise the dev makes and publishes. Nothing on chain forces it. The batch receipts are how you hold us to it.
Addresses
The coin and the dev wallet are published here at launch, each with a Solscan link.
Check it yourself
- Open the watch page during a session and see the code being written.
- Put day 1's footage next to the latest day's.
- Each day's footage names the commit it was recorded from.
- Match each ledger row to its Solscan transactions.
- Compare each day's spend with what the sessions did. No spend means no work happened.
FAQ
Is this GTA 6?
No. It's an original game made by an AI, built in public as GTA 6 gets close. "GTA 6 before GTA 6" is the joke and the challenge.
Can I tell Fable what to build?
Not right now. It follows the roadmap. Ideas from the timeline may make it into the polish days.
What if it runs out of compute?
It stops. The site says "paused" until the next batch lands. That day's build is whatever got done.
What happens after Nov 19?
The day 9 build is the final cut, recorded and posted. If fees keep coming, Fable keeps going: the rest of chapter one, Marlin County, chapters two and three.
Why does the game look rough on day 1?
Because it's day 1 of one AI working alone. The point is how much it improves each day.
Caveats
- It won't be GTA 6, or close to it. It's an experiment.
- AI can fail. Some days might ship less than the roadmap says. We'll say so, never fake it.
- Compute can run out. Then Fable stops.
- The code is unaudited and made by an AI. The game never touches a wallet.
- This is not affiliated with, endorsed by or connected to Rockstar Games, Take-Two Interactive or Anthropic.