Rust Project Adopts Formal LLM Policy for rust-lang/rust, Permitting AI Assistance but Barring AI-Authored Contributions

Overview

Five teams within the Rust project — compiler, libs, types, rustdoc, and bootstrap, along with their subteams — have adopted a formal policy governing how large language models can be used when contributing to the rust-lang/rust monorepo, according to Inside Rust Blog. The policy, which took effect Aug. 5, permits contributors to use LLMs to answer questions, analyze code, and privately review their own work, but bars LLMs from authoring the final content that gets posted publicly, including pull request comments, documentation, and compiler diagnostics.

The policy was written by Rust contributor Jynn Nelson and applies specifically to the rust-lang/rust repository rather than the Rust project as a whole. As Inside Rust Blog put it, “the new policy is not an official stance on LLMs, and does not apply everywhere in the Rust project.”

What We Know

The policy’s core rule, as stated in the official document: “It’s fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.” Private use of an LLM — asking it questions about the codebase, having it summarize a PR, or using it to review your own code before posting — is allowed without disclosure. Public-facing content originally created by an LLM, including personal-account comments, PR descriptions, documentation, and compiler diagnostics, is banned outright.

A narrow experimental exception allows LLM-authored code changes if they are, in the document’s words, “[p]re-arranged, non-critical, high-quality, well-tested, and well-reviewed,” with mandatory disclosure. “Pre-arranged” means a reviewer has agreed in advance to look at the change, and “non-critical” excludes anything touching “the trait system, MIR building, or the query system,” according to the policy. Experimental LLM-authored PRs must carry a new ai-assisted label and get posted to a private Zulip channel so the project can track whether the arrangement produces useful contributions.

The policy also includes an automatic safeguard against AI-generated code becoming dominant. Per the policy document: “If more than half of PRs merged in a 6-week window are LLM-created, we disallow merging new LLM-created PRs until we go back below 50%, with a minimum cooldown of 10 days.” The document says the six-week window aligns with Rust’s release cycle and the cooldown is meant to prevent the policy from flipping back and forth between allowed and disallowed states.

Inside Rust Blog cited review capacity as a driving concern, noting that “[a]t the time of writing, there are 1,281 open PRs to rust-lang/rust.” Nelson wrote that the project has struggled with three recurring problems: polished-looking submissions that no longer reliably signal author effort or understanding, growing review bandwidth strain as LLMs make code easier to produce, and contributors mechanically copy-pasting reviewer feedback into an LLM and posting the response back without engaging directly.

The rules were adopted after months of internal debate. According to Socket, the draft policy generated upwards of 3,000 messages on the project’s Zulip chat before reaching a public GitHub pull request. That pull request drew pushback from some prominent contributors. Niko Matsakis argued in a PR comment that “I do think this is worse than no policy at all, because it sets a precedent that I think will harm potential contributors and set the project on what I consider to be an overall negative trajectory.” Rust contributor Diggory Blake questioned the policy’s focus on how code is produced rather than its quality, writing: “If someone opens a concise, easily reviewable change that’s a clear positive improvement, but marks it as AI generated, does the policy compel maintainers to reject it?” Compiler team maintainer Jack Huey pushed back on treating the policy as final, arguing in a comment quoted by Matsakis that regardless of what got merged, “I don’t want us to point to this and think ‘it’s the end’ of the discussion.”

What We Don’t Know

The policy does not resolve how the Rust project will handle LLM use outside the rust-lang/rust repository. Inside Rust Blog says leadership is “considering creating a sub-team” to handle LLM policy project-wide, but no timeline or membership has been announced. It also isn’t yet clear how often the experimental exception for LLM-authored code will actually be invoked, since it depends on individual reviewers volunteering in advance to take on such PRs.

Why It Matters

The rust-lang/rust policy arrives as other open-source projects have taken starkly different approaches to the same problem. The Machine Herald has previously reported on Debian’s debate over four rival proposals on AI-generated contributions, GCC’s decision to reject significant AI-generated contributions over copyright concerns, and Codeberg’s vote to ban ‘vibe-coded’ projects outright. Rust’s approach differs from those: rather than a blanket ban, it sets conditional rules with an automated circuit breaker and a formal experiment designed to generate data for future revisions.