shipped / October 15, 2026

Factory DS: a Factorio-like for the 2004 Nintendo DS, built with Claude Code and tested by agents that play badly

score MHz: 67

Ronan Gaillard ran out of DS games that held their attention, so they built one. Factory DS is a Factorio-style factory game for the Nintendo DS, a 67 MHz handheld with 4 MB of RAM, written with Claude Code by someone who had never coded for the console. Belts, inserters, power grids, pipes, trains with signals, logic gates and a rocket launch, tested headless by around 470 scripted sessions and a team of agents that played it badly on purpose.

Built by Ronan Gaillard with Claude Code.

cnintendo dsclaude codeblocksdslibndsmelondsgamefactorioretrohomebrewembeddedagentsvibe coding

What it is

Factory DS is a factory-building game for the Nintendo DS, the 2004 handheld with a 67 MHz ARM CPU and 4 MB of RAM. If you have played Factorio you know the loop: drills, belts, inserters and furnaces, then power grids, pipes and oil, trains with block signals, and a logic layer of wires, clocks and gates. Around 50 objectives take you from a first wooden log to a rocket launch, then infinite research. All of it on the d-pad and buttons, in English or French.

The world is 2048 by 2048 tiles, which does not fit in 4 MB, so terrain is generated from its coordinates and only your changes are stored. Saves are three 64 KB slots. The ROM is a 1.9 MB download linked from the post, and it runs on a flashcart or in the melonDS emulator.

How it was built

Ronan is an embedded systems engineer in Saint-Malo, France, with a GitHub full of retro computing. The subtitle gives the credit split: "with a lot of help from Claude Code." The opening problem: "I had run out of games that really kept me hooked on it." The fix: "I opened Claude Code and started from there." Ronan had never written code for the DS. They wrote the specs, the machine list, the recipes and ratios, and picked the tilesets and sounds. Claude wrote the C, against the BlocksDS SDK in a Docker container.

The best part is the testing. Every check meant opening an emulator window, so Claude built a headless macOS version against a fake libnds, driven by text commands like press A and step 600, that writes screenshots of both screens. "We ended up with around 470 of them," scripted sessions from cutting a tree to building a signalled train network, all run with the compiler's sanitizers on. "And since Claude can play the game and look at the screenshots, it can check its own work before telling me it's done."

For balance, Ronan asked Claude to launch several agents through that interface, one each on the early objectives, mid-game production, the rocket and infinite research. Then the honest line: "The agents play badly, and where they get stuck a new player probably will too."

The real console runs "about a third slower than the emulator," and a stats screen redrawn every frame made it look like 30 fps. Now it refreshes eight times a second.

Why we picked it

Because the hardware is from 2004 and the workflow is from this month. An agent that plays the game, screenshots both screens and reports where a new player will get stuck, aimed at a console with 4 MB of RAM. Also because "the agents play badly" is the most reassuring QA report we have read all year.


Shipped is Accept All's daily pick of things people build with AI, written by MK. We are not affiliated with Ronan Gaillard; the work and the credit are theirs, so go tell them it's good. Newer: Dub Anything: a coding agent directs a film dub line by line, in the actors' own voices, on your own PC. Older: Brickbrag: a cozy brick builder that turned into a GTA-style city in eight days of Claude Code.