Meilisearch, the Rust search engine that also sells AI and hybrid search, published v1.56.0 on Monday. Under “Miscellaneous” sits a policy change first merged on 15 October in PR #6684, “Disallow AI Contributions”, by co-founder and CTO Clément Renault.
What changed
The old rule asked contributors to “transparently disclose any usage of generative AI tooling”, to check generated claims, and to keep generated changes small. The new CONTRIBUTING text reads:
We will not consider any content generated by generative AI tooling (GitHub Copilot, ChatGPT, Claude Code, Cursor, etc.) in external contributions, including: code, tests, documentation, PR descriptions, PR comments, issue descriptions, and issue comments.
The pull request template dropped its “uses generative AI tooling” option. Now a PR “will not be reviewed unless its description contains” a checked line certifying that the code, PR description and PR comments do not use any generative AI tooling.
What it does and does not cover
- External contributions only. The wording is limited to outside contributors. The policy says nothing about how Meilisearch’s own team works.
- Honour system. The only enforcement in the repo is the checkbox.
- One leftover. As of Monday, step 5 of the same CONTRIBUTING file on main still tells contributors who use AI tools to disclose it in the PR description, a line from the old policy that now contradicts the new one.
The same release, AI side
v1.56.0 also changes how indexing treats embedders: Meilisearch now gives up early when an embedding service cannot keep up with a large update or stays unavailable too long, and honours the Retry-After header. Another fix corrects binary quantization state after embedders are deleted.
Meilisearch is one of several projects changing their rules because of AI this month, from Bitcoin Core’s faster fixes for LLM-findable bugs to the r/opensource ban.
The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment