What Changed
RPCS3, the open source PlayStation 3 emulator, has updated its stance on AI-assisted code after maintainers became tired of low-quality pull requests from people using automated tools. The team is not saying that every bit of AI help is forbidden. Instead, it wants contributors to be honest about how their code was made, especially when a pull request includes work generated or heavily shaped by an AI system.
In a May 9 post from the RPCS3 account, the project asked people to stop sending poor AI-made code and warned that users who hide AI involvement may be banned. The message also pointed would-be contributors toward learning how to debug and write code themselves, rather than submitting changes they do not understand. For a project as technical as a PS3 emulator, that distinction matters: maintainers need to review changes that affect complex behavior, not untangle mystery code dropped into the queue.
The New Expectation
- Pull requests made by AI agents or automated tools need a clear note in the PR description.
- That note should explain which parts were AI-generated or AI-modified.
- Undisclosed AI-assisted submissions can lead to bans under the updated policy.
Because RPCS3 is open source, anyone can propose changes through pull requests. If the maintainers judge a change to be useful and sound, it can be merged into the main project. The rise of so-called vibe coding has made that process harder for some software teams, because AI can produce code that looks confident at first glance while still being wrong, fragile, or disconnected from how the project actually works. RPCS3’s rule is aimed at making review clearer before that code reaches the emulator itself.
Z-retro’s view: this is a practical middle ground for a preservation-minded project. AI tools may have a place in coding, but emulator work depends on careful testing, clear intent, and trust between contributors and maintainers. Asking for disclosure keeps the door open while protecting the quality of the project.
