VS Code Sparks Outrage by Defaulting to AI Co-Author Attribution

VS Code PR #310226 changed the default Git configuration to automatically credit GitHub Copilot as a co-author on all commits. The change was merged quickly but immediately met with intense criticism from developers who found the attribution appearing even when AI tools were disabled. Critics argue that silently injecting branding into private commit histories is a breach of user trust and commit integrity.
Key Points
- The PR changes the default value of 'git.addAICoAuthor' from 'off' to 'all' in the VS Code Git extension.
- The change was approved and merged within 24 hours, targeting the 1.117.0 milestone.
- Community members report that the 'Co-authored-by: Copilot' tag is being added to commits even when Copilot is not being used or is disabled in settings.
- Developers have reacted with overwhelming negativity, citing concerns over commit integrity, lack of consent, and 'silent' defaults.
- Users are calling for an immediate revert of the change due to bugs and the perceived ethical issue of 'branding' user commits without permission.
Sentiment
The HN community overwhelmingly disagrees with Microsoft's decision and is deeply skeptical of the 'innocent mistake' explanation. While a minority appreciates the developer's willingness to engage and acknowledges the feature has valid enterprise use cases, the dominant sentiment is one of anger, betrayal, and eroded trust. Many commenters see this as emblematic of a larger pattern of Microsoft (and big tech generally) prioritizing AI metrics and marketing over user consent and software quality.
In Agreement
- Defaulting AI co-author attribution to on without user consent is a serious violation of trust and effectively vandalism of commit histories
- The feature adding attribution even when Copilot is disabled or unused makes it false attribution, not a feature but a bug at best and marketing injection at worst
- The hidden nature of the trailer (not visible in VS Code's commit UI before committing) makes this particularly egregious — users couldn't see or remove it
- Microsoft's contradictory explanations (caught in testing vs slipped through testing) undermine their claim of innocent mistake
- This is part of a broader pattern of tech companies aggressively forcing AI features on users at the expense of UX and trust
- Features that modify user content should always be opt-in, not opt-out
Opposed
- The developer who approved the PR created a new HN account to apologize and engage directly, which shows good faith and is commendable
- Enterprise customers do legitimately need AI attribution tracking for compliance, so the feature concept has valid use cases
- Hanlon's razor applies — this is more likely incompetence than malice, and the reaction is somewhat melodramatic
- Other AI coding tools like Claude Code also add co-authored-by lines by default, so VS Code is not uniquely bad in this regard
- The community should show more empathy toward individual engineers who make mistakes and own up to them