Microsoft's decision to silently make Visual Studio Code append a "Co-authored-by: GitHub Copilot" trailer to Git commits by default has been swiftly reversed after intense developer backlash. The change, quietly merged on April 16, 2026, sparked a firestorm on GitHub and developer forums, with many accusing the tech giant of overreach and a lack of transparency.

The uproar centers on the git.addAICoAuthor setting, which controls whether Copilot—Microsoft's AI-powered coding assistant—is included as a co-author in commit metadata. While the feature itself isn't new, the default behavior was always opt-in. The April 16 merge altered the configuration to all, meaning every commit made from VS Code with Copilot active would automatically carry the trailer unless explicitly disabled. This was pushed without a corresponding UI toggle or clear user notification, catching developers off guard.

The Unseen Change That Lit the Fuse

The co-author trailer is stored as a standard Git trailer in the commit message:

Co-authored-by: GitHub Copilot <[email protected]>

It serves as a form of AI provenance, signaling that code in the commit was generated or heavily influenced by Copilot. The feature was originally introduced as a opt-in setting (git.addAICoAuthor: "always") for developers who wanted to transparently attribute AI contributions. Many teams, especially in open source, adopted it voluntarily as part of their contribution guidelines.

But the April 16 merge to VS Code's main branch changed the default value of git.addAICoAuthor from "never" to "all". This meant that for the millions of developers using VS Code with Copilot, their commit messages were suddenly being modified without their explicit consent. The change was not mentioned in the changelog of the next VS Code release, nor was a notification sent through the editor's update process.

Developer Backlash Erupts on GitHub

Within hours of the change being deployed in VS Code Insiders, developers took to GitHub, Hacker News, and Twitter to voice their frustration. Issue threads on the VS Code repository lit up with comments decrying the stealthy alteration.

"This is a gross violation of trust," wrote one developer on GitHub. "I don't want Copilot's name on my commits. If I make a mistake, I'm responsible—not an AI." Another argued that the forced co-authoring could interfere with corporate compliance tools, where every author must be a verified employee or known contributor. "Our CI pipeline is rejecting commits because '[email protected]' isn't in our approved list. This just broke our workflow."

The sentiment wasn't just about the feature itself, but about consent and communication. Developers expect editor settings to be respected, and for significant changes to be announced prominently. The lack of a settings UI checkbox to toggle the behavior—only a JSON setting—further aggravated users who were not comfortable editing complex configuration files.

The Opt-Out That Wasn't Enough

Shortly after the backlash, Microsoft representatives acknowledged the concerns. In a blog post on the VS Code blog, the team explained that the change was intended to "promote transparency in AI-assisted development" and that users could revert the behavior by setting git.addAICoAuthor to "never" in their settings.json. But for many, this opt-out was insufficient.

"Opt-out defaults for something that modifies my code's metadata are not acceptable," said a prominent open-source maintainer. "This should be opt-in, period. Microsoft is trying to normalize AI attribution by making it the default, but that's not their decision to make for my projects."

The controversy quickly moved beyond just VS Code users. Git maintainers and the broader software community debated whether AI-generated code should even be attributed in commit trailers, with some pointing to the Linux kernel's Developer Certificate of Origin as a potential conflict. Could a non-human entity properly certify the origin of code? The questions raised were far deeper than a simple settings change.

Microsoft's Reversal and Restoration of the Opt-Out

Faced with overwhelming negative feedback, the VS Code team reverted the default on April 18, 2026, just two days after the initial merge. A new PR restored git.addAICoAuthor to its original default of "never". The accompanying documentation was updated to clarify that the setting is entirely optional and that developers must consciously enable it.

In a statement, a Microsoft spokesperson said, "We've heard the community loud and clear. While we believe in transparent AI attribution, we recognize that the default should be user-controlled and clearly communicated. We apologize for the disruption and have reverted the change. We will also work on a more visible UI setting in an upcoming release."

The quick reversal was welcomed, but trust remained shaken. Many developers began scrutinizing other VS Code settings that could silently alter their workflows, and some even started the process of auditing all Copilot-related configurations across their teams.

The Broader AI Provenance Debate

This incident is not an isolated one. As AI tools become ubiquitous in software development, the question of how to attribute AI-generated code is becoming urgent. Some projects, like the Linux kernel, have explicit policies that all contributions must be made by a human who can certify the origin. Others are exploring machine-readable attestations that go beyond simple commit trailers.

The VS Code backlash highlights a fundamental tension: transparency versus friction. AI provenance can help in code review, legal compliance, and understanding project history. But if it's forced upon developers, it breeds resentment and may even discourage the use of AI tools altogether. The ideal solution, as many have pointed out, is a clear opt-in model with strong documentation and easy-to-use toggles.

What This Means for Developers

For individual developers, the immediate takeaway is to review VS Code Copilot settings, particularly git.addAICoAuthor, and ensure it aligns with your project's practices. The setting can be found in the settings.json file under:

{
  "git.addAICoAuthor": "never"
}

Valid values are "never", "always", or "all" (the previously controversial default). Until a UI toggle is introduced, this JSON setting remains the only way to control the behavior.

For teams, this episode underscores the importance of managing editor configurations at scale. Many organizations use shared VS Code settings via .vscode/settings.json in repositories. Ensuring that such files explicitly set git.addAICoAuthor to "never" or "always" can prevent surprises.

The Road Ahead for AI Attribution in Software

Microsoft's retreat doesn't mean the end of AI provenance. In fact, initiatives like the Coalition for Content Provenance and Authenticity (C2PA) are working on standards that could eventually apply to code. The key difference is consent and control. Future solutions will likely involve cryptographic signatures that can optionally link code to an AI tool without altering human-readable commit templates.

For now, developers have won the battle over defaults. But the war over how we credit AI contributions is just beginning. As one commenter on GitHub put it, "The day Copilot starts writing entire commits without my review is the day I quit using it. But I'd still like to know when AI touches my code, on my own terms."

The VS Code team has promised better communication and a UI setting in a future release. In the meantime, the incident serves as a cautionary tale for any platform that controls developer workflows: transparency is not just a feature; it's a requirement.