Another controversy has erupted among software developers against Microsoft due to the addition of new capabilities in Visual Studio Code that allowed AI assistant, Copilot, to be displayed as an author on commits even to people who had not activated this option.
This problem emerged when a pull request was issued for a new capability that added “co-authored by Copilot” as a setting within VS Code. With this update, developers found their commits listed as having been co-authored by Copilot. Complaints regarding the feature came out almost immediately.
The Controversy Surrounding VS Code and Copilot’s “Ghost” Commits
Some developers felt the feature was going too far while others complained about the appearance of Copilot’s co-authorship even on projects in which AI tools were disabled.
Trust was one issue. Commit logs are used by developers to see who wrote code and the reasoning behind the modifications. Critics argued that Microsoft has muddied the distinction between the work done by the developer and the assistance provided by the computer by attributing AI to each commit.
The negative reaction intensified due to the fact that the feature is not restricted only to developers utilizing the Copilot. There have been reports that attribution will be added even if developers have disabled Copilot by using the “chat.disableAIFeatures” option. This was yet another instance where Microsoft had integrated AI tools into its software despite the developers’ reluctance to use them.
There were numerous accusations that Microsoft was attempting to boost Copilot utilization metrics. By having every commit include an attribution from Copilot, the company can present statistics demonstrating high levels of usage, irrespective of whether the developers have ever interacted with Copilot. This move was viewed as part of Microsoft’s “AI slop” policy.
It has been verified that the PR was reviewed and approved by Dmitriy Vasyura, who is part of the VS Code team. After complaints were made about the issue on various online forums for developers, Vasyura took it up in public.
Microsoft Reverses Course on Mandatory Copilot Attribution Amid Developer Backlash
As per Microsoft, the attribution being mandatory was due to a glitch that wasn’t detected during internal testing. The software giant decided to reverse its decision and made the change default from future updates onwards.
In the new scheme of things, the attribution to Copilot will only happen when the changes suggested by the latter are implemented into the projects by the user. The users will also be required to explicitly agree to the addition of any kind of co-author messages in their commit messages.
Many developers refused to be convinced by such reasoning. While for some, the incident was just an example of how Microsoft’s AI is buggy and unreliable, others saw a pattern of aggressive rollouts of the technology that overlooked the needs and fears of developers.
What makes the case even more complex is the timing. Indeed, Microsoft has been gradually rolling out Copilot capabilities to its various offerings in Windows 11, GitHub, and Office applications, where features that involve assistance through AI have appeared in Word, Excel, and PowerPoint. Furthermore, Microsoft has also been testing AI workflows in which AI performs actions with limited user involvement.
This is especially complicated for developers, who are expected to create personalized configurations and have their tools behave predictably.
Microsoft’s Balancing Act Between AI Integration and Developer Autonomy
Some users fear that incorporating AI is moving beyond an option and becoming a standard. Additionally, others believe that integrating AI into their work will result in a loss of visibility for the developer over how much AI-generated content goes into their production systems. In some industries, a mistake here can lead to legal issues.
The debate around this topic highlights the struggle within the software development world in general. There is a race between firms to incorporate AI technologies into their products, yet developers continue to be skeptical over AI system incorporation in their work. It seems like developers oppose the idea of changing their processes without explicit consent.
Microsoft finds itself in a difficult position as the company aims to make Copilot a central tool in its portfolio while competitors release similar products. On the other hand, developers want transparency and autonomy when working with their software.
Currently, this issue becomes one more example of why users oppose AI incorporation. Although the software glitch may be fixed easily, Microsoft still needs to regain developers’ trust, which will likely require more time.
