Linus Torvalds credited an AI in a Linux kernel commit — should I let AI write my code too?

Crediting AI in a commit is a transparency signal, not proof that generated code is automatically trustworthy. Use AI for drafts, repetitive transformations,…

Crediting AI in a commit is a transparency signal, not proof that generated code is automatically trustworthy. Use AI for drafts, repetitive transformations, tests, and explanations—but keep a human responsible for the design, license compatibility, security review, and final diff. Run the project’s test suite, inspect every changed line, and never paste private code or production secrets into a service that is not approved for them.

Why one AI credit line rattled people

The Linux kernel runs most of the world's servers, phones, and supercomputers, and its maintainers are famously strict: every change is human-reviewed. An AI being credited in a commit does not mean a robot merged code — a human maintainer still reviewed, tested, and accepted it, and the credit is disclosure, the same honesty the community demands about any tool.

What to do, step by step

1. Read the credit correctly: the human who submits and signs off on a patch is legally and professionally responsible for it.
2. Expect disclosure norms, not bans. Open-source projects are converging on 'say what the AI did' rather than 'never use it.'
3. Judge the patch, not the byline. Kernel review catches bad code from humans weekly; the process does not care who typed the first draft.