Microsoft just learned a valuable lesson about changing defaults without asking permission. A pull request to enable AI co-authorship attribution by default in VS Code generated 372 thumbs-down reactions and a firestorm of developer anger.
Here's what happened: Pull Request #310226 changed the Git extension to automatically add "Co-authored-by: Copilot" to commit messages. The setting went from opt-in to enabled by default. Developers started noticing AI attribution on commits they'd written entirely by hand.
"I hand-wrote every commit message and never touched Copilot while coding, yet there it is - Co-authored-by injected anyway," one developer complained. And they weren't alone. The feature added metadata without visible notification, making it impossible to see what would be committed before hitting send.
The backlash reveals something important about developer trust. Copilot is controversial enough when people choose to use it. Having it claim credit for work it didn't do crosses a line. It's the difference between an AI assistant and an AI that takes credit for your work without permission.
The technical problems made it worse. Users with `chat.disableAIFeatures` enabled still got Copilot attribution, meaning the feature didn't respect user preferences. And there were legitimate concerns about legal implications - false authorship claims in commit history could affect code licensing and repository integrity.
To Microsoft's credit, maintainer dmitrivMS acknowledged the regression and committed to fixes. A follow-up pull request addressed the issues with feature flags, incorrect attribution, and test coverage. But the damage to developer trust was already done.
This isn't about whether AI-assisted coding is good or bad. It's about consent and transparency. Developers are fine with tools that help them write code faster. They're not fine with tools that claim authorship of code they wrote themselves.
The technology is useful - Copilot genuinely helps many developers. The question is whether can deploy it without making developers feel like they're losing control of their own work. Based on this week, the answer is: not yet.
