"I've removed the Claude co-authorship from the commits a few days ago. So good luck figuring out what's generated and what is not."
That's the Lutris creator's response to community pushback after users spotted AI-generated code flowing into the popular Linux game manager. The quote tells you everything about where the AI-in-open-source debate stands right now: messy, defensive, and unresolved.
What Actually Happened
Lutris is a well-known game manager for Linux that helps users install and run games from various sources. Its creator, who goes by strycore and has over 30 years of programming experience, started using Claude to generate code contributions. The reason was understandable: health issues and depression had slowed development, and AI coding tools offered a way to catch up on a backlog of work.
GitHub users noticed "LLM generated commits" in the repository. One asked bluntly whether "Lutris is slop now." The backlash hit several nerves at once: trust in code quality, copyright questions around AI-generated code ownership, ethical objections to supporting AI companies, and what some saw as a contradiction for a game preservation platform.
The developer's fix was not to stop using Claude or to have an open conversation about AI-assisted development practices. Instead, he stripped the Claude co-authorship tags from commits, making it impossible to tell which code was human-written and which was AI-generated.
The Real Problem Isn't the Tool
The developer argued that the real issues stem from corporate behavior, not from AI tools themselves. That's a fair point. Claude Code, Cursor, GitHub Copilot - these tools are already embedded in professional software development. Plenty of code shipping to production today has AI fingerprints on it.
But open source runs on different fuel than corporate software. Contributors donate time because they trust the project. Users audit code because they can. Hiding which commits came from an AI undermines both of those foundations. The transparency that makes open source work is exactly what got removed here.
This isn't unique to Lutris. The Linux kernel has been wrestling with AI-generated contribution policies. Multiple open-source foundations are drafting guidelines. The friction point is consistent: it's not that developers are using AI tools, it's that there's no agreed-upon standard for disclosing it.
For the growing number of developers using Claude, Copilot, or Cursor in their daily work, the Lutris situation is a preview of conversations coming to every open-source project. The co-authorship tag was actually the right approach. Removing it was the wrong one.