VS Code Copilot Co-Author Controversy: What Developers Need to Know

What Happened: The Silent Co-Author

On April 29, 2026, Microsoft released VS Code 1.118 with a change that ignited one of the biggest developer backlashes of the year. The update introduced a new default behavior: automatically appending Co-authored-by: Copilot <copilot@github.com> to git commits whenever the editor detected any AI-assisted code contribution — even something as trivial as accepting a single autocomplete suggestion for a typo fix.

The feature, controlled by the git.addAICoAuthor setting, defaulted to chatAndAgent mode rather than off. Most developers discovered it only after noticing the attribution appearing in their git logs or CI output — in many cases, weeks after the feature had silently activated via auto-update.

Here's what the silent modification looks like in practice:

# What you type:
git commit -m "Fix authentication bug"

# What VS Code 1.118 creates:
git commit -m "Fix authentication bug

Co-authored-by: Copilot <copilot@github.com>"

The change happens silently unless you manually review the commit message before confirming. Worse, some developers reported seeing the attribution appear even when they had Copilot features disabled entirely — suggesting the detection threshold was overly aggressive or the feature was triggering erroneously.

Why Developers Are Furious

The reaction was immediate and intense. Within 24 hours, GitHub Issue #313064 erupted with complaints from developers around the world. The core objections fell into several categories:

• Unconsented authorship claims: Developers view git history as a professional record of their work. Having a machine automatically claim co-authorship without asking feels like an assertion of ownership over human-created code.
• Permanent git history: Once you've pushed commits with "Co-authored-by: Copilot," removing them requires rewriting git history — a destructive operation that breaks forks, disrupts collaboration, and is impractical for large repositories.
• Opt-out, not opt-in: The feature was enabled by default, requiring developers to discover it and manually disable a buried setting. Critics compared it to email signatures like "Sent from my iPhone" — unwanted advertising baked into professional output.
• Even non-Copilot users affected: Reports emerged of the attribution appearing for developers who don't actively use Copilot, suggesting the autocomplete detection was overly broad.

One Hacker News commenter captured the sentiment: "That is not co-authorship. It's like 'Sent from an iPhone' levels of nuisance default advertising." Another developer who doesn't use Copilot called the approach "desperate," noting that Microsoft was claiming authorship on code it didn't help write.

The Copyright Minefield

The timing of this feature couldn't be worse for Microsoft. On March 2, 2026 — just 58 days before VS Code 1.118 shipped — the U.S. Supreme Court denied certiorari in Thaler v. Perlmutter, cementing the precedent that non-human authors cannot hold copyright under the Copyright Act. The Copyright Office has been explicit: only works authored by human beings are eligible for copyright protection.

This creates a genuine legal tangle:

• Open source complications: Licenses like GPL, MIT, and Apache all rest on copyright law, which assumes human authorship. Listing a non-human as co-author introduces ambiguity about the copyright status of the code.
• Corporate IP concerns: Companies with strict intellectual property requirements may inadvertently complicate ownership claims by having AI listed as a co-author on their proprietary code.
• Contributor license agreements: Many open source projects require contributors to affirm they hold copyright on their contributions. If AI is a co-author, who actually holds that copyright?

How Other AI Coding Tools Handle Attribution

Microsoft's approach stands in stark contrast to the rest of the AI coding tool industry. Every other major player makes attribution opt-in, respecting developer choice:

The pattern is clear: industry consensus respects user choice on AI attribution. Microsoft broke from that consensus by forcing attribution as the default, then requiring users to find and disable a setting buried in their configuration. Transparent tools ask permission. This feels more like branding.

How to Disable Copilot Co-Author

If you're using VS Code 1.118 or later, here's how to turn off the automatic attribution:

Method 1 — Settings JSON:

// Add to your settings.json
{
    "git.addAICoAuthor": "off"
}

Method 2 — Settings UI:

• Open VS Code Settings (Cmd+, on Mac, Ctrl+, on Windows)
• Search for "Git Add AI Co Author"
• Set the value to off

Check if you're already affected:

git log --grep="Co-authored-by: Copilot"

If you find affected commits that have already been pushed, you'll need to decide whether rewriting history is worth the disruption to your collaborators. For many teams, this is an unwelcome choice forced upon them by a silent default.

What This Means for AI Coding Tools

The Copilot co-author controversy is about more than one setting in one editor. It highlights a broader tension in the AI tool industry as companies race to embed AI into every workflow:

• Transparency vs. branding: There's a legitimate case for acknowledging AI contributions to code. But the line between transparency and forced advertising is thin, and Microsoft crossed it. The right approach is opt-in attribution that developers actively choose.
• Developer trust: The AI coding tool market is fiercely competitive, with Cursor, Zed, Claude Code, and others all vying for developers' attention. Trust is the currency. Silent changes to git history erode that trust quickly.
• Legal frameworks lag behind: As AI tools become more capable, the gap between what's technically possible and what's legally clear grows wider. The copyright implications of AI co-authorship need legislative attention, not unilateral corporate decisions.
• User agency matters: Developers are particular about their tools and workflows. Any change that silently modifies professional output without consent will face backlash — regardless of the company behind it.

The controversy also coincides with a period of intense competition in AI coding editors. Zed 1.0 launched on April 30 to massive enthusiasm (nearly 2,000 HN points), positioning itself as a privacy-first, high-performance alternative. Cursor continues to gain market share with its AI-native approach. And Claude Code has become a favorite among developers who want AI assistance without editor lock-in.

Frequently Asked Questions