RC Car Game Built With AI in a Month: What the Opus 5.5 Maker Reports and What Remains Unverified

A solo developer posting as u/MacXou34 says they made a full game in less than a month with Claude Opus 5.5, and the project is described as an RC car game. Only two things can be confirmed here: the thread title and the topic. This specimen treats the RC car game built with AI in a month as a claim. It sets the claim beside what outside sources say about the model and compares it with a documented one-day build that shows its working.

What did the maker say they built?

The thread on r/aigamedev is titled "Opus 5.5 is a beast. Made a full game in less than a month." The project is described as an RC car game, made by one person.

The thread's contents could not be retrieved while this article was being written. So these points remain open:

• Which engine or framework the game uses
• Whether it runs in a browser, on desktop or on mobile
• What "full game" covers: tracks, cars, modes, menus, progression
• Whether there is a playable build or a store page
• How the developer worked with the model, and what model access cost

Read the post as a self-report. No outside source has checked the build, the timeline or how much of the work the model did. The project belongs to u/MacXou34. Open the original thread for the maker's own screenshots, footage and replies. This article does not reproduce any of them.

What do outside sources confirm about Opus 5.5?

The model is real and recent. Yahoo Finance reports that Anthropic released Claude Opus 5.5 on September 22, 2026, as the first model in its 5.5 family.

The same article reports:

• Typical workload costs about 40% lower than Opus 5
• Output more than 30% faster
• Availability through cloud platforms including AWS and Google Cloud
• Coding examples such as a legacy HAProxy port from C to Rust in 9.5 hours, and an audit of 200,000 lines of code in under three hours

These figures are secondhand, as the article reports them, and none of them measures game development. The DEV Community post covered below also lists Artificial Analysis Intelligence Index scores for Opus 5.5: 58 at max effort, 56 at xhigh and 54 at high.

For a month-long solo project, cheaper and faster output matters because the developer pays for every iteration. But a lower cost per task tells you nothing about whether a model can make a small car feel good to drive. None of these sources speak to that.

How does it compare with a documented one-day Claude Code game?

In a DEV Community post, author tiagovilasboas describes building Montanha: Zero Day in one day with Opus 5.5 and Claude Code. It is a Mega Man X-style progressive web app (PWA), so it runs in the browser.

The speed is not what makes the post useful. What makes it useful is that the author states the details a reader needs to judge the claim:

1. Cost. The author reports the build used about half of a daily allotment on the usage panel.
2. Setup. The author credits a harness rather than a longer prompt. The harness has guides that shape the model's work before it writes code, and sensors that check the result after the model says it is done.
3. Gaps. The author notes that the in-session playtest missed something, which openly admits the limits of the post's own testing.

Here are the two claims side by side, based only on what each source states or what could be confirmed:

A third claim in the same family is a YouTube video titled "Opus 5.5 Built a Full 3D Game for $55". Its search snippet says a 3D platformer called Go Go Slime was built in under four hours. That video was not reviewed in full, so treat it only as context: claims about Opus 5.5 game builds are piling up faster than anyone is checking them.

What does a month of AI-assisted work probably cover?

What follows is reasoning from the sources, not a report of how u/MacXou34 worked.

If one day with a good harness can produce a playable browser game, a month is roughly thirty times that budget. The extra time most likely goes to the work the sources show models handle worst on their own: feel, content and testing.

RC car games make this sharper because the genre lives or dies on vehicle feel. Acceleration curves, grip, steering response, weight transfer, camera follow and collision response are all numbers a model can write. Whether those numbers feel right only shows when a person picks up a controller and drives. That suggests a few questions specific to this project:

• Did the maker tune handling by hand, or accept the values the model proposed?
• Did the model write custom physics, or set up an engine's built-in vehicle system?
• How were tracks made: by hand, by procedural generation, or with model-written layout code?
• What did the model fail at, and who fixed it?

The closest genre comparison on this site is the vibe coded racing game devlog, six months on. It shows how much of a racer's time goes into iteration after the first playable version.

Questions to ask any "built in a month" claim

1. Hours per day. A month of evenings is a different project from a month of full-time work.
2. Tools. Chat window, Claude Code, an editor connection over MCP, or a mix?
3. Cost. Which subscription tier, or how much token spend?
4. What is unfinished. Missing modes, known bugs, placeholder menus.
5. Art and audio. Did the maker create them, buy them, use free assets, or generate them?
6. Playtesting. Who played it, for how long, and what changed as a result?

Two other specimens on this site show what answers to these questions look like. Poke Party covers a Mario Party-style game made over a month-long AI session. The Claude-built 3D Terraria rebuild counts its chats and sets out where the result falls short. For why human QA still matters, see a 12-year game dev's first AI game.

Can the AI test what it built?

Partly. The Montanha author's own note is the clearest evidence here: the in-session playtest missed something. Sensors in a harness can catch crashes, failed builds and broken game states. They cannot judge whether a turn feels too floaty.

If you want to see how far agent-driven testing can go, this site's test plan for an AI agent playtesting a Godot game sets out what such a setup checks. Handling and feel stay a human job in every source cited here.

Verdict: who should pay attention?

Based on the sources, the Reddit post is evidence of what one solo developer says is possible with a current coding model. It is not proof. It becomes useful evidence once the maker shows the build, the cost and the limits, as the Montanha post does.

Worth following if you are a solo developer deciding whether a small vehicle game fits a one-month scope. The thread may show what a finished project in this genre looks like at that size.

Less useful if you want benchmarks, cost figures or a repeatable workflow. Unless the thread supplies those, the Montanha write-up is the stronger reference.

If you plan a similar build, the setup matters more than the model's name. This site's guide on setting up Claude Code for game development explains how to make a project readable to the agent. That is the same idea the Montanha author credits for their result. For more agent-built projects, browse the coding agents tag and the browser games tag.