VS Code Is Quietly Adding Copilot as a Co-Author on Your Commits

Pull up your recent GitHub commits. Look at the footer. If you spot a Co-Authored-by: Copilot <...> line on code you wrote entirely by hand, you’re not imagining things — and you’re not alone. A growing chorus of developers has noticed VS Code attributing commits to Copilot without ever asking. The grumbling on Hacker News and r/programming has been steady, and it points at something larger than a UX miss.

What’s actually happening

The mechanic is simple. When you commit through VS Code’s Source Control panel with the Copilot extension installed, the commit message gets a Co-Authored-by: Copilot footer appended automatically — regardless of whether you accepted a single suggestion.

Hand-typed every character after an hour of debugging? Doesn’t matter. Have Copilot installed but mostly disabled? Doesn’t matter. The label gets stamped on either way.

The kicker is that it’s opt-out, not opt-in. Unless you go hunting through settings to disable it, the default behavior treats every commit as a collaboration with an AI you may not have used.

Why this isn’t just a bug

The instinct is to shrug and flip a setting. Step back, though, and the picture gets more interesting.

What’s the single most-cited statistic from Microsoft and GitHub right now? “The percentage of code written by Copilot.” When Satya Nadella tells an earnings call that AI writes 20–30% of Microsoft’s code, the underlying data has to come from somewhere — and commit metadata is exactly the kind of signal that feeds those numbers.

If hand-written code gets auto-signed as a Copilot collaboration, the denominator is contaminated from the start. Whether intentional or not, the architecture inflates AI’s apparent contribution. The narrative writes itself before anyone audits the data.

What developers are really mad about

The surface complaint is “the default is annoying.” Read the threads carefully and three deeper concerns surface.

First, provenance and liability. For developers working under strict licensing regimes — finance, regulated software, anything with a clean-room requirement — an “AI co-author” tag isn’t just metadata. It’s a flag that an auditor will ask about. Once it’s in the git history, it’s there forever.

Second, performance reviews. Some companies have already started folding “AI tool adoption” into engineer evals. An auto-stamped co-author label can cut both ways: evidence you’re an “AI-forward” developer, or a quiet signal that you can’t ship without one. Either way, the label wasn’t yours to apply.

Third, and most fundamentally, consent. The pushback isn’t “I can’t find the toggle.” It’s “why was this on by default in the first place?” That’s a different category of complaint, and it’s the one that’s hardest to wave away.

How to turn it off

If you want to check your own setup right now: open VS Code settings and search for git.useCoAuthoredBy or the Copilot-related commit options. Toggle them off.

To audit what’s already in your history, run git log --format=full and scan for Co-Authored-by footers you don’t remember adding. Don’t rewrite already-pushed commits — that path leads to broken refs and angry teammates. Just clean it up going forward.

The takeaway

This story is interesting not because of the bug, but because of what it exposes: every “AI wrote X% of our code” claim rests on a labeling rule someone, somewhere, decided. Change the default, change the number.

Check your next commit. See who’s listed as co-author. Then ask the harder question: are we actually measuring AI’s contribution to software, or just measuring whatever our tools have decided to call it?