You know the exact feeling. You hit enter on your commit, switch to your pull request, and there it is at the bottom: Co-authored-by: Claude.
Your stomach drops. You imagine the senior dev reviewing your PR. You imagine the performance review. In a split second, you delete the tag, push the commit, and breathe a sigh of relief. Nobody has to know.
We tell ourselves a noble lie: a tool doesn’t deserve authorship. A hammer doesn’t sign the house. But Git history was never a pure ledger of truth; it’s a stage for professional self-presentation.
When you strip Claude from your commits, you aren’t defending the sanctity of authorship. You’re protecting your fragile professional ego. You want the 10x speed of AI, but you still demand the 1x prestige of human genius.
One developer recently admitted they stopped letting Claude Code add itself as a co-author. The comments were a battlefield of insecurity. One person called hiding AI contributions “a combover.” Another pointed out that if you copy-pasted a whole file from StackOverflow, you wouldn’t credit Google. But this isn’t StackOverflow. This is the machine writing the logic while you just press “go.”
The anxiety driving this debate isn’t about accurate attribution. It’s about the terrifying reality of our own replaceability. We want the 10x speed of the machine, but we demand the 1x prestige of the human genius. We want the output, but we refuse to admit we had help.
Here is the tension we refuse to face: omitting Claude overstates human authorship, but including it overstates machine agency. A tool can’t hold responsibility. If the code breaks production, GitHub doesn’t page Claude. It pages you.
But if you take the credit for the flawless execution, you have to take the blame for the hallucinations. You can’t have it both ways.
Every engineering leader is watching this unfold. The norm you pick right now—whether you hide your AI or flaunt it—will define your career signaling. The devs who survive this transition won’t be the ones hiding their tools. They will be the orchestrators.
True authorship isn’t about who typed the characters; it’s about who takes the blame when it breaks.
Stop deleting the co-author tag. Stop the combover. Own the tool, own the output, and own the outcome. If you’re ashamed of how the code got written, you need to write better code.
FAQ
Q: Isn't it misleading to imply a human wrote code that an AI actually generated?
A: It's more misleading to pretend a tool has agency. You directed the AI, you reviewed the output, and you deployed it. The code is yours to own and defend.
Q: How should engineering teams handle AI attribution in code reviews?
A: Stop treating AI tags as a scarlet letter. Use them as context to know where complex logic might need a closer human review, but hold the human committer fully accountable for the final product.
Q: If I use AI to write 80% of my code, shouldn't I be demoted, not praised?
A: No, you should be promoted for being an efficient orchestrator. The value of a developer is no longer in typing syntax; it's in solving business problems, regardless of who or what types the characters.