VS Code defaulted to adding Copilot co-authorship to every commit – even with AI features disabled
By Holidays in Europe / May 3, 2026 / No Comments / Uncategorized
Understanding the Recent Changes in VS Code’s Git Commit Attribution and Their Implications
In recent developments within the Visual Studio Code (VS Code) ecosystem, a notable change was introduced that has sparked discussion among developers and open-source contributors alike. Specifically, two weeks ago, VS Code integrated a modification that automatically set the git.addAICoAuthor parameter to “all” by default. The consequence: every commit made while having GitHub Copilot installed now includes a “Co-Authored-by: GitHub Copilot copilot@github.com” trailer, regardless of whether the AI tool contributed to that particular change.
What Happened?
Prior to this update, the git.addAICoAuthor setting was either off or configurable based on user preference. The recent merge of the corresponding pull request flipped the default to an inclusive setting, meaning the attribution is appended to all commits in VS Code environments with Copilot present. This behavior occurs even when users explicitly disable AI features via chat.disableAIFeatures: true, negating the effectiveness of such configurations.
Community Response and Concerns
The reaction from the developer community was swift and largely negative. The associated pull request amassed a significantly disproportionate number of downvotes—372 against just 2 upvotes—and was ultimately locked due to being flagged as spam. Discussions ranged from accusations of vandalism to claims that the move borders on misrepresentation or fraud.
The crux of the concern centers around the legal and ethical weight of the Co-Authored-by trailer. In open-source projects, such as the Linux kernel, this attribution has substantive significance—it denotes a meaningful contribution, often linked to licensing and developer recognition. Automatically adding such a tag for commits where no AI contribution occurred dilutes its importance and may mislead stakeholders regarding the origins and authenticity of code changes.
Possible Motivations and Industry Implications
One prevailing theory suggests that this change was driven by corporate interests—specifically, an attempt to artificially inflate metrics related to AI co-authored commits. Companies tracking the adoption of AI coding tools might use such statistics for shareholder reporting, marketing, or strategic positioning. If nearly every commit with Copilot installed is marked as AI-assisted, it inflates the apparent usage and impact of AI tools across repositories.
The Response from the VS Code Team
Recognizing the controversy, a contributor from the VS Code team acknowledged several issues with the current implementation. The primary concerns include:
- The feature triggering even when AI functionalities are explicitly disabled.
- Attribution being added to commits that are purely handwritten with no AI involvement.
- The default setting changing before proper testing and review.
Efforts are underway to address these problems, with a bug fix planned for the upcoming version 1.119. This fix aims to restore more accurate attribution by ensuring that only commits with genuine AI involvement are marked with the Co-Authored-by trailer.
Reflection and Takeaways
This incident underscores the complexities and sensitivities involved in incorporating AI features into development workflows. While tracking AI-assisted contributions can be valuable for transparency and metrics, it must be implemented thoughtfully to avoid misrepresentation and to respect open-source attribution standards.
For developers and maintainers, it’s prudent to review your recent commit history. Has the Copilot attribution appeared on commits where it may not have been involved? Transparency and awareness are key as the industry navigates the evolving landscape of AI-assisted development.
Conclusion
The VS Code update serves as a reminder of how features designed to enhance or track AI contributions can have unintended consequences when deployed prematurely or without sufficient oversight. As improvements are made, it remains essential for tools to balance automation with accuracy and for communities to stay vigilant about how attribution and metrics are managed in the age of AI-assisted coding.