Claude Code and Fable 5 port Command & Conquer to native iOS
Ammaar Reshi used Anthropic's Claude Code and Fable 5 to run Command & Conquer: Generals Zero Hour natively on ARM64.
TL;DR
- 01Ammaar Reshi used Anthropic's Claude Code and Fable 5 to run Command & Conquer: Generals Zero Hour natively on ARM64.
- 02Ammaar Reshi ported "Command & Conquer: Generals Zero Hour" to iPhone and iPad using Anthropic's Claude Code together with Fable 5, producing a native ARM64 build that runs without an emulator.
- 03The build supports campaign, skirmish, and the "Generals Challenge" and translates the game's DirectX 8 graphics pipeline to Apple's Metal API through several intermediate steps.
Ammaar Reshi ported "Command & Conquer: Generals Zero Hour" to iPhone and iPad using Anthropic's Claude Code together with Fable 5, producing a native ARM64 build that runs without an emulator. The build supports campaign, skirmish, and the "Generals Challenge" and translates the game's DirectX 8 graphics pipeline to Apple's Metal API through several intermediate steps.
How did they port it?
The port uses Claude Code and Fable 5 to convert a DirectX 8 Windows game into a native ARM64 iOS binary, translating graphics calls to Metal through intermediate steps. Reshi, Lead Product and Design for Google AI Studio, says the first build took about 40 minutes, followed by "a few hours" of debugging.
Reshi combined Anthropic's Claude Code with Fable 5 to automate large parts of the conversion process. The graphics pipeline specifically performs a translation from DirectX 8 to the Apple Metal API, rather than running the game under an emulator. Reshi documented the process in an engineering log that lists each bug and fix, and he published the full source code on GitHub as open source. Game assets are not included in that repository, so you need your own copy of the game to run the port.
What actually runs and what breaks?
Campaign, skirmish, and the "Generals Challenge" all work with touch controls, but the build can be unstable on some devices because of memory limits. On iPads the game can crash during long sessions because of high memory usage.
Reshi notes the port runs natively on ARM64 with no emulator. That makes the touch controls functional for core modes, though long play sessions on iPad may encounter crashes tied to memory pressure. Reshi also said he spent two days using Claude Code and "burned through his entire Claude Max quota" while iterating on the port. The original game remains the source of assets; Steam sells a copy for about $5 if you want to try the port yourself.
Why did Reshi use a competitor's tool?
Reshi used Anthropic's Claude Code despite his role at Google Deepmind's AI Studio, explaining the choice as a focus on results rather than allegiance. He wrote, "you can love the AI space and respect the competition while still being fully focused on building the best answer. It’s a long game." That line captures why he combined tools from different vendors to complete the port quickly.
Using Claude Code accelerated the initial conversion: Reshi reported the first build took roughly 40 minutes, then a few hours of debugging produced a working native iOS build. The combination of Claude Code and Fable 5 handled much of the translation work, including shader and pipeline conversion, while Reshi tracked and fixed runtime issues via his engineering log.
Why it matters
A native, non-emulated port of a 2003 DirectX 8 PC game to ARM64 iOS shows how modern AI-assisted tooling can compress long porting projects into hours and days rather than weeks. The project demonstrates a practical path for translating old Windows graphics pipelines to Apple Metal, and it exposes the limits still faced on mobile devices: memory usage and runtime stability.
This also highlights how developers are mixing tools from multiple AI vendors to solve engineering problems quickly, and publishing the resulting source code makes the technique reproducible for others who own the original game assets.
What to watch
Check the GitHub repository Reshi published to follow bug fixes and improvements, and watch for updates that address iPad memory crashes. The next concrete signals will be patches that reduce memory usage and commits that document fewer runtime crashes during extended play sessions.
Written by The Brieftide · Source: The Decoder
The Brieftide Daily · 06:00
Briefs like this one, in your inbox every morning.