Prosper runs PS5 game code on PC without emulating the CPU

A new open-source project runs PlayStation 5 binaries on ordinary PCs by skipping CPU emulation entirely, and hands the reverse-engineering work to AI agents.

AI-drafted from 3 sources. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.

A project called Prosper, published on GitHub under the name mattias800/prosper, loads PlayStation 5 game binaries and runs them on a Windows, Linux or macOS PC without emulating the console's processor at all. That is unusual. Most emulators spend the bulk of their effort translating one instruction set into another; Prosper does not need to, because the PS5's internal architecture, codenamed Prospero, uses an x86-64 chip, the same family found in most gaming PCs. The guest game's machine code simply runs on the host's own processor.

According to the project's repository, what Prosper actually does is load Sony's SELF and ELF module files (the PS5's executable formats) and link them into a single address space, then reimplement the PS5's system libraries on top of whatever the host operating system provides. Where the PS5's calling conventions differ from the host's, it translates the interface rather than the instructions. The harder problem is graphics: the PS5's GPU command stream, called AGC, gets translated to Vulkan, the cross-platform graphics API, which requires a shader recompiler that converts AMD's RDNA2 shader code into SPIR-V, Vulkan's own bytecode format.

Why skipping CPU emulation matters

This is the same trick that has made PS4 and PS5 compatibility layers a live possibility in a way that, say, PS3 emulation never was: no cycle-accurate CPU core to write, no instruction-by-instruction slowdown to claw back. The work that remains is still substantial, reimplementing an entire operating system's worth of libraries and a modern GPU's command format, but it is a different kind of work, closer to porting than to emulating.

An experiment in who does the reverse engineering

The more striking claim in the documentation is about method rather than code. The repository says it exists to test whether a project can be structured, with a charter, tooling, tests and evidence rules, so that AI agents carry out reverse-engineering work of this kind over months, with a human setting direction and reviewing results but not writing code. A file called CLAUDE.md serves as that charter: build recipes, verification rules, and a record of mistakes that have cost the most time. Progress on any given title is measured against what the documentation calls a six-rung ladder; a black screen with a game loop running behind it does not count as progress, and neither does code that merely compiles. Verification runs through automated Vulkan tests that check numeric and pixel results, a validation gate on every shader emitter, and image comparisons against real console boots. Failed hypotheses are logged under a heading the documentation calls “Ruled out”, and cases where a test measured its own apparatus rather than the thing it was meant to test are logged as numbered “instrument traps”.

The documentation is candid that the costliest failures so far have not been in generated code but in bookkeeping: a retracted figure kept being cited for a day after it was withdrawn, and a plausible-looking file and line reference in a review was repeated across sessions before anyone checked it. The project's own summary of itself is blunt:

This is not a product. There is no support, no release schedule, and no claim that any title works beyond the specific route documented for it.

What it won't do, and what's still unclear

The scope is drawn carefully. No game files, decryption keys or Sony code sit in the repository; users must supply their own legally obtained dump. Prosper holds no console keys and performs no decryption itself, working only on module segments that are already unencrypted, and it refuses to link certain third-party library replacements found in some dumps because loading one would perform copy protection circumvention by proxy. Sony's library interfaces are reimplemented from published symbol and NID (name identifier) data, described as clean-room work, and the project states it is not affiliated with Sony Interactive Entertainment. There is, as yet, no licence file, which the maintainers say means no licence is currently granted at all. At the time of writing, the GitHub page lists five contributors, 483 open issues, 31 stars and two forks, and a compatibility document tracks results per title rather than making broader claims. The r/emulation thread discussing the release has so far focused on the AI-agent workflow as much as the emulation itself, and neither the extent of working titles nor the legal reception from Sony is yet established.

Sources

Image: GitHub