--- title: "The Zig project's rationale for their firm anti-AI contribution policy" source_name: "Simon Willison's Weblog" original_url: "https://simonwillison.net/2026/Apr/30/zig-anti-ai/#atom-everything" canonical_url: "https://www.traeai.com/articles/7a46ccd8-ae88-41b6-9d56-9a7385c0ac71" content_type: "article" language: "英文" score: 8.5 tags: ["Zig","开源","AI伦理"] published_at: "2026-04-30T01:24:23+00:00" created_at: "2026-04-30T03:52:02.256993+00:00" --- # The Zig project's rationale for their firm anti-AI contribution policy Canonical URL: https://www.traeai.com/articles/7a46ccd8-ae88-41b6-9d56-9a7385c0ac71 Original source: https://simonwillison.net/2026/Apr/30/zig-anti-ai/#atom-everything ## Summary Zig项目坚持严格的反AI贡献政策，旨在培养长期可靠的贡献者而非追求短期代码质量提升。 ## Key Takeaways - Zig项目禁止使用LLM进行问题、拉取请求及评论的提交。 - Zig重视贡献者的成长超过其单次贡献的价值。 - LLM辅助破坏了通过审查PR来培养新贡献者的过程。 ## Content Title: The Zig project's rationale for their firm anti-AI contribution policy URL Source: http://simonwillison.net/2026/Apr/30/zig-anti-ai/ Published Time: Thu, 30 Apr 2026 03:29:17 GMT Markdown Content: # The Zig project's rationale for their firm anti-AI contribution policy # [Simon Willison’s Weblog](http://simonwillison.net/) [Subscribe](http://simonwillison.net/about/#subscribe) **Sponsored by:** Sonar — Now with SAST + SCA for secure, dependency-aware Agentic Engineering. [SonarQube Advanced Security](https://fandf.co/4bzyODl) 30th April 2026 [Zig](https://ziglang.org/) has one of the most stringent [anti-LLM policies](https://ziglang.org/code-of-conduct/) of any major open source project: > No LLMs for issues. > > > No LLMs for pull requests. > > > No LLMs for comments on the bug tracker, including translation. English is encouraged, but not required. You are welcome to post in your native language and rely on others to have their own translation tools of choice to interpret your words. The most prominent project written in Zig may be the [Bun](https://bun.com/) JavaScript runtime, which was [acquired by Anthropic](https://bun.com/blog/bun-joins-anthropic) in December 2025 and, unsurprisingly, makes heavy use of AI assistance. Bun operates its own fork of Zig, and recently [achieved a 4x performance improvement](https://x.com/bunjavascript/status/2048427636414923250) on Bun compile after adding "parallel semantic analysis and multiple codegen units to the llvm backend". Here's [that code](https://github.com/oven-sh/zig/compare/upgrade-0.15.2%E2%80%A6upgrade-0.15.2-fast). But [@bunjavascript says](https://twitter.com/bunjavascript/status/2048428104893542781): > We do not currently plan to upstream this, as Zig has a strict ban on LLM-authored contributions. In [Contributor Poker and Zig's AI Ban](https://kristoff.it/blog/contributor-poker-and-ai/) ([via Lobste.rs](https://lobste.rs/s/ifcyr1/contributor_poker_zig_s_ai_ban)) Zig Software Foundation VP of Community Loris Cro explains the rationale for this strict ban. It's the best articulation I've seen yet for a blanket ban on LLM-assisted contributions: > In successful open source projects you eventually reach a point where you start getting more PRs than what you’re capable of processing. Given what I mentioned so far, it would make sense to stop accepting imperfect PRs in order to maximize ROI from your work, but that’s not what we do in the Zig project. Instead,**we try our best to help new contributors to get their work in, even if they need some help getting there**. We don’t do this just because it’s the “right” thing to do, but also**because it’s the smart thing to do**. Zig values contributors over their contributions. Each contributor represents an investment by the Zig core team - the primary goal of reviewing and accepting PRs isn't to land new code, it's to help grow new contributors who can become trusted and prolific over time. LLM assistance breaks that completely. It doesn't matter if the LLM helps you submit a _perfect_ PR to Zig - the time the Zig team spends reviewing your work does nothing to help them add new, confident, trustworthy contributors to their overall project. Loris explains the name here: > The reason I call it “contributor poker” is because, just like people say about the actual card game, “you play the person, not the cards”. In contributor poker, you bet on the contributor, not on the contents of their first PR. This makes a lot of sense to me. It relates to an idea I've seen circulating elsewhere: if a PR was mostly written by an LLM, why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem? Posted [30th April 2026](http://simonwillison.net/2026/Apr/30/) at 1:24 am ## Recent articles * [LLM 0.32a0 is a major backwards-compatible refactor](http://simonwillison.net/2026/Apr/29/llm/) - 29th April 2026 * [Tracking the history of the now-deceased OpenAI Microsoft AGI clause](http://simonwillison.net/2026/Apr/27/now-deceased-agi-clause/) - 27th April 2026 * [DeepSeek V4 - almost on the frontier, a fraction of the price](http://simonwillison.net/2026/Apr/24/deepseek-v4/) - 24th April 2026 This is a **note** by Simon Willison, posted on [30th April 2026](http://simonwillison.net/2026/Apr/30/). [javascript 753](http://simonwillison.net/tags/javascript/)[open-source 303](http://simonwillison.net/tags/open-source/)[ai 1991](http://simonwillison.net/tags/ai/)[zig 9](http://simonwillison.net/tags/zig/)[generative-ai 1765](http://simonwillison.net/tags/generative-ai/)[llms 1731](http://simonwillison.net/tags/llms/)[ai-assisted-programming 378](http://simonwillison.net/tags/ai-assisted-programming/)[anthropic 277](http://simonwillison.net/tags/anthropic/)[ai-ethics 295](http://simonwillison.net/tags/ai-ethics/)[bun 4](http://simonwillison.net/tags/bun/) ### Monthly briefing Sponsor me for **$10/month** and get a curated email digest of the month's most important LLM developments. Pay me to send you less! [Sponsor & subscribe](https://github.com/sponsors/simonw/) * [Disclosures](http://simonwillison.net/about/#disclosures) * [Colophon](http://simonwillison.net/about/#about-site) * © * [2002](http://simonwillison.net/2002/) * [2003](http://simonwillison.net/2003/) * [2004](http://simonwillison.net/2004/) * [2005](http://simonwillison.net/2005/) * [2006](http://simonwillison.net/2006/) * [2007](http://simonwillison.net/2007/) * [2008](http://simonwillison.net/2008/) * [2009](http://simonwillison.net/2009/) * [2010](http://simonwillison.net/2010/) * [2011](http://simonwillison.net/2011/) * [2012](http://simonwillison.net/2012/) * [2013](http://simonwillison.net/2013/) * [2014](http://simonwillison.net/2014/) * [2015](http://simonwillison.net/2015/) * [2016](http://simonwillison.net/2016/) * [2017](http://simonwillison.net/2017/) * [2018](http://simonwillison.net/2018/) * [2019](http://simonwillison.net/2019/) * [2020](http://simonwillison.net/2020/) * [2021](http://simonwillison.net/2021/) * [2022](http://simonwillison.net/2022/) * [2023](http://simonwillison.net/2023/) * [2024](http://simonwillison.net/2024/) * [2025](http://simonwillison.net/2025/) * [2026](http://simonwillison.net/2026/)