5/3/2026 at 12:06:42 AM
I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation.There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well.
Obviously, it should not be on when disableAIFeatures is on and it should not be reporting changes that were not done by AI. I'll work on fixing those and meanwhile revert default to off in 1.119 update.
I am open to any (constructive) comments/suggestions - please feel free to reach me directly (my alias @microsoft.com) or open an issue on GitHub. Happy to answer anything here as well.
by dmitriv
5/3/2026 at 1:15:21 AM
I think the constructive criticism is best directed at whatever process you are following. That process allowed a very visible user facing change in a widely used piece of software. How did this change make it to production without some process catching the impact of this change? Was there really no internal discussion from a code review at least? This seems hard for me to believe. I expect more from Microsoft.by somebehemoth
5/3/2026 at 4:43:27 AM
> Was there really no internal discussion from a code review at least? This seems hard for me to believe.The outlined story feels unfortunately very believable to me.
Teams need to push out the most number of features, and nobody stops even for a second to think about how a feature might affect other flows or other users not in the feature request.
It might have been quickly reviewed to check if the code does what it needs to do (add the coauthor note).
Do you think reviewers will think about unwanted effects, when they need get back to feeding their own poorly thought out and underspec’d features to their LLMs?
by serial_dev
5/3/2026 at 6:38:00 PM
> Was there really no internal discussion from a code review at least? This seems hard for me to believe.>The outlined story feels unfortunately very believable to me.
100% agree here - we seem to forget that most developers hate code reviews. I actually laughed out loud at the use of the word "discussion," it's so rare people want to get together and talk about changes. By the time the PR is up anything that stands in the way of merging and shipping is seen as a nuisance.
To my mind this whole debacle is not really the individuals fault or even the team's fault but the economic pressures that drive people into situations like this.
by _doctor_love
5/3/2026 at 7:03:47 AM
Fair point. We did catch it internally in testing (as we use VS Code for all our work, so some folks did stumble on it), but I think we underestimated the impact and should do a better job at that.by dmitriv
5/3/2026 at 10:32:05 AM
This is honestly the most concerning part of all of this. You're saying you knew that this exact bug was present up front and still decided to release it?This basically invalidates the entire premise that it was an innocent mistake. It's impossible for me to believe that you actually thought that people wouldn't care about 100% of their commits being attributed to Copilot even when it was never used. Either you're misconstruing what you caught with the testing beforehand or your entire development process is tainted, because there's no way that a non-evil corporation would see this default behavior and think that people would be fine with it. It seems far more likely you just thought you could get away with it.
by saghm
5/3/2026 at 11:27:03 AM
Agreed, this approach feels like folks at Microsoft still feel they have enough karma to burn. It's way past that.by sinpif
5/3/2026 at 11:32:09 AM
I think there is a "ship fast" component here that should be adjusted. Product Management introduced weekly "stable" releases in March, no matter the content.by lppedd
5/3/2026 at 6:13:53 PM
don't call it a bug, they were intentionally aggressively pushing marketing copy into people's commits.this was malice or greed
by make3
5/4/2026 at 6:49:51 PM
I think so too, but my point is that even according to their own words about what happened, the best possible interpretation is that they didn't mean to do it but knowingly let it happen. I agree that a worse version is more likely, but it's pretty damning when even the ceiling for what they can plausibly claim is "we intentionally didn't bother stopping it once it happened accidentally".by saghm
5/3/2026 at 10:54:14 AM
Seems that they released it only in some internal / alpha version.by spixy
5/3/2026 at 9:46:49 AM
Thank you. My personal opinion is the idea of weekly releases should be discarded. It's too easy to release broken stuff in non-insiders updates.I think many people agree here.
by lppedd
5/3/2026 at 8:12:39 PM
A generous read of this comment might be that you did catch it internally in testing AFTER it shipped but shrugged it off as something you'd patch in the next release in a week or two. Is that what you meant here?Or that it was caught but didn't surface fully before release?
A helpful governance policy here might be that anything that mutates user content without opt-in consent requires a distinct sign-off or a double sign-off. If the goal is to prevent this from happening in future.
by anbende
5/3/2026 at 8:05:51 PM
You say in another comment this slipped through testing. Can you elaborate on exactly what was caught in internal testing?by geekone
5/4/2026 at 11:40:15 PM
I don't really understand this. There was a known bug and it was shipped anyway? I must be misunderstandingby xenago
5/3/2026 at 9:30:11 AM
It got to production because they wanted it.> This seems hard for me to believe. I expect more from Microsoft.
Those are some baseless expectations given the entire company's history
by PunchyHamster
5/3/2026 at 3:37:53 PM
Expecting more from Microsoft is the new showing-my-age: of being born in this century.by noisy_boy
5/3/2026 at 11:59:34 PM
I saw a lot of "they made a game I like (Halo), therefore they must not be that bad" from the gaming cloud that only experienced the console side of itby PunchyHamster
5/3/2026 at 1:45:15 PM
Also, who/what group is pushing for this change internally and what is the opinion of the team implementing it? What is the road map and vision for AI in VSCode?by marricks
5/4/2026 at 12:16:44 AM
[dead]by sorry_outta_gas
5/3/2026 at 1:36:36 AM
I think there’s a few of us who appreciate you being up front. I’d question the intent and why it was a mistake, especially when the commit[0] message reverting said functionality states “widespread criticism” citing this very HN article makes it look seemingly like the revert is due to negative PR opposed to a mistake.[0]https://github.com/microsoft/vscode/pull/313725/commits/1e70...
by jamesbfb
5/3/2026 at 1:52:10 AM
Author of that PR doesn't seem to be a Microsoft employee. Keep in mind that anyone on GitHub can create PRs against VSCode.by l2dy
5/3/2026 at 2:18:35 AM
Author is absolutely from Microsoftby beardbandit
5/3/2026 at 2:44:13 AM
The linked revert PR is not from Microsoft (and also isn't merged)by kllrnohj
5/3/2026 at 4:31:59 PM
It is mergedby politelemon
5/3/2026 at 7:00:52 PM
dmitriv recreated in a separate PR and merged that. The linked revert PR by a user was closed.by PinkSheep
5/3/2026 at 7:20:07 AM
Yep - Says he's got a Microsoft.com email address:> "feel free to reach me directly (my alias @microsoft.com) or"
by ncr100
5/3/2026 at 2:07:58 AM
Even if that would be so, the person who approved it certainly is.by lightdot
5/3/2026 at 4:08:58 AM
The PR linked to in https://news.ycombinator.com/item?id=47992431 is not yet approved as of May 3 4:08 GMT.by asdfasgasdgasdg
5/3/2026 at 7:05:09 AM
I am reverting it because there are bug in the feature and it obviously does not work as expected. Any feedback is important, HN or not.by dmitriv
5/3/2026 at 7:46:21 PM
So, you're reverting because of "bugs", not because you had massive backfire? Do you understand that no one wants this, right?by liendolucas
5/3/2026 at 6:42:55 AM
My issue with this: if my intention is to never have these "co authored by <tool>" trailers in my commits, this is a sudden breaking change. What's worse, it is not immediately visible to the user. Now I could look like I use a not-company-approved AI. That's absolutely unacceptable, this could cost people their jobs. The "bug" (or "metrics boosting feature", as PMs call it?) that it claims all commits including ones never touched by Copilot are just icing on cake.by PufPufPuf
5/3/2026 at 2:08:46 AM
Changing the default behavior for all of your users with no notification is pretty unforgivable. Even if this feature worked correctly, it obviously doesn’t, this should at minimum be a prompt after upgrade to let the user confirm that this is what they want. But honestly should be opt in for those that want it.To have it silently just start adding marketing copy to git commit messages is pretty bad. To have that added text not be visible to the user in the UI so they can remove it before commit is just much worse.
This kind of thing being released speaks to a greater disfunction over there. Not a good look at all and I am not a Microsoft or AI hater. But my commit messages are not where you move fast and break things
by alemanek
5/3/2026 at 2:37:41 AM
Well, the good news is commit messages are some of the most visible thing, and there are no silent modifications that are really possible.The bad news is - where else have this happened in VS Code?
- A happy user of (n)vim
by Aperocky
5/3/2026 at 2:19:07 PM
> Well, the good news is commit messages are some of the most visible thing, and there are no silent modifications that are really possible.The problem is that it's only visible after committing, it doesn't seem to show in the integrated git view when you prepare the commit.
by echoangle
5/3/2026 at 6:56:18 AM
> Changing the default behavior for all of your users with no notification is pretty unforgivable.I noticed that as soon as you make a bug report/feature request on VSCode's repo, you instantly get someone's OpenClaw agent with an automated pull request that sometimes wants to change defaults in the main codebase
Looks like AI is really trigger-happy with that, with zero understanding or care that there's thousands of users affected and it's not just one individual's settings.json
Also, the hallucinated PR does not necessarily address the original issue whatsoever, just like this PR. It should have functionality to detect AI-authored code, but whoever made the PR skipped actually doing the hard work and just changed a default to always on, exactly the kind of misunderstanding you see with OpenClaw shotgun PRs
by Aerolfos
5/3/2026 at 8:04:36 AM
And then they apparently posted an alibi "I'm sorry" here. Or maybe it is genuine, but the choice is between incompetence and fake "I'm sorry". Where is QA?by zelphirkalt
5/3/2026 at 8:20:33 AM
As far as I know VSCode doesn't really have QA. I'm not sure it even has tests, which makes it very surprising that it works as well as it does!by IshKebab
5/3/2026 at 9:55:12 AM
Because it is dogfood?(Meaning the devs use it themself, that is great incentive to fix things)
by lukan
5/3/2026 at 7:05:01 AM
> To have it silently just start adding marketing copy to git commit messages is pretty bad. To have that added text not be visible to the user in the UI so they can remove it before commit is just much worse.This is one of the problems, but it is not only one. To be better, should be:
1. It should be visible in the UI for entering the commit message, to make it clear what it is doing.
2. It should not add such a thing if the Copilot is disabled. (It is mentioned by dmitriv and would hopefully be fixed soon enough)
I do not use Copilot nor any other LLMs nor VS Code, but if the problems are corrected then I think the feature would probably be reasonable.
by zzo38computer
5/3/2026 at 7:39:27 AM
Agreed on both points. Having it shown before going into the commit would let the developer decide whether they want it. #2 is fixed in my PR.by dmitriv
5/3/2026 at 9:01:17 AM
Thank you for being upfront and engaging with us on this. This was a breach of trust, but your engagement here is commendable.by adastra22
5/4/2026 at 2:58:08 AM
You're giving a lot of credit to a one day old anonymous account.by b40d-48b2-979e
5/4/2026 at 6:30:39 AM
I have no reason to assume this is not Dmitriy Vasyura.by adastra22
5/3/2026 at 9:41:36 AM
> Changing the default behavior for all of your users with no notification is pretty unforgivableHow else is a poor programmer gonna hit their KPIs and get that promo?
by imron
5/3/2026 at 4:06:28 AM
"unforgivable" is a little melodramaticby someguynamedq
5/3/2026 at 7:52:09 PM
No, it's fine. I really hope that more people will switch to something else, like Neovim, Emacs, or any other open-source editor where such unacceptable situations are practically impossible. I hope more people will start to value their privacy and right to choose, and find the courage to say gtfo and switch to something else. Because this is unforgivable.by allarm
5/3/2026 at 8:19:53 AM
please no more popups on vscode, im begging youby lucas_t_a
5/3/2026 at 4:39:13 PM
It really is a problem, across Microsoft as a whole. I had to ditch VS after the constant popups finally pissed me off enough.by Pay08
5/3/2026 at 2:31:02 AM
[flagged]by dakolli
5/3/2026 at 8:41:46 AM
> Changing the default behavior for all of your users with no notification is pretty unforgivable.What does that even mean? The git log exists. Do you mean they should shove the entire git log in the face of every user on every update?
Obviously this change was a massive fuckup, but that sentence makes absolutely no sense.
by boxed
5/3/2026 at 2:11:06 PM
It just means that when changing a global default with such impact the user should be prompted with an option to opt out of the new behavior. Something like “AI assisted changes will now have ‘coauthored by Copilot’ added to the commit message”. If the user clicks “no thanks” it changes their local setting to “off” to opt them out of this new global default.by alemanek
5/3/2026 at 3:06:00 AM
Don't you understand that the default shouldn't be changed at all in this case? It improves nothing and affects every single user. If an org/project wants this behavior then it can enforce this flag for its contributions. The only valid reason for this change is someone's performance somewhere in Microsoft is dependent on VS Copilot usage metric.by anvuong
5/3/2026 at 7:44:37 AM
Good feedback, there needs to be a more explicit opt-in into this for teams that want it. FWIW nobody's performance here will improve from having this metric :-)by dmitriv
5/3/2026 at 7:54:41 PM
> FWIW nobody's performance here will improve from having this metricIt's even more frightening if so. Meaning you really thought it's something users wanted.
by allarm
5/3/2026 at 2:22:41 AM
Interesting case:- a project manager vibe-coded the change without thinking it through at all
- the PR was reviewed by an LLM
- an actual engineer gave LGTM without really reviewing the changes, trusting the LLM
Did I get this right?
by kgeist
5/3/2026 at 4:25:13 AM
>a project manager vibe-coded the change without thinking it through at allThe PMs vibe-coding and having no idea what they're doing isn't even the main issue (although it is pretty bad).
The main issue is: how are the actual engineers supposed to "review" the slop? They probably report to the same PM or are at below in the org chart and might be evaluated by them. Not just at MS, but any company.
Such a conflict of interest would be detrimental to quality anywhere. You wouldn't build a bridge like this, nor should you software.
by throwaway277432
5/3/2026 at 10:14:32 AM
The revert commit appears to have also been done by copilotby duskdozer
5/3/2026 at 4:42:18 AM
You can't make this shit up.by strix_varius
5/3/2026 at 3:24:22 AM
The LLM actually points out the problem thoby teg4n_
5/3/2026 at 3:39:39 AM
Maybe the engineer's LLM agent's summary of the GitHub LLM bot's review omitted that warning.by isityettime
5/3/2026 at 7:03:55 AM
Maybe the GitHub comments didn’t properly load due to the weekly partial outage.by herrherrmann
5/3/2026 at 1:41:39 AM
Why does the commit editor hide the coauthored message? Why not pre-populate the text field and users take or leave it when committing?by schwede
5/3/2026 at 9:27:48 AM
I think this is a good point - perhaps there should be some commit-time UI which would let the user make the choice. Thanks for the suggestion!by dmitriv
5/3/2026 at 2:53:38 AM
Co-Authored-By is normally a trailer, and trailers aren’t part of the commit message. It’s likely the commit editor isn’t set up to show trailers. They’re not exactly obscure, but it does seem that they’re relatively unknown.by jdlshore
5/3/2026 at 4:16:13 AM
What do you mean they aren’t part of the commit message? Trailers like (signed off by) are absolutely part of the message. Tools can choose to treat them as special metadata, but they’re part of the commit.The docs for the function to interpret trailers even says this explicitly: https://git-scm.com/docs/git-interpret-trailers
> Add or parse structured information in commit messages
by mplanchard
5/3/2026 at 4:54:52 AM
I mean that they’re not necessarily part of the --message parameter to `git commit`, but instead part of the --trailer parameter. I don’t know how VSCode is programmed, but it seems plausible that trailers are handled separately from the message parameter.by jdlshore
5/3/2026 at 10:20:25 AM
We're talking about Git here. The question is not "how VSCode is programmed", the question is "does Git have a special field for commit trailers". The answer is no. Git stores the trailer as part of the commit message.by baobabKoodaa
5/3/2026 at 2:55:02 PM
If you look at the comment I’m responding to, it is in fact about how VSCode is programmed; specifically, a possible reason why the Co-Authored-By trailer doesn’t show up in VSCode’s commit message box.by jdlshore
5/6/2026 at 5:20:59 AM
It seems like it would be most reasonable to consider porcelain vs. plumbing command details in deciding if something is logically distinct to Git. git-commit has --message and --trailer options, git-commit-tree has a --message option. I take that as trailer is a convenience option to provide a consistent way to append those details to the commit message. But that doesn't mean it's not part of the commit message, nor that the user shouldn't see it while reviewing the commit message.by opello
5/3/2026 at 12:58:56 AM
I appreciate you acknowledging that this was a mistake, but as you surely know from your own experience with other people’s mistakes, some mistakes are so egregious that they cast doubt on the intentions of the people involved even if they are corrected later.To me, “let’s add false attribution to every commit by default without informing the user” falls squarely into that category. I don’t think I’ve ever worked in an environment where something like that wouldn’t have been red-flagged in three seconds by anyone who took even a casual glance. I’d honestly be embarrassed if such a proposal even made it into a public pull request for my organization, nevermind that pull request getting merged.
by p-e-w
5/3/2026 at 6:44:17 AM
If what you described would make it to our PR queue, it would definitely not pass the gates.The idea was to track AI-only changes and add the trailer when such changes were detected AND the setting was enabled. Obviously, we didn't want to attribute all changes to AI. There is a bug in change detection (which slipped through testing), which led to even non-AI changes being tracked. And thus we have this problem.
The PR linked here wasn't even implementing the feature, it was changing the default for the setting.
by dmitriv
5/3/2026 at 9:39:19 AM
> (which slipped through testing)In another comment you say you caught it in testing and didn't think it needed fixing, which is it?
by detaro
5/4/2026 at 5:45:35 AM
>If what you described would make it to our PR queue, it would definitely not pass the gatesIt just did though. Did you approve the PR without actually looking at the code?
by fastasucan
5/3/2026 at 6:32:14 AM
I just wanted to say, while I think this feature was a bad idea, I sincerely applaud your willingness to post here, knowing you'll get roasted. Seriously brave and commendable.by freedomben
5/3/2026 at 7:18:11 AM
They pretended to be fronting up but didn’t respond to anything after that. Doesn’t seem very commendable to me.by galonk
5/3/2026 at 8:19:56 AM
Other people aren’t your slaves. You don’t get to demand they respond immediately, and this Reddit-like mindset needs to die. HN is a place where we often can actually get devs from companies responding directly and listening to feedback, and this hostility is looked at by all the other devs from those similar companies and remembered when it’ll be their turn.Stop making HN a worse place for everyone by being unnecessarily hostile. (and this comment is only mildly directed at you but rather at a bunch of people in this thread)
by scrollaway
5/4/2026 at 2:41:27 AM
They said three times "ask me anything" and then didn't respond to a single question. Stop making HN wose by comparing someone dodging accountability to slavery.by galonk
5/3/2026 at 9:24:46 AM
Someone made a mistake, owned up to it and fixed it. No one is entitled to more than that for a free software.Anyone with a bit of software experience knows it’s easy to miss things when you are doing your own tasks + context switching + giving reviews. We should exercise kindness and empathy instead of projecting evil intentions.
by _waqas_ali_
5/3/2026 at 10:18:20 AM
> Someone made a mistake, owned up to it and fixed it. No one is entitled to more than that for a free software.Funny how these "mistakes" only seem to happen in ways that align with the agenda of the supposedly non-evil corporation.
by saghm
5/3/2026 at 12:14:36 PM
Not sure about the other “mistakes” but this one is way too stupid to be evil :) Hanlon’s razor applies pretty well here.Pretty sure no one thought “let’s add a lie to every commit and hopefully no one minds. Free Marketing yay!” at Microsoft.
by _waqas_ali_
5/3/2026 at 2:44:13 PM
Even if I accepted the premise that this is too stupid to be evil, that doesn't change the fact that this would be extremely easy to test for. The fact that they considered it important enough to get this feature implemented without proper testing says plenty about their incentives.They might not have intentionally done this (although it's honestly not clear), but they definitely didn't care enough to prevent it because it wouldn't have been hard at all. That's my point here; which bugs slip through and which don't implicitly conveys what their priorities are. I don't think it's particularly hard to infer what story this bug tells.
by saghm
5/3/2026 at 2:03:56 PM
IDK, I heard way stupider and less ethical ideas at work.by FeistySkink
5/3/2026 at 7:36:13 AM
That's a good point, let's see if they come back and respond. It is the middle of the night in the US so they may be sleepingby freedomben
5/3/2026 at 7:41:53 AM
It is the middle of the night and I am responding. Anything specific you'd like me to respond to?by dmitriv
5/3/2026 at 8:51:26 AM
https://news.ycombinator.com/item?id=47992781by jdenning
5/3/2026 at 9:26:49 AM
First comment does not sound constructive - are you interested in my opinion on (n)vim?I am not a legal, so can't comment on legal things. However, I have already responded elsewhere here that this feature has nothing to do with licensing or ownership and was added for those that want the attribution. I understand the desire to see anything Microsoft as bad and evil, but we are really just trying to make a better experience.
I'll respond to the third one, thanks!
by dmitriv
5/3/2026 at 1:23:37 PM
Perhaps next time you should consult with legal before asserting co-authorship on end users’ code. The appended comment was not “edited with VS code” or “sent from VS code”, it was “co-authored by Copilot”. You do understand that there are legal implications to claims of authorship, right?by jdenning
5/3/2026 at 7:06:58 PM
To be honest, this question should be directed at the person who made the change/commit:> cwebster-99 / Courtney Webster / Product Manager at @microsoft working on VS Code and GitHub Copilot!
>> No description provided.
by PinkSheep
5/3/2026 at 11:20:31 AM
It was pretty obvious from your first comment that you were going to get creative with the definition of "constructive".> are you interested in my opinion on (n)vim?
The first comment is three short lines. One of them is the extremely reasonable and relevant question of where else this has happened in VSCode.
And you think that the commenter is wondering about your opinion on (n)vim? That is what you think they are interested in?
Could you just, like, ignore the signature if it is distracting you from the only other line that has a question in it?
by albedoa
5/3/2026 at 1:17:22 PM
Comments like this are why developers don’t engage directly. The first link is “just asking questions” and implying that the project is rotten. He’s not being “creative” he’s just not engaging in bait.by maccard
5/3/2026 at 4:40:41 PM
They’ve done a commendable job responding. Please show some respect when people put themselves in vulnerable situations, otherwise the whole “devs respond on HN” thing will cease to happen.by HDThoreaun
5/3/2026 at 9:30:25 AM
I noticed you only respond to comments that are positive (or neutral). The majority (and the most insightful) comments here are negative, but you seem to ignore them.by 400thecat
5/3/2026 at 8:04:15 AM
their comments are dead, probably related to it being a new accountby gizzlon
5/3/2026 at 9:28:51 AM
I really did create a new account to respond :)by dmitriv
5/3/2026 at 11:46:39 AM
Why are you taking the fall and not the PM who authored the change (and submitted a PR with an uninformative title and no comment) and, I'm assuming, plays a role in managing the project?by snet0
5/3/2026 at 4:00:45 AM
Just for any future mea culpa, I'd recommend not hedging with comments like this one:> As folks mentioned here - many similar tools do this as well.
It's really doubtful they have the same behavior people are complaining about here: namely including the authored by Copilot statement when it wasn't used (or even enabled).
by nsagent
5/3/2026 at 4:26:41 AM
Anthropic does by default. I had to put “no co-authored by lines in commits, ever” into my global settings.That’s pretty close to “included when it wasn’t used (or even enabled)” since it’s opt-in by default and you have to explicitly say no. It’s not even clear where to turn it off, I just rely on the AI to figure out not to do it.
by sillysaurusx
5/3/2026 at 8:07:15 AM
Maybe I misunderstand you, how is Claude doing commits where you don't use Claude?That is a very different case to VS Code which is something you can in fact use without Copilot.
by jstanley
5/3/2026 at 10:00:41 AM
That is not what dmitriv claimed. He said this was a bug, the behavior should have been to add it only when AI was involved, which indeed, is what claude does by default.(Both is not fine with me)
by lukan
5/3/2026 at 3:47:28 AM
> I am open to any (constructive) comments/suggestionsHere's one:
I think a senior sysadmin needs to sit you down in their office and have a very serious talk with you about the responsibility that comes with writing code other people run. I am serious. We used to have these talks with everyone who got sudo access. You shouldn't be shipping code if you don't understand the trust that is required of people in your position.
This isn't just about this "feature" being active when AI features are disabled, the way you mis-implemented this has resulted in it modifying the commit message with the user even seeing it! That is malicious behavior, not an innocent little feature "to make life easier".
I've fully switched off of VS Code to Kate now, which is faster and better behaved in most cases anyway. Bye.
by solid_fuel
5/3/2026 at 4:19:27 AM
To be fair, looks like a PM vibe coded it and this person “just” gave it an approval with no comments after an LLM review.by mplanchard
5/3/2026 at 4:43:45 AM
To be fair, that makes it worse for MS, not better.This should not be vibe-coded by someone who has absolutely no idea about any of these things.
by throwaway277432
5/3/2026 at 12:20:50 PM
Oh yeah sorry, I was being sarcastic. I think it’s hilariously bad, but I also avoid MS products like the plague as a rule.by mplanchard
5/3/2026 at 3:51:14 AM
He makes more money than you and you’re responding to his ai chatbotSeethe
by ATMLOTTOBEER
5/3/2026 at 8:39:26 PM
There’s more to life than money, child.by solid_fuel
5/3/2026 at 8:40:30 AM
What is the use-case where you expect users would be happy that you modify their commit messages with MS marketing? Do you think it would be ok to edit every commit to append “written with VS Code”?by jdenning
5/3/2026 at 9:31:33 AM
MS would absolutely do that if they could get away with. Hell, you'd get azure promo code with itby PunchyHamster
5/3/2026 at 2:57:46 AM
thank you for doing this, it gave me the push I needed to finally switch to zed. vscode has really been going downhill for a while now. it's sad to watch, it used to be a really nice editorby jbxntuehineoh
5/3/2026 at 8:10:24 AM
- A qualified sorry for one particular aspect of this- It wasn't our intention
- Our users asked for it [you'll have to take our word for it]
- Everyone else is doing it anyway
- Statement that I am reasonable and will be co-operative with the community but with conditions
That's a bingo!
by gib444
5/3/2026 at 1:59:49 AM
> a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated codeLiterally who?
by nhinck2
5/3/2026 at 3:26:34 AM
I could easily see companies, especially enterprise-level companies, expect code that was generated with AI to have some level of ownership attributed to that AI. Whether a simple "Co-Authored-by Copilot" byline on the commit is the right way to do that is another question though.by JoRyGu
5/3/2026 at 7:46:19 AM
Correct, this was the ask.by dmitriv
5/4/2026 at 2:24:13 PM
And thank you for this. In my professional setting, this is a very valuable addition -- provided it works correctly, of course ;-).Now if we could also have comments inside the code ("BEGIN/END snippet by Copilot"), that would also be great!
by zvr
5/3/2026 at 3:17:41 AM
No one, which is why he refuses to reply further to any of these inquiries.by IAmGraydon
5/3/2026 at 7:46:39 AM
I don't refuse - what would you like to ask?by dmitriv
5/3/2026 at 8:08:53 AM
they do, at least to some degree, but their comments are dead. You'll see them if you turn on show-dead somewhereby gizzlon
5/3/2026 at 6:28:02 AM
> There was no ill intent by evil corporationI simply do not believe you
by wren6991
5/3/2026 at 8:10:30 AM
It’s true. There was no ill intent, just a system of incentives that not only permitted but encouraged it.by nicbou
5/3/2026 at 7:48:21 AM
That's ok :-)by dmitriv
5/3/2026 at 8:07:43 AM
> There was no ill intentOnly callous disregard for your users
> many similar tools do this as well
But since we have normalised that, it’s okay?
by nicbou
5/3/2026 at 2:00:32 AM
Thanks for facing this head-on here; mistakes happen.I think the default to on should also be reconsidered regardless. The assessment (co-authored by AI) may be valid but the assumption the user wants that advertising is exactly that, an assumption, and a dubious one at that.
by mellosouls
5/3/2026 at 7:48:07 AM
Thanks. Done here: https://github.com/microsoft/vscode/pull/313931by dmitriv
5/3/2026 at 1:58:40 AM
> There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code.What metric did Microsoft use to assess that VS Code users "expect" their commits to have unsolicited messages added to them?
> Obviously, it should not be on when disableAIFeatures is on and it should not be reporting changes that were not done by AI.
Did you discuss adding these messages with your legal department?
What is Microsoft's position on adding such authorship statements to the code Microsoft did not author?
Or is Microsoft stating that using LLM assistants makes Microsoft a co-author of the code?
Does Microsoft have copyright claims on the code if LLM assistants are used at any time during its creation?
by lightdot
5/3/2026 at 8:46:02 AM
I would also really like to see answers to these questions. This change explicitly claims that MS co-authored the commit.by jdenning
5/3/2026 at 4:55:53 AM
> There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well.Then make it an extension, not a IDE-behaviour thing. Is that so complicated, so difficult?
by captainepoch
5/3/2026 at 7:47:29 AM
It would be tricky, yes, since it depends on core editor functionality which is not exposed through the API.by dmitriv
5/3/2026 at 10:23:58 AM
So why did this feature get rushed out without proper testing? Are you claiming that not having this happen automatically for the commits where Copilot actually co-authored them is so urgent that it was necessary?I'd argue that this was extremely non-urgent and the fact that this got rushed so sloppily is a giant red flag about the priorities of you and your team. You asked about constructive criticism, and yet you're also acting like this is a one-off innocent mistake by only addressing what you've done to roll this back for now and address the immediate issue. I don't buy the premise that we could trust that this was a mistake made in good faith when it's something that you clearly should have known people would be so upset about if you got it wrong.
by saghm
5/3/2026 at 9:13:50 AM
Considering the size (and significance) of the VSCode user base, it feels like someone should be in charge of ensuring that default behavior doesn't change without good reason.Does anyone (or any team) have ownership of the extensions/git/package.json file?
by DavidVoid
5/3/2026 at 8:33:30 AM
> There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code.Can you expand on this? Who "expects" their code editor to lie about using Copilot?
by macic
5/3/2026 at 8:43:06 AM
The supposedly expected functionality is very obviously that it marks copilot co-authored code as copilot co-authored, not the bug that is being reverted.by yreg
5/3/2026 at 9:29:50 AM
Correct.by dmitriv
5/3/2026 at 6:15:51 PM
> a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated codeThis isn't enough. What was the _full train of thought_ for this? Why would it be added when AI isn't used?
by kevinmgranger
5/5/2026 at 1:57:53 AM
FYI - we have posted update on the subject with more details, links and analysis here: https://github.com/microsoft/vscode/issues/314311Hopefully this answers some more of the questions raised here. It also incorporates a lot of feedback from this thread with respect to next steps (thank you!).
by dmitriv
5/3/2026 at 6:51:25 PM
Under which circumstances can you ever approve something like this?This goes beyond incompetence. Either you do not understand what important information a commit holds or what seems way more plausible to me is that Microsoft simply decided to try this out and see how people would react.
> There was no ill intent by evil corporation...
I will ever in my life buy that from Microsoft.
by liendolucas
5/3/2026 at 2:27:55 AM
Have it as an add-on said customers can add. Opt-in, not opt-out. No AI without consent.by teunispeters
5/3/2026 at 7:48:44 AM
Switched back to opt-in here: https://github.com/microsoft/vscode/pull/313931by dmitriv
5/3/2026 at 8:31:14 AM
Changing a global default this way is hugely disrespectful to users.As a result I’ll be uninstalling vscode from all my machines, I’m tired of disabling things in vscode I didn’t ask for especially in regards to AI.
There are open source tools that clearly respect users more and have a track record of not doing these kinds of stupid things.
Be better.
by noir_lord
5/3/2026 at 10:09:45 PM
Whether or not the intent is good, the optics are extremely bad.I assume you are keenly aware that Windows, Office, and by extension, all of MS's customer facing products are not exactly regarded particularly well. Windows 11 specifically is a laughing stock today, even among folks who don't necessarily know computers, and a lot of that resentment is driven by 2 things:
• Pushing AI everywhere when no one asked for it. • Not reading the room and adding junk features that no one wants.
This change is both of those, again, wrapped up in another package. The timing of this is extremely bad for VS Code as a project as it looks an awful lot like, 'Microsoft is just shoving my AI junk into my stuff and failing to work on the features we actually want'.
I'm not taking a side on this either way as I will jam a fork into my eye before I use VS Code over VS proper and have no stake in this, but I'm just saying that the powers that be that are approving these kinds of changes are ~continuing~ to fail to read the room.
I'll add as someone who may be forced to consider VS Code in the future (Depending on if Windows unfucks itself before something critical breaks for me on W10), I would read something like that and I think rightly assume bad intent. I know VS Code and VS and Office and Windows are not the same team, but again, MS as a whole has a very serious optics problems and my read of this on the surface level is: "Oh, they tried to sneak in more AI junk, and when called out on it, they pushed it to the back, probably to make it a default again in some future update that they can hide it in". It just looks very, very bad at a time when no MS products have negative social capital to spend on this kind of stuff.
by Kadecgos
5/3/2026 at 1:12:55 PM
I appreciate your willingness to come and try and salvage this situation. What I don't understand is why are you the one doing this here and on GH, during the weekend, and not the PM who created the original PR? Surely they have some input.And another thing is, why was there absolutely no pushback from your part on any of the issues with the original PR, and why it was merged within hours in that state?
by FeistySkink
5/3/2026 at 7:46:51 PM
Respectfully -You are working for one of the largest companies on the planet. You push code that gets used by millions of people.
How on earth are you not thoroughly testing your changes??? How can something like this slip into a real build? Like, this is egregious.
I work somewhere that makes software for a lot of users (although not as many as Microsoft!). We also need to ship quickly. But we work on a 45-day cycle, with 15 of those days being dedicated to ensuring we didn't add any awful bugs (and fixing them ASAP before it goes to users - or reverting the change until it is ready).
I would expect Microsoft to have AT LEAST that amount of care. We can't trust that you are shipping software that even works anymore!
What other changes are going in that are broken in more subtle ways? It used to be that VS Code was rock solid, and any issues were likely third-party extensions - but now it's a crapshoot, and I can't be sure if crashes etc. are the fault of extensions or Microsoft themselves!
The VS Code team needs to use this mistake as motivation to lead the charge on making a quality editor. Not an editor that gets half-baked, untested changes pushed weekly. An editor that is dogfooded and where a mistake like this going to prod is unacceptable.
Because if you don't, people won't trust your editor anymore. Just like people have stopped trusting your OS, and now users are fleeing it in such numbers that the Windows team has recognized they have a problem and are changing course.
That WILL happen to VS Code and GitHub soon unless you actually start owning mistakes internally and fixing them before users find them.
by EnglishMobster
5/3/2026 at 10:12:35 AM
> There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well.Please elaborate on what "similar tools" claim that commits are co-authored by AI when the AI features are all turned off. You're trying to defend the theoretically correct version of this that you didn't make, not the actual version you did make.
> I am open to any (constructive) comments/suggestions
It's hard to take this seriously; you know exactly what you did wrong here and what you should have done instead. Testing that this doesn't happen when Copilot was not used is extremely trivial; if you're not lying about it being unintentional, the fact that it didn't occur to anyone to do it still says more than enough about what the priorities are here. At absolute best, the priorities of you and your team are so fundamentally wrong that it's impossible to trust any of you going forward.
by saghm
5/3/2026 at 3:05:29 PM
I feel like many replies are missing that this is satireby outlore
5/3/2026 at 3:09:01 PM
What makes you say that?by BatmanAoD
5/3/2026 at 3:29:26 PM
At a hackathon for my school recently a MS employee was a judge.ALL he wanted to tell me was that I should give VSCode another shot: "It's good now".
You can't blame the dog, only the environment surrounding the dog.
by 4b11b4
5/3/2026 at 4:01:19 PM
Calling people dogs by analogy is not great.That aside, corporations and groups don't make decisions. People do. We can understand and empathize with what led them to that decision (and sometimes we might be looking at the wrong person), but they're still responsible.
by NegativeK
5/3/2026 at 8:19:27 AM
Rule of thumb, such features should always be Opt-Inby croes
5/3/2026 at 8:28:59 AM
First, revert the commit, then apologise.by grey-area
5/3/2026 at 9:33:52 AM
I did both, didn't I? :-)by dmitriv
5/3/2026 at 2:46:03 PM
At the time of writing it wasn’t reverted, but thank you for replying.by grey-area
5/3/2026 at 4:23:49 PM
I rarely comment on HN threads, but in this case big respect for coming out and owning the mistake, keep that shit up.If more people from MS had the guts to actually talk to their users, I'd probably have a lot less to complain about at work ¯\_(ツ)_/¯
Hopefully there's some good lessons to improve the process, not just feedback for this single incident.
by CosmicBagel
5/3/2026 at 6:18:55 PM
Thank you for your honesty, this is pretty brave.On the other hand...this feels like a situation where possibly you should not have said anything at all? The fact that you're on HN responding feels ill-advised to me.
So far this is what I've gleaned:
- Microsoft has PMs vibe coding against VSCode (by itself not necessarily a big deal)
- Microsoft PMs can vibe code against VSCode and get stuff shipped to production with only a single approval
That second one is a huge deal in my book. What I've learned now is that VSCode, a product with an enormous deployment base, is trivially compromised if the calls are coming from inside the house. Apparently all that has to happen for all users to be affected is a PM requesting you to "please approve my PR real quick, trying to get it in." And now there's a massive change in the wild, visible to many users.
Being familiar with big corp dynamics, this really worries me. This does feel like a not-well-thought-out mistake but I can easily imagine many other scenarios that would be far worse.
How can I trust VSCode going forward? How can I reassure my employer and fellow colleagues that it's safe to use? This is really a terrible look for Microsoft and very damaging to the reputation.
I feel bad for you the engineer and PM here because with the web being what it is, folks are casting blame onto you. That's missing the point since the issue is that MSFT even let this happen in the first place. Engineering processes need to be halted and re-evaluated basically yesterday. If something like this happens again it may not be possible to rebuild the trust at all.
I hate to say it but for myself this issue makes me strongly consider switching away from VSCode permanently, something I had not seriously considered before yesterday. Best of luck to everyone on the VSCode team.
by _doctor_love
5/3/2026 at 3:33:50 AM
[flagged]by LandoCalrissian
5/4/2026 at 3:06:11 AM
"Please don't fulminate."Not saying you owe $BigCo better, but you owe this community better if you're participating in it.
by dang
5/3/2026 at 6:02:50 AM
Just disable everything AI by default bro.by ares623
5/3/2026 at 7:27:22 AM
Nobody wants this shit. There is no timeline where developers want junk inserted into their commit messages.by Gud
5/3/2026 at 6:54:09 PM
One of my customers actually requires attribution to agents if they're used, not only for tracking purposes but also for understanding potential vectors for slopcode. It's been useful and occasionally enforced. That being said, implementation without due consideration and warning should be frowned upon.by benchwright
5/3/2026 at 1:54:20 AM
[dead]by jibal
5/3/2026 at 2:06:11 AM
Brave man. RIP your inbox.by aaaronic
5/3/2026 at 8:26:53 AM
You're an idiot.But I'm an idiot every day too, so I can relate. We can only learn from these mistakes, keep it up!
by rf15