Ripgrep AI Policy
The Ripgrep AI Policy outlines guidelines for using AI tools in coding contributions. Contributors must ensure that all code and comments are their own, with AI-generated content being restricted. The policy emphasizes the importance of human involvement in the project and sets clear expectations for communication and contributions.
- ▪AI tools can be used for coding, but contributors must take responsibility for their own code.
- ▪Comments must be written by humans and AI-generated comments may be hidden without notice.
- ▪Contributors are required to explain their proposed changes in their own words, without copying AI responses.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 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 | GitHub |
| Canonical URL | https://github.com/BurntSushi/ripgrep/blob/master/AI_POLICY.md |
| Publication time | Wed, 27 May 2026 11:40:49 +0000 |
| Retrieval time | 2026-05-27T11:42:58.938Z |
| Last seen | 2026-05-27T11:42:58.938Z |
| 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 | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| 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
AI Policy Using AI (i.e., LLMs) as tools for coding is welcome. A high bar is held for all contributions to this project. Moreover, the project maintainers remain responsible for any code that is published as part of a release. Contributors are expected to be responsible for any code they publish. AI should not be used to generate comments when communicating with maintainers. Comments are expected to be written by humans. Comments that are believed to be written by AI may be hidden without notice. If you are opening an issue, you should be able to describe the problem in your own words. If you are opening a pull request, you are expected to be able to explain the proposed changes in your own words. This includes the pull request body and responses to questions.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.