RPCS3 says "learn to code" as it bans autonomous AI agents from project

3 min read Original article ↗
When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.
The RPCS3 team said that AI is allowed for research purposes, but contributors must "fully own and understand all code they submit."

RPCS3

RPCS3 has updated its guidelines to combat the influx of low-quality, AI-generated code submissions. The new rules demand that contributors fully own and understand any code they submit, even if AI was used for research.

The guidelines update comes just a day after the project made a post on X begging people to "stop submitting AI slop code pull requests to RPCS3," and that there are "plenty of resources online" for people to learn how to properly code and debug instead of generating things they do not understand.

As you can imagine, this post drew some backlash from AI influencers and vibe coders on X, but the project did not seem to care, arguing that it "reached maturity with 70% playable games" several years ago, before LLMs became a thing.

Our guidelines for submitting AI-generated code are now up in our repository!

As for all the AI bros seething on our socials, we're simply blocking you.

Learn how to debug, code, and leave behind something useful to humanity when you're gone, instead of peddling slop. https://t.co/yMtczjXQN1

— RPCS3 (@rpcs3) May 11, 2026

Here are the full guidelines:

Use of AI tools for research and reverse engineering purposes is permitted. However, contributors are expected to fully own and understand all code they submit. Any communication with the team — including code, code comments, and GitHub comments — must come from the human contributor, not an AI agent acting autonomously.

We have unfortunately seen a rise in untested and unverified AI-generated slop being submitted to this project. This wastes maintainer time and, in worse cases, such changes get merged and break functionality for all users. Repeated violations will result in a ban from the repository. Please be respectful of everyone's time.

Pull requests opened by AI agents or automated tools must include a disclosure in the PR description stating the scope of AI involvement — which parts were AI-generated and what human testing or review was performed prior to submission. PRs that omit this disclosure may be closed without review.

If you are unsure about your work, open a discussion issue to talk it through with the team, or reach out to a maintainer on Discord.

RPCS3, for those who do not know, is a super cool open-source emulator for the Sony PlayStation 3. It lets you play PS3 games on Windows, Linux, macOS, and FreeBSD. GitHub, the main home of RPCS3's code, has been facing infrastructure challenges thanks to the huge rise in long-running and resource-heavy "agentic" AI, leading to service disruptions. To manage the situation in the short term, GitHub has made several changes to its Copilot service, including pausing new sign-ups for individual plans and enforcing stricter usage limits.

Earlier this year, cURL shut down its bug bounty program after it was bombarded with what lead developer Daniel Stenberg calls "AI crap". The main issue is that many AI tools lack the necessary context to produce accurate bug reports, which results in a high volume of nonsensical submissions that waste maintainers' time.