Rust repo drafts policy to curb low-effort AI pull requests

What counts as a Rust pull request when an LLM helped write it? The Rust Leadership Council has a draft answer for rust-lang/rust: disclose the machine help, show the work was still understood by a human, and keep low-effort “slop” out of the review queue.

The proposal, opened as issue #273 on March 6, 2026, is aimed squarely at rust-lang/rust first. Maintainers and moderators there say they have seen a significant uptick in AI-adjacent contributions, including issues, comments, and pull requests that were not adequately human-reviewed. The draft says those submissions have become an unsustainably large burden on maintainer and moderation bandwidth, describing the pattern as feeling like a DDoS against maintenance and moderation capacity.

That wording is doing a lot of work. The policy is not written as a ban on AI-assisted coding. Instead, it draws a line between acceptable assistance and “vibecoded” contributions that lack careful self-review. The draft explicitly says it is not intended to block AI-assisted work that has been thoroughly reviewed by the contributor, but it does aim to stop submissions where the author cannot clearly stand behind the patch. In practice, that means contributors sending PRs to rust-lang/rust would need to be upfront about LLM use and able to show they understand the changes they are asking the community to merge.

The scope is deliberately narrow. The council draft says rust-lang/rust is probably the highest-traffic Rust repository and has attracted a disproportionate quantity and frequency of slop contributions. It also says the current compiler-team policy on burdensome PRs does not specifically call out slop and only goes as far as closing a PR, while the moderation team’s spam policy does not clearly cover this exact problem. Other repositories in the rust-lang organization are not in scope, and the document leaves room for a broader Rust-wide AI policy later if the project decides to extend or replace it.

The governance choice matters as much as the wording. The draft would live in Rust Forge as a living document rather than as a dead RFC, and it would be linked from CONTRIBUTING.md in rust-lang/rust as well as from the rustc and std-dev guides. That fits Rust’s existing policy machinery, including its centralized policy index under rust-lang.org/policies, and it follows a community conversation that was already underway on Rust Internals on February 14, 2026 about contributor responsibility and review cost in the age of code generation.

For Rust’s biggest repository, the question is no longer whether AI tools exist. It is whether every PR still arrives with a human who can defend it, explain it, and keep the review queue from drowning in noise.