Visual Studio Code faces backlash over default AI co-authoring in commits
A proposed update to the Git extension has triggered a significant outcry, with users reporting the feature is active even when AI tools are disabled, prompting comparisons to rival editors and threats to abandon Microsoft's software.
A pull request submitted to the Visual Studio Code repository proposes altering the Git extension's default configuration to automatically append 'Co-authored-by: Copilot' trailers to commits where AI-generated code is detected. The initiative aims to standardise attribution for machine-assisted contributions, yet it has ignited a fierce backlash on Hacker News regarding the lack of explicit user consent.
Critics argue that the proposed change forces the feature on unsuspecting users, with several commenters confirming that the tag is being injected into their commits even when they have explicitly disabled AI features or have not utilised Copilot at all. One user reported that despite setting `chat.disableAIFeatures` to true, the system continued to attribute their hand-written code to the AI assistant, describing the behaviour as unacceptable and vandalism.
Technical inconsistencies within the current proposal have further complicated the situation. The configuration schema default was set to "all", intending to enable the feature globally, while the runtime fallback in the source code still defaults to "off". This mismatch creates uncertainty regarding the intended behaviour in specific testing or hosting environments where contributed configuration defaults may not be loaded.
The controversy has drawn sharp comparisons with the Zed editor, which reportedly offers a single global option to disable all AI features. Users frustrated by the perceived lack of control in Visual Studio Code have cited this contrast as a primary reason for threatening to switch away from Microsoft's software to alternatives such as Zed, Neovim, or Emacs.
One developer noted that while Cursor handles AI attribution differently by assuming the user reviews every diff before committing, the Microsoft approach conflates using the editor with co-authoring the code. This devalues the metadata signal that 'Co-authored-by' is meant to carry and risks turning commit history into noise where real authorship becomes difficult to track.
The debate highlights a broader tension in the open-source community regarding how AI integration should be managed. With users expressing that they are warming up to other editors but now feel forced to leave Visual Studio Code, the outcome of this pull request could influence the platform's reputation among developers who prioritise transparency and user agency in their software development lifecycle.
