LLVM AI Tool Use Policy
The LLVM project has established a policy for the use of AI tools by contributors, requiring a human to be in the loop and review all generated code or text before submission. Contributors are expected to be transparent and label contributions that contain substantial amounts of tool-generated content. The policy aims to ensure that contributions are of high quality and do not extract unnecessary work from project maintainers.
- ▪Contributors must read and review all LLM-generated code or text before submitting it for review.
- ▪The contributor is always the author and is fully accountable for their contributions.
- ▪Using AI tools to fix GitHub issues labelled as 'good first issues' is forbidden.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,983 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Llvm |
| Canonical URL | https://llvm.org/docs/AIToolPolicy.html |
| Publication time | Thu, 30 Jul 2026 23:34:27 +0000 |
| Retrieval time | 2026-07-30T23:47:34.388Z |
| Last seen | 2026-07-30T23:47:34.388Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 7NJnxAl7Tpjl · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
LLVM AI Tool Use Policy# Policy# LLVM’s policy is that contributors can use whatever tools they would like to craft their contributions, but there must be a human in the loop. Contributors must read and review all LLM-generated code or text before they ask other project members to review it. The contributor is always the author and is fully accountable for their contributions. Contributors should be sufficiently confident that the contribution is high enough quality that asking for a review is a good use of scarce maintainer time, and they should be able to answer questions about their work during review.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Llvm.
Discussion
0 commentsMore from Llvm
