RPCS3 warns against undisclosed AI pull requests, threatens bans

RPCS3 drew a hard line against undisclosed AI-generated pull requests after warning contributors that repeat violations could lead to bans from the repository. The message landed on May 11, 2026, and quickly caught fire across the emulation scene, pulling in more than 29,000 likes and a flood of discussion.

The policy is not a blanket ban on AI. RPCS3’s guidance says AI tools are still allowed for research and reverse engineering, but anyone submitting code has to fully own and understand it. If an AI agent or automated tool helped produce a pull request, the description now has to spell out what part was AI-generated and what human testing or review was done. Pull requests that leave out that disclosure may be closed without review.

That distinction matters for a project like RPCS3, which is a multi-platform open-source PlayStation 3 emulator and debugger for Windows, Linux, macOS, and FreeBSD. Its goal is accurate PS3 emulation through reverse engineering and community collaboration, a workflow that depends on maintainers being able to trust every line of code that lands. The repository snapshot showed about 18.8k stars and 2.3k forks, a scale that makes every bad submission expensive in time and attention.

The team’s concern is practical, not philosophical. Untested AI code can add regressions, obscure debugging, and force maintainers to spend time untangling changes that the author does not actually understand. In a project where a tiny fix can affect boot behavior, rendering accuracy, controller input, or stability across thousands of game-specific edge cases, that overhead slows down real progress for everyone using the emulator.

RPCS3 also pointed people without coding experience toward a different kind of contribution: testing games and filing bug reports. For an emulator this complex, that kind of hands-on feedback can be more valuable than a polished-looking pull request that nobody can confidently debug. After the warning, the team said it was blocking users who pushed back on the policy, including the “AI bros” it said were reacting negatively.

The message from RPCS3 was blunt, but the goal was simple: protect the quality of the codebase so the emulator stays reliable, accurate, and maintainable for the long haul.