live · day 1
live buildstarted 19 nov 2026target 2046


starting fund
that is the whole budget.
dev time
GTA VI took 13.
wanted: bugs
fail a test, gain a star. fix it, lose one.
live feed
the team
Fable's latest model.

GTA VI arrived about 13 years after GTA V. A sequel at that scale is a 20-year job, so we're starting now. Claude writes, runs, tests and fixes GTA VII from an empty repo, funded with $200 in API credits. Everything it thinks and does streams below.

every step claude takes, as it happens. the strip above the terminal shows where it is in the loop. type help in the prompt to poke at it.

claude@gta7 — booting

the gap between big releases keeps growing. if the next one takes twenty years, day one is today.

2013
2026 ~13 years after GTA V, built by a full studio
2026
2046 ~20 years, Claude Fable 5.2, $200 to start

seven phases over twenty years. each one has written goals, deliverables, milestones and exit criteria. open any phase for the full plan.

one model, one repo, one loop, run for twenty years.

01

Every system, from the job scheduler to the radio DJs, is written by Claude Fable 5.2 from an empty repo. No human-written game code.

02

Each change is built and tested before it lands. Failures are logged in the terminal, not hidden.

03

Bugs are found, reasoned through and patched in the open. The wanted level shows how many are loose right now.

roadmap2026 → 2046v1.0 · written 19 nov 2026


This is the full plan for building GTA VII from an empty repository to a released game on 19 November 2046. Each phase lists its goal, what gets built, dated milestones, the criteria for calling it done, the main risks and how the budget is used. Phases overlap slightly so the next one can start while the last is being finished.

phases
duration
team
current

the main focus of every year from first commit to release.

the starting credits cover phase 0 and the first months of the engine. later phases are funded by top-ups.

it's a plan, not a promise.

review

Claude compares progress to the milestones, writes a short report to /docs/reports, and moves dates if the evidence says so.

scope

If a phase runs late, features are cut or deferred before the release date moves. 19 November 2046 is the fixed point.

record

Any change to this roadmap is a commit with a reason. The version number above goes up each time.

documentationv1.0updated 19 nov 2026

Everything about the project: what it is, how Claude works on it, how the code is organised, how money is spent, and how to read what you see on the build page.

start

GTA VII is an open-world game being written entirely by Claude, starting on 19 November 2026 and targeting release on 19 November 2046. It begins from an empty repository with $200 in API credits. There is no studio and no human-written game code: Claude plans the work, writes the code, builds it, tests it, fixes what breaks and commits the result.

The premise is simple. GTA VI arrived roughly thirteen years after GTA V. Each generation of open-world game is bigger than the last, so the next one plausibly takes twenty. If the clock is twenty years, the only sensible time to start is now.

  • Build page: the live terminal, the process strip showing which step Claude is on, and the dashboard of progress, budget and module status.
  • Roadmap: the seven-phase plan from 2026 to 2046, written out in full.
  • Docs: this page.

  1. Small steps. Every change is small enough to build and test in minutes.
  2. Tests before trust. Nothing is merged without a passing test.
  3. Never rewrite what works. Twenty years of budget can't survive repeated rewrites.
  4. Everything in the open. Thinking, failures and fixes are all shown.
start

You don't need to install anything to follow the build.

  1. Open the build page and scroll to the terminal.
  2. Watch the process strip above it. The highlighted step is what Claude is doing right now.
  3. Click into the prompt at the bottom of the terminal and type help.
  4. Try status, budget and modules to see where things stand.
  5. Use pause to hold the feed while you read (it catches up when you resume), and 1x / 2x / 4x to change how fast commands are typed out.
  6. Open the code page to read every file Claude has committed.
  7. Switch the site between light and dark with the button in the top bar, and the terminal on its own with the light / dark button in the terminal bar.
start

The whole team is one model: Claude Fable 5.2, Fable's latest model. It does every job a studio would normally split across departments.

RoleDone byWhat that means here
Engine programmingClaude Fable 5.2Job system, memory, rendering, physics, streaming.
Gameplay programmingClaude Fable 5.2Vehicles, NPCs, police, combat, economy.
ToolsClaude Fable 5.2Command-line tools in place of an editor.
QAClaude Fable 5.2Writing and running tests, soak tests and automated playthroughs.
WritingClaude Fable 5.2Story, missions, dialogue, radio.
ProductionClaude Fable 5.2Quarterly reviews, roadmap updates, budget tracking.

When a newer model is released, the team line is updated and the change is recorded in the decision log.

how it's built

All work happens in one repeating loop. Each pass handles one small task, such as "add tire friction" or "fix the pedestrian pathing bug". The process strip on the build page lights up the current step.

pick
think
write
build
test
fix
commit
StepWhat happens
PickThe next task is taken from the current roadmap phase, smallest useful task first.
ThinkClaude reasons about the task: what exists already, what the simplest correct version is, what could break. This is the italic thinking line in the terminal.
WriteCode and tests are written. Tests for new behaviour usually come first.
BuildThe target is compiled. A failed build goes straight back to Think.
TestThe tests for that target run: basic, load, edge and stress cases.
FixOnly when a test fails. Claude reads the failure, reasons about the cause, patches it and re-runs the tests.
CommitPassing work is committed with a message naming the module and the change.
A task that still fails after two fix attempts is parked: its changes are reverted and it is retried later with fresh context. This stops the budget being spent on one stubborn bug.
how it's built

GTA VII is a single C++ monorepo built with CMake. It has its own engine rather than a licensed one, so every system can be written and tested by Claude end to end.

gta7/
├── CMakeLists.txt
├── README.md
├── docs/
│   ├── decisions/      # one file per architectural decision
│   ├── reports/        # quarterly progress reports
│   └── parked/         # tasks set aside after repeated failures
├── src/
│   ├── engine/core/    # jobs, memory, entities, time
│   ├── render/         # renderer and backends
│   ├── physics/
│   ├── world/stream/   # map, terrain, streaming
│   ├── ai/npc/
│   ├── vehicles/
│   ├── audio/radio/
│   ├── missions/
│   └── online/
├── tests/              # mirrors src/, one suite per module
├── assets/             # source assets and pack rules
└── tools/              # command-line tools in place of an editor

Lower layers never depend on higher ones. This keeps tests fast and lets each layer be finished and frozen in turn.

missions  ──► ai/npc, vehicles, audio/radio
ai/npc    ──► world/stream, physics
vehicles  ──► physics, render
world     ──► render, engine/core
physics   ──► engine/core
render    ──► engine/core
online    ──► everything above, read-only
how it's built

These are the modules shown in the modules card on the build page. Each one has its own tests and its own progress bar.

ModuleResponsible forPhase
repo/scaffoldRepository layout, README, licences, coding standards.0
build/cmakeBuild presets, CI pipeline, sanitizers, packaging.0
engine/coreJob system, fibers, entity component system, memory arenas, time, save games.1
renderGraphics backends, lighting, materials, shadows, sky, weather visuals.1 – 2
physicsCollision, rigid bodies, ragdolls, buoyancy, destruction.1 – 3
world/streamTerrain, roads, districts, interiors, level of detail, streaming.2
ai/npcPedestrians, traffic, police, schedules, reactions to the player.3
vehiclesHandling, damage, sound, cars, bikes, boats and aircraft.3
audio/radioMixing, music stems, radio stations, DJs and ads.3 – 4
missionsScripting, checkpoints, cutscenes, dialogue, heists.4
onlineServers, sessions, persistence, co-op, anti-cheat.5
how it's built

Every commit is built and tested automatically. A commit that breaks any test is reverted.

Test typeWhat it checksWhen it runs
BasicThe feature does what it should in the normal case.Every commit
LoadIt still works with many instances at once.Every commit
EdgeBoundary cases: zero, maximum, empty, overlapping.Every commit
StressLong runs and random input to shake out crashes.Every commit, short; nightly, long
PerformanceFrame time stays within its budget (16.6 ms for 60 fps).Every commit
DeterminismRecorded replays play back identically, frame for frame.Nightly
SoakClaude drives and plays through the world for hours.Nightly, from Phase 3
PlaythroughEvery mission is completed automatically.Weekly, from Phase 4

In the terminal, test results appear as [PASS] or [FAIL] followed by the test name and either its run time or the reason it failed.

how it's built

  1. Found. A test fails. The wanted level goes up one star.
  2. Diagnosed. Claude reads the failure and writes its reasoning as a thinking line.
  3. Patched. A patch line shows the file, line and size of the change.
  4. Verified. The same tests re-run and pass. The wanted level drops one star.
  5. Committed. The fix is committed with a message starting fix.
  6. Regression test. The failing case is kept in the suite so it can't come back unnoticed.
money

The project starts with $200 in API credits. Every call Claude makes costs tokens, and the budget card on the build page tracks real spend against that $200, worked out from the token counts the API returns.

  • Each task logs its token count and cost in the terminal, on the dim line after the commit.
  • The api budget card shows total spent, percentage of the $200 used and total tokens.
  • Type budget in the terminal for spent, remaining and a bar.

The starting credits cover Phase 0 and the first months of Phase 1. The breakdown is on the roadmap page.

Later phases are funded by top-ups. Spend slows as the budget runs down, so the remaining credits always go to the highest-priority work.

money

With a small budget and a long timeline, the most expensive mistake is spending money going in circles. These rules prevent that.

GuardrailRule
Task capEach task has a maximum dollar cost. Reaching it parks the task.
Retry limitTwo failed fix attempts park the task and revert its changes.
Hard stopWhen the total budget is spent, the loop stops until it is topped up.
SandboxGenerated code is compiled and run with time and memory limits, in an empty folder.
the site

Each kind of line has its own colour so you can scan the feed quickly.

LineExampleMeaning
Thinkingthinking Tests first...Claude's reasoning before it acts.
Command$ ctest -R ...A command Claude runs.
Writewrite src/...Files being written and how many lines.
Pass[PASS] ...A test passed.
Fail[FAIL] ...A test failed, with the reason.
Patchpatch src/...A fix: file, line, lines added and removed.
Commit[main 3f9a1c2] ...Work committed to the main branch.
Costtokens +12.4k ...Tokens used by the task and total spend.

ButtonWhat it does
light / darkSwitches only the terminal between a light and a dark theme.
pause / resumeStops the feed so you can read, then continues it.
1x / 2x / 4xChanges how fast commands are typed out.
clearClears the screen. The build keeps going.

The feed scrolls automatically. If you scroll up to read, it stays where you are until you scroll back to the bottom.

the site

Type these into the prompt at the bottom of the terminal and press Enter.

CommandOutput
helpLists every command.
statusCurrent day, progress, current task and counters.
budgetSpent, remaining, tokens and a budget bar.
etaRelease date and time remaining.
modulesProgress bar for every engine module.
roadmapThe seven phases and which one is running.
teamWho is building the game.
wantedCurrent wanted level and open bugs.
lsTop-level files in the repo.
logThe latest real commits.
filesEvery source file and its line count.
cat <path>Prints a file from the repo.
theme light / theme darkSwitches the terminal theme.
pause / resumeStops or restarts the feed.
speed 1 / 2 / 4Sets the feed speed.
docsOpens this documentation.
aboutA short description of the project.
clearClears the screen.
the site

Every number on the build page, and how it's worked out. Counters are real. They come straight from the build server: every token is counted from the API response, every line from the git repo, every pass and fail from an actual compiled test run.

MetricDefinition
Progress to shipTime elapsed since the first commit as a share of the 20 years to release.
ElapsedDays, hours, minutes and seconds since the first commit.
Time to releaseCountdown to 19 November 2046.
API budgetCredits spent out of the starting $200, with total tokens.
Lines writtenLines of C++ and tests in the repo right now.
Tests passedTotal passing test cases across every real test run.
Bugs fixedFailures that were patched and verified.
Wanted levelFailures that are still being worked on, zero to five stars.
ModulesFeatures committed against the planned backlog for that module.
the site

A nod to the game itself. Every failing test adds a star; every verified fix removes one. Five stars means five bugs are loose at once.

StarsMeaning
0Clean. Everything passes.
1 – 2Normal. Claude is fixing something.
3 – 4Busy. Several failures at once, usually after a big change.
5Maximum heat. New features pause until the count comes down.
the site

There are two separate switches.

  • Site theme: the button in the top bar switches the whole site between light and dark.
  • Terminal theme: the light / dark button in the terminal bar, or theme light and theme dark, switches only the terminal. You can have a dark terminal on a light page, or the other way round.

Both choices are remembered in your browser for next time.

more

Is this an official GTA game?

No. GTA VII is an independent fan project. It has no connection to Rockstar Games or Take-Two Interactive.

Why twenty years?

GTA VI arrived roughly thirteen years after GTA V, and each generation is bigger than the last. Twenty years is the planning estimate for a sequel at that scale.

Why only $200?

To show how far a small, disciplined budget can go when work is done in small tested steps and nothing is rewritten without a reason. Later phases are funded by top-ups.

What happens when the $200 runs out?

Spend slows as the credits run down, so the most important work is done first. Top-ups fund the following phases.

Which model is building it?

Claude Fable 5.2, Fable's latest model. It's the whole team.

Does a human write any code?

No. Claude writes all the game code, tests and tools. People set the direction and fund the work.

Will it be playable before 2046?

Parts of it. The roadmap has playable milestones along the way: a drivable car in 2032, the first full mission in 2038 and a public online load test in 2045.

Can I follow along?

Yes. The build page shows the work as it happens, and the roadmap is updated after every quarterly review.

more

TermMeaning
CIContinuous integration: building and testing every change automatically.
DeterminismThe same inputs always give the same result, so replays match exactly.
ECSEntity component system: game objects are ids with data attached, processed in bulk.
FiberA lightweight task that can pause and resume, used by the job system.
LODLevel of detail: simpler versions of objects used far from the camera.
Parked taskA task set aside after repeated failures, to be retried later.
Soak testA long run, often hours, to find problems that only show up over time.
StreamingLoading parts of the world as you approach them, with no loading screens.
TokenThe unit API usage is measured and billed in.
repositorymainloading

The code

Every file in the GTA VII repo, exactly as Claude committed it. Nothing here is written by a person except the tiny test harness in tests/.

select a file