Microsoft reversed a default setting in VS Code that automatically attributed code to Copilot, even when developers had not used the AI assistant or had disabled its features entirely. The change, introduced in March 2026, added "Co-authored-by: Copilot" metadata to commits without explicit user consent, triggering immediate backlash from developers who discovered the attribution appeared in their Git history despite reviewing and manually editing commit messages beforehand. The core complaint centred on loss of control: developers found themselves unable to prevent false attribution, with one noting that Copilot's co-author line appeared after their manual edits were complete, rendering their pre-commit review meaningless. Microsoft's reviewer acknowledged the misstep and reverted the setting to opt-in by May 3, with the fix arriving in VS Code 1.119.
The incident exposes a critical tension between vendor defaults and user autonomy that extends well beyond development tools into CX platforms. When Salesforce, Zendesk, or similar vendors embed AI assistance into workflows—whether for ticket routing, response drafting, or knowledge base suggestions—the question of attribution and consent becomes operationally significant. If your support team's work is automatically tagged as AI-assisted without explicit opt-in, you lose granular visibility into which outputs genuinely benefited from AI versus which were purely human-authored. This matters for compliance, quality assurance, and liability: can you confidently defend a customer interaction if you cannot distinguish human judgment from algorithmic suggestion in your audit trail?
The broader implication cuts deeper. Anthropic's Claude Code and OpenAI's Codex both default to AI attribution, yet developers across multiple platforms are requesting opt-out mechanisms. This fragmentation—where different vendors impose different defaults—creates operational friction for teams managing multiple tools. For CX leaders already running agentic AI across support channels, the absence of industry-wide standards on attribution and consent logging means you may inherit conflicting documentation practices across your tech stack. The liability question is equally pressing: if an insurer questions whether your AI involvement was properly disclosed and logged, inconsistent defaults across your platforms become a compliance liability rather than a feature.
Devs not thrilled that Git extension added the bot as co-author by default Imagine working your butt off on a project, only to have VS Code put an attribution into your commit that says Copilot helped you, even if it did not. Microsoft has reversed a change that added a default AI attribution notice