I have used the new template below to show how it looks. We can add more details to the linked CONTRIBUTING.md in the pop repo.
I have not included any LLM (also known as AI) generated content in...
I gotta admit KDE’s stance on this frustrates me a lot.
On the flip side… I am also fully aware that policies of prohibition, in the broadest sense, tend to not be terribly successful, and I wouldn’t be shocked if some contributors simply excise the “co-authored by <agent-name>” from the commit messages with a simple pre-push hook or something like that on projects that explicitly prohibit LLM/codegen usage.
IMO one of the major problems with LLm code generation is that it has the capacity to overwhelm human capacity to review code and properly understand the codebase.
From that perspective, a prohibitive policy doesn’t have to be 100% effective to be useful, it just needs to slow things down enough to keep the manageable and maintainable (and fun to work on).
Some people will absolutely lie, but I suspect most contributors will respect the rules, and ultimately cut down on AI PRs overall, as those AI contributors switch to projects who are pro-AI.
I admit I haven’t followed the KDE AI debacle very closely, but as far as I understand KDE has not yet decided on an AI policy. Am I mistaken?
Edit:
From all primary sources I’ve been able to track down, nothing suggests an AI policy has been decided. This is the best explanation of the situation I’ve found so far, though it is a bit over a week old: https://planet.kde.org/nate-graham-2026-09-23-kde-and-ai-and-you-and-me/. If you have a primary source that says otherwise, please link it here, I’d like to know what their AI policy ends up being.
Your very source confirms they have not yet decided on an llm policy. It’s also pretty old, and the link I posted on my other comment, which comes from Nate Graham himself, goes a lot more in depth about the incomplete policy proposal he had and is more up to date on the situation.
I’ll keep an eye out for their policy when it comes out, but all signs point to a policy not yet being decided upon.
From all primary sources I’ve been able to track down, nothing suggests an AI policy has been decided. This is the best explanation of the situation I’ve found so far, though it is a bit over a week old: https://planet.kde.org/nate-graham-2026-09-23-kde-and-ai-and-you-and-me/. If you have a primary source that says otherwise, please link it here, I’d like to know what their AI policy ends up being.
I gotta admit KDE’s stance on this frustrates me a lot.
On the flip side… I am also fully aware that policies of prohibition, in the broadest sense, tend to not be terribly successful, and I wouldn’t be shocked if some contributors simply excise the “co-authored by <agent-name>” from the commit messages with a simple pre-push hook or something like that on projects that explicitly prohibit LLM/codegen usage.
IMO one of the major problems with LLm code generation is that it has the capacity to overwhelm human capacity to review code and properly understand the codebase.
From that perspective, a prohibitive policy doesn’t have to be 100% effective to be useful, it just needs to slow things down enough to keep the manageable and maintainable (and fun to work on).
Some people will absolutely lie, but I suspect most contributors will respect the rules, and ultimately cut down on AI PRs overall, as those AI contributors switch to projects who are pro-AI.
I admit I haven’t followed the KDE AI debacle very closely, but as far as I understand KDE has not yet decided on an AI policy. Am I mistaken?
Edit:
From all primary sources I’ve been able to track down, nothing suggests an AI policy has been decided. This is the best explanation of the situation I’ve found so far, though it is a bit over a week old: https://planet.kde.org/nate-graham-2026-09-23-kde-and-ai-and-you-and-me/. If you have a primary source that says otherwise, please link it here, I’d like to know what their AI policy ends up being.
They have, and I’m not really a fan of their choice.
You got a source?
https://chrislongros.com/2026/09/11/kde-about-to-introduce-a-llm-policy/
Your very source confirms they have not yet decided on an llm policy. It’s also pretty old, and the link I posted on my other comment, which comes from Nate Graham himself, goes a lot more in depth about the incomplete policy proposal he had and is more up to date on the situation.
I’ll keep an eye out for their policy when it comes out, but all signs point to a policy not yet being decided upon.
From all primary sources I’ve been able to track down, nothing suggests an AI policy has been decided. This is the best explanation of the situation I’ve found so far, though it is a bit over a week old: https://planet.kde.org/nate-graham-2026-09-23-kde-and-ai-and-you-and-me/. If you have a primary source that says otherwise, please link it here, I’d like to know what their AI policy ends up being.
Or you tell it not to commit but to suggest the commit message
A simple mention of it in your agent instructions will also do it.