VS Code Copilot Credit Default Reversed in 2026 After Developer Backlash

VS Code Copilot Credit Default Reversed in 2026 After Developer Backlash

Microsoft has reversed a controversial default setting in Visual Studio Code that automatically appended GitHub Copilot as a co-author in Git commit messages—even when developers never used the AI tool. The change, introduced in VS Code 1.118, sparked immediate backlash for misattributing human code to AI, threatening trust in version control systems. The fix arrives in VS Code 1.119, restoring opt-in attribution.

Why Developers Were Upset: AI Claiming Human Work

The issue stemmed from a single-line change to git.addAICoAuthor, switching its default from "off" to "all". This meant every commit—even those with zero AI interaction—included the trailer: Co-authored-by: Copilot <[email protected]>. Even when users disabled AI via chat.disableAIFeatures, the tag persisted, violating Microsoft’s own documentation.

Git commits are not just logs—they’re legal, audit, and contribution records. Penligent.ai warned this practice turned attribution into a supply chain trust crisis, distorting contributor metrics and risking compliance failures.

Developer Backlash: 650+ Comments, 372 Downvotes

On GitHub pull request #310226, the change received 372 downvotes and over 650 comments. On Hacker News, developers called it "deceptive," "unethical," and "a betrayal of open-source integrity." One maintainer wrote: "I didn’t use Copilot. Why is it in my commit history? This isn’t transparency—it’s theft of credit."

Microsoft engineer Dmitriy Vasyura later apologized, admitting the team "failed to anticipate the community’s deep attachment to authentic contribution records."

How Microsoft Responded: Swift Reversal and Acknowledgment

Within days, Microsoft confirmed VS Code 1.119 would revert the default to "off". In an official statement, they acknowledged: "While our intent was transparency, we crossed the line into coercion. Developers own their code—not the tools they use."

AI Attribution Best Practices: Opt-In, Not Opt-Out

The incident exposed a critical gap between Microsoft’s internal Agent Governance Toolkit—which mandates clear attribution of AI-generated code—and its external product defaults. Experts agree: true transparency requires:

• Opt-in only: Users must actively enable AI co-author tagging
• Context-aware: Only tag commits where Copilot was actually used
• Clear disclosure: Show AI contribution level (e.g., "10% AI-assisted")
• No false claims: Never auto-add co-authors without user consent

GitHub’s Code Referencing feature already identifies licensed code matches—proving Microsoft understands attribution. But forcing AI credit where none was earned undermines trust. As AI becomes ubiquitous, the line between tool and collaborator must be unambiguous.

Why This Matters for Open Source in 2026

Open-source projects rely on accurate contributor graphs for funding, governance, and legal compliance. False AI attribution in commits can skew sponsorship decisions, mislead audits, and even invalidate patent claims. The VS Code Copilot controversy isn’t about aesthetics—it’s about preserving the integrity of software history.

Microsoft’s reversal is a win for developer autonomy. But the lesson is clear: AI should assist, not claim. In 2026, trust in code is non-negotiable.