SQLite has added an AGENTS.md file stating it does not accept agentic code but welcomes agentic bug reports with reproducible test cases, and has split AI-generated bug reports into a separate forum.
# sqlite AGENTS.md
Source: [https://simonwillison.net/2026/May/27/sqlite-agents/](https://simonwillison.net/2026/May/27/sqlite-agents/)
27th May 2026 \- Link Blog
**[sqlite AGENTS\.md](https://github.com/sqlite/sqlite/blob/master/AGENTS.md)**\([via](https://discord.com/channels/823971286308356157/1097032579812687943/1507447792598253748)\) SQLite gained an AGENTS\.md file[five days ago](https://github.com/sqlite/sqlite/commit/a1e5778889252d2609a59fd9b819d70392c5789e)\- but it's not intended for their own development, it's presumably aimed at people who are pointing agents at the SQLite codebase\. It includes:
> SQLite does not accept pull requests without prior agreement and/or accompanying legal paperwork that places the pull request in the public domain\. However, the human SQLite developers will review a concise and well\-written pull request as a proof\-of\-concept prior to reimplementing the changes themselves\. SQLite does not accept agentic code\. However the project will accept agentic bug reports that include a reproducible test case\. Patches or pull requests demonstrating a possible fix, for documentation purposes, are welcomed\.
The[most recent commit](https://github.com/sqlite/sqlite/commit/db7fe319ed5a18dbc732ab8eacea557f41cd910f)to that file removed "\(currently\)" from "SQLite does not \(currently\) accept agentic code", with the commit message "Strengthen the statement about not accepting agentic code"\.
Meanwhile the SQLite forum was being flooded with so many AI\-generated bug reports \- of varying quality \- that they've now[split those off](https://sqlite.org/forum/forumpost/2e7a8d6ba4b46d8315e80fd4a1e2feb40948dff5b7b11d5ba9cea5cb40aa252b)into a[new SQLite Bug Forum](https://sqlite.org/bugs/forum)\. D\. Richard Hipp is resolving issues on there with a flurry of commits to the codebase\.
The article proposes that organizations adopting AI coding agents should create a company-wide AGENTS.md file, similar to a human onboarding doc, to standardize agent behavior and context.
Dan Luu reflects on his experiences using AI coding agents, noting that while AI can fabricate convincing but false repros, it still offers productivity gains in areas like debugging and testing. He discusses the balance of trust, automation, and quality in modern software development.
Engineers across database, iOS, frontend, data engineering, and backend domains discuss how AI code generation shifts the hard part to verification and integration, requiring human judgment for subtle risks and architectural fit.
The article highlights a critical issue where AI coding agents may introduce security vulnerabilities into code, noting that simply asking for secure code is insufficient to prevent this.