The Mesa 3D graphics driver project has loosened what had been stricter wording in its AGENTS.md file, now permitting AI and large language model assistance in producing code comments and commit or patch messages — provided a human reviews and edits the output before submission, according to Phoronix.
The relaxation appears confined to prose that surrounds the code. The revised policy covers comments and commit or patch descriptions; it says nothing about whether AI-generated code itself is permitted, so contributors should not read the update as a green light for machine-written source.
Why a policy file matters
AGENTS.md has emerged as a conventionally named file in which repositories record how AI coding agents are expected to behave inside that project — what they may touch, what they must not, and what a human is accountable for. Its spread beyond any single ecosystem means a wording change in one project's file is closely watched as an indicator of where AI contribution policy is heading across open source generally.
Mesa's file carries unusual weight in that respect. The project is a high-stakes upstream: it underpins hardware-accelerated graphics on Linux and adjacent platforms, and its review queues absorb contributions from a broad developer base, including corporate engineers and hobbyists. Its guidance is therefore likely to be read as a reference point for how other mature projects frame similar rules.
What actually changed
The load-bearing condition is human review. Under the updated wording, an AI or LLM may draft a comment or a commit or patch message, but a person must review and edit that text before it lands. That places accountability squarely on the contributor who submits the patch, rather than on maintainers to detect machine-generated prose during triage.
The scope boundary is worth restating plainly, because headlines about the change risk being over-read. This is a policy adjustment around documentation surfaces that reviewers already read closely — prose that is visible, diffable and attributable to the person who posted it. The published summary does not indicate that AI-generated code is permitted, and our reading is that this silence should be treated as an absence of permission rather than an implicit approval.
For open-source watchers, the significance is structural rather than technical: no code path changed, but a governance artefact did. Projects are increasingly treating AGENTS.md as a living document whose rules get tuned as agent tooling matures, rather than as a one-time statement of prohibition. Whether that produces better or worse upstream quality is not the question this change answers; it answers a narrower one — which surfaces a project is willing to let machines draft, under what conditions.
What teams can take from this
Teams drafting their own repo-level agent rules can draw a workable pattern from the shift:
- Differentiate by risk, not by tool. Low-risk, review-visible surfaces — comments, commit messages, changelogs — can tolerate AI drafting with mandatory sign-off. Security-critical or integrity-sensitive code paths warrant stricter controls.
- Make human review explicit and non-optional. State who is accountable for the final text, and make clear that approval means a person read and edited it.
- Delimit scope in the file itself. Specify which artefacts the permission covers, and say what the policy does not address, so contributors cannot infer broader rights from silence.
- Revisit the file periodically. If a project treats
AGENTS.mdas a living document, version it and note what changed and why.
For Hong Kong development teams setting their own AI-agent repo rules, the transferable point is that a governance file — not a code change — can carry the policy, and that a clear, revisited AGENTS.md is how other projects will expect contributions to be framed.
Source: Phoronix, "Mesa Loosens Rules Around AI Agents For Code Comments / Commit Messages."
據 Phoronix 報道，Mesa 3D 圖像驅動項目已放寬其 AGENTS.md 檔案中原本較為嚴格的措辭，現容許借助 AI 及大型語言模型（LLM）撰寫代碼註釋以及 commit 或 patch 訊息 — 前提是提交前須由人手審閱及修改產出內容。
今次放寬似乎僅限於圍繞代碼的文字部分。修訂後的政策涵蓋註釋及 commit 或 patch 描述，並未提及是否容許 AI 生成的代碼本身，因此貢獻者不應將是次更新理解為機器撰寫源碼已獲放行。
為何一個政策檔案如此重要
AGENTS.md 已逐漸成為一種慣用命名的檔案，用以在各個 repository 記錄 AI 編碼代理在該項目內的行為準則 — 它們可以碰什麼、不可碰什麼，以及人手須承擔什麼責任。它已普及至單一生態系統以外，因此某個項目檔案中的措辭變動，會被密切注視為觀察整個開源界 AI 貢獻政策走向的指標。
就此而言，Mesa 的檔案份量非同一般。該項目是影響深遠的 upstream：它支撐著 Linux 及相鄰平台的硬件加速圖像，其審核隊列吸納來自廣泛開發者群體的貢獻，當中包括企業工程師及業餘愛好者。因此，它的指引很可能被視為其他成熟項目制定類似規則時的參考基準。
實際改動了什麼
最關鍵的條件是人手審核。根據更新後的措辭，AI 或 LLM 可以起草註釋或 commit、patch 訊息，但該文字在落實之前必須經人手審閱及修改。這將責任明確歸於提交 patch 的貢獻者身上，而非要求維護者在 triage 過程中自行偵測機器生成的文字。
範圍界線值得再清楚重申一次，因為相關新聞標題有被過度解讀的風險。這是一項圍繞審稿人本已仔細閱讀的文件層面所作的政策調整 — 這些文字是可見、可 diff、且可歸屬到發布者的。已公布的摘要並未表示容許 AI 生成的代碼，而我們的理解是，這種沉默應被視為未獲授權，而非默許批准。
對開源觀察者而言，這次變動的意義在於結構層面而非技術層面：沒有任何代碼路徑改變，但一個治理 artefact 改變了。項目愈來愈將 AGENTS.md 視為一份持續演進的文件，其規則會隨代理工具成熟而不斷調校，而非一次性頒布的禁令聲明。這會帶來更好抑或更差的 upstream 質量，並非是次變動所回答的問題；它回答的是一個更狹窄的問題 — 項目願意讓機器在什麼條件下起草哪些層面的內容。
團隊可從中借鏡什麼
正在擬定自身 repository 層級代理規則的團隊，可從是次轉變中歸納出一套可行模式：
- 按風險區分，而非按工具區分。 低風險、審稿可見的層面 — 註釋、commit 訊息、changelog — 可容許 AI 起草，但必須有人工簽署。涉及保安關鍵或完整性敏感的代碼路徑，則需更嚴格的管控。
- 將人手審核明確化且不可豁免。 說明誰須為最終文字負責，並清楚表明獲批准即代表有人閱讀及修改過該文字。
- 在檔案本身劃定範圍。 指明許可涵蓋哪些 artefact，並說明政策沒有處理什麼，以免貢獻者從沉默中推斷出更廣泛的權利。
- 定期重新審視檔案。 若項目視
AGENTS.md為持續演進的文件，應對其作版本管理，並記錄有何改動及原因。
對制訂自身 AI 代理 repository 規則的香港開發團隊而言，可借鏡之處在於：承載政策的可以是一份治理檔案，而非一次代碼變更；而一份清晰、持續更新的 AGENTS.md，正是其他項目預期貢獻應以何種框架呈現的方式。
來源：Phoronix，〈Mesa Loosens Rules Around AI Agents For Code Comments / Commit Messages〉