One fascinating thing about the whole AI phenomenon is how incredibly hostile it is to _standards_. Whether something works properly, or is ethical, or is true, no longer matters at all; all that matters is "pls use our AI".
Microsoft spent literal decades rehabilitating their reputation. And then set fire to the whole thing in an offering to their robot gods.
And it's not just them. There was a time that Google cared deeply about UX. Now, on macOS Google remaps CMD-G in Google Docs to launch some LLM bullshit (EDIT: huh, they may have fixed this; it was definitely doing it a couple of weeks ago), because, after all, it has only had a standard universal meaning on macOS for about three decades, no big deal.
yankohryesterday at 9:36 PM
This feels like the modern version of 'Sent from my iPhone' but much more invasive. Git commits are legal and technical records. Falsifying who authored a piece of code just to pump up AI usage stats is a huge breach of trust and it is disappointing to see Microsoft prioritize branding over the integrity of the developer's log.
I expect my IDE to record what happened, not what the marketing department wants people to think happened.....
dmitrivtoday at 12:06 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.
ddktoyesterday at 9:20 PM
The best part is that copilot commented on the PR saying that this doesn’t actually change the behaviour, creates inconsistency in the codebase and suggested reverting the change! (This comment seems to have been ignored…)
> The configuration schema default was changed to "all", but the runtime fallback in extensions/git/src/repository.ts still calls config.get('addAICoAuthor', 'off'). This is now out of sync and can lead to unexpected behavior in contexts where the contributed configuration defaults aren't loaded (e.g., some tests/hosts), and it makes the intended default unclear. Update the runtime fallback to match the schema default (or omit the fallback so the contributed default is used).
artyomyesterday at 10:27 PM
To everyone who bought the "developer-friendly" Microsoft of VSCode fame from a few years ago: this is what they forever did, and forever will do.
This company has been pulling these tricks since the early 90s.
If you fell for this once again, there's nobody else to blame but yourself.
dsigntoday at 5:58 AM
This is bad. I need to start Monday warning my team about this and installing validation hooks in our repos that catch any commits with this. We don't have a non-AI policy, but we have an "approved AI" policy due to data security, and having all your commits say "Co-Authored-by Copilot" is more or less the same as as "I ** on infosec". We also have a "short commits message" policy, and that "Co-Authored" thingy takes characters.
"Sent from my iPhone" marketing only works if people want everyone to know they're using the product.
mister_mortyesterday at 9:11 PM
This is pumping someone's metrics up inside of Microsoft, somewhere.
The question is - will their boss revert it or encourage it when they discover the source of the stats being juiced?
low_tech_loveyesterday at 9:09 PM
Isn’t this a kind of “leopards ate my face” situation? I thought we had all “agreed” that letting AI write code and take control of software repositories is good, even if we have no idea what is going on beyond a thin surface layer, because well it’s fast and we can fix it later and lol who needs testing? My customers are my testers.
And now it’s suddenly bad because the developer is the customer?
albert_etoday at 11:37 AM
Question -- is this a general feature that detects which AI agent was used to edit your code (Claude, Codex, etc) and inserts THAT agent's name into the commit message's trailer. Or this pnly detects and inserts (Github) Copilot as a co-author?
amarantyesterday at 9:09 PM
Microsoft is such a master class in how to make me hate you, quickly.
mrcartmenesesyesterday at 8:49 PM
Next it will be Co-authored by Co-Pilot with help from Dominos Pizza
lagniappeyesterday at 11:57 PM
microsoft locked as spam and limited conversation to collaborators 6 minutes ago
digitaltreestoday at 12:28 AM
This is especially hostile to users given that courts are ruling that AI written code can’t be copyrighted.
When Hotmail inserted “sent using Hotmail” in emails as a growth hack it didn’t have legal consequences. This might.
albert_etoday at 11:31 AM
Given that there are 536 different types of "Copilot" under Microsoft umbrella, I am surprised they did not distinguish between GitHub Copilot and Microsoft Copilot here.
MkLouisyesterday at 9:23 PM
Jeez, you can see many things wrong with this new all-in AI direction that Microsoft is taking. Commit by a product manager, who probably actually never digged through the code before…automated ai review not catching the problem, and the vibe codes pr introduction the error itself
docheinestagestoday at 1:14 AM
Even large companies like Anthropic and Microsoft keep pushing out features without proper code and/or product review. This has become a bottleneck in software engineering.
cozzydyesterday at 9:06 PM
My newest yocto image mounts a 640K RO tmpfs on top of $HOME/.vscode-server to prevent people using VSCode from shitting all over the relatively small emmc.
csmantletoday at 1:06 AM
The PR author didn't even bother to properly capitalize their subject and add a description. What a double standard for code quality Macroslop is applying to internal vs. external contributions.
ludicrousdisplatoday at 11:31 AM
I wonder what sort of liability this introduces for Microsoft when their 'Co-Aauthored by Copilot' code causes harm.
RandyOriontoday at 1:54 AM
Wow. Just like using ungoogled-chromium instead of chrome, lineage os instead of oem android, using vscodium instead of vscode is again justified. These decisions really are the ones that I'll never regret.
In addition, using the word microslop instead of microsoft is again justified, too.
stodor89yesterday at 9:13 PM
Adding Copilot as co-author: For when just stealing other people's code doesn't cut it anymore.
sandeepkdtoday at 8:15 AM
Interestingly a product manager creates a PR with small but sort of policy change without any backstory/explanation, it gets reviewed by a single developer and merged without a single comment. The bar to make changes to a production software used by so many people has gown down considerably.
sedatkyesterday at 9:14 PM
Search for "AICoauthor" in VSCode settings and turn it off.
throwaway81523yesterday at 9:02 PM
Wonder if they're going to claim copyright interest based on inserting that crap.
bg24today at 12:59 AM
I have been in this situation. A major driving force is some kind of a demand from the leadership to see the KPI for the AI adoption. And this unfortunately is the easiest one to implement.
The other aspect is virality. I think by now the implementing team should know that most people do not appreciate Claud inserting itself into the commit message. It's the job of the team to feed that to the leadership.
quinktoday at 12:22 AM
And here I’m thinking that my text editor should have zero interaction with anything git other than as a diff viewer.
lazygit is text editor agnostic and works brilliantly to give some near perfect porcelain to git specifically. And it works the same with Ghostty, Terminal, zed, VS Code, any environment I happen to be in, while saving so many keystrokes.
tokioyoyoyesterday at 9:39 PM
At no point in time companies were so desperate for developer attention. It feels like the general consensus is it is a “winner takes it all” race, and everyone has to add as many dark patterns as possible to increase stickiness.
If your code is "co-authored by Copilot", does that then allow future AI to train on it without your consent?
b4rtaz__yesterday at 9:06 PM
This is really bad.
golem14today at 1:38 AM
I miss in this whole thread why this is happening. Presumably to be transparent whether code has been co-written by AI?
What's in it for Microsoft?
If we accept that AI can't copyright or own IP rights on something, then why?
I have a sneaky suspicion that there's some lobbying in the works to overturn that ruling going forward. In the past, it was OK to build models from copyrighted data etc one might have found on the wayside. But, in the future, no such thing for you. Everything generated by the AIs will then belong (at least partly) to the megacorps (maybe THEY can co-own the copyright if the AI cannot). Nice pulling-up-the ladder if true.
This could also be a move against other countries' IP position.
I've seen the explanation from dimitriv [1], but I am not convinced. These markings achieve very little, as people can clearly work around it by copy-pasting code from another place, or using other companies tools, like claude code or antigravity (or, not even use the GUI)
I suppose the answer might just be "don't attribute to malice ...", even if Microsoft has proven us wrong before; they generally know exactly what they are doing strategically.
I'm so glad I switched to NeoVim. I've got the good LSP and auto-complete stuff, a nicer grepping experience, semantic moving and selecting with treesitter textobjects, and absolutely ZERO LLM AI stuff. (I still use LLMs outside my editor for some searching and questions, but may try to cut that down too.)
Call me a Luddite, but we are up against something extra insidious with this new AI wave, and the cracks of the psychosis are starting to show.
(Looks like that one never made the front page, so we won't treat the current one as a dupe)
vb-8448today at 1:07 AM
So what's next ... Is this a proof for when they are going to charge you a 30% commission on your sales for products build with their tools?
fhnyesterday at 11:18 PM
I've been hesitant to use Zed mostly because I didn't want to learn new key but last week, I finally jumped in and remapped to keys that I like. It works really well.
rwaksmunskiyesterday at 9:24 PM
Just when you think they've reached the bottom, they just keep digging.
ryan-ayesterday at 9:38 PM
Time to leave for something else if you haven't already, vscode has been good to us but this kind of behavior is only going to ramp up as Microsoft seeks to get a return on their AI investments.
holistioyesterday at 8:56 PM
Whenever I use Cursor's voice dictation, my prompts get "Thank you" inserted at the end of the sentence.
hansmayertoday at 10:48 AM
For the folks who need their IDE but w/o the slop and constant notifications, there is very good public fork called VSCodium: https://vscodium.com/
Not only is it free of MS "telemetry" nonsense, it is also way quieter to use, no bullshit popups for updates etc.
ninjahawk1yesterday at 9:08 PM
Great, here’s how to remove it from your commits:
Run git commit --amend
Your text editor will open. Delete the line: Co-authored-by: Github Copilot <noreply@github.com>
Save and exit
Force push the change: git push --force-with-lease
bravetravelertoday at 9:22 AM
Left with no choice but to add "co-authored with man + ansible-doc" to everything now
djoldmanyesterday at 10:11 PM
Looks like it comes into play for telemetry and here in actual commits:
withing ONE week, Microsoft one-sidedly decided to
1. increase the LLM usage by 20x in Copilot
2. add rate hourly (roughly 4 hours blocks) and weekly rate limits to models use in Copilot
3. introduce credit based billing where you can't roll over unused credits
4. and now inserts themself to the commits as co-author
Man, I really feel like they want us to hate them
yoda7marinatedtoday at 8:34 AM
How long do you think it will take before the Free & Pro plans start showing ads in vscode and its terminal?
i386today at 12:09 AM
PMs at Microsoft have incredibly bad taste
srikanthsastrytoday at 2:16 AM
Determining AI provenance is really tricky and difficult when you have so many different ways to author code.
Looks like VS Code has decided that by stamping all code as AI generated, it is more likely to be right than wrong. Some PM must have declared that false negatives are a lot more dangerous than false positives when it comes to AI provenance tracking
KyleBerezinyesterday at 11:53 PM
quote:
"Thank you all for your feedback, professional or otherwise.
Sorry about the regression. I will work on fixing this in 1.119.
There is a number of issues with the Co-Author functionality:
It should never have been enabled when disableAIFeatures is on.
It should not add attribution to changes that were not done by AI.
We need to make sure it receives a more test coverage before change the default.
If you have additional (constructive) feedback, please ping me directly or open an issue."
It's all because of ridiculous performance systems of some $BIGTECH$
"Here's we increased number of commits by Copilot from X to Y, %Z increase"
Havoctoday at 8:36 AM
MS sure is making a lot of strange moves as of late
guluartetoday at 12:27 AM
Seems like MS from the Gates/Ballmer era is back
chrysopraceyesterday at 9:41 PM
Is this when you add a commit through VSC or does the editor add some git hook?
starefossentoday at 4:02 AM
Changes the defaults. Does not care to provide a pull request description. Talk about hubris.
deletedyesterday at 9:04 PM
hparadiztoday at 1:17 AM
This is why I never ever commit through the gui.
pglevytoday at 2:41 AM
Wondering what else I'm using from MS that might be at risk. <glances at TypeScript>
bytesandbitstoday at 7:40 AM
I thank Microsoft deeply for the forced copilot crap, almost impossible to remove, that they have put into vs code. Finally after 5 years I have deleted vs code in my Mac! that was the last piece of windows software I still had around. VS code was great years ago, until Microsoft started to push crap into it – and afaik they also made the fully open-source, telemetry-free fork difficult to use with many extensions.
Really, thanks for forcing me into deleting it. turns out vim + Claude Code or codex was much better all along, it really works well for me.
rbbydotdevyesterday at 9:34 PM
So GitHub reached its tipping point, I guess vscode will follow
Animatsyesterday at 8:54 PM
Does that make the code uncopyrightable? Non-human authorship?
nclin_today at 1:40 AM
It's your own fault for using anything made by microsoft at this point.
matt3210today at 1:20 AM
Adding anything to my commits or PRs or anything else is a deal breaker TBH
thomblesyesterday at 9:26 PM
I saw this the other day and was pretty confused - I prefer to write my own commit messages and wondered if I’d accidentally let the AI do it this time. Nope, just MS changing things behind my back. Sigh.
ninkendoyesterday at 9:47 PM
> No description provided.
Right because of course you wouldn’t provide an explanation for why such a change would be made.
Providing zero description or background or explanation for why a change is made is probably the only thing that pisses me off as much as a pure AI-slop description of a change: your job in a PR description is to give the background for why a change is being made. Honestly, any PR which doesn’t do this should be insta-closed by policy. But it totally tracks with the level of quality I’d expect from the company in question.
slowhadokenyesterday at 11:34 PM
My early paranoia about corporate AI is really maturing. No one’s really laughing at me anymore either.
WhereIsTheTruthtoday at 8:47 AM
KPI maxxing gone wrong
What's the legality of this, does this mean you give Copilot exclusive rights to your projects?
Fishy fishy
bakugoyesterday at 10:05 PM
Having to scroll through 3 screens worth of giant automated comments on the linked PR before seeing any comments written by humans is the cherry on top.
So many repositories look like this now, it's honestly sad.
flipthefrogyesterday at 9:32 PM
A lot of bitching about Microsoft here, for something Claude has been doing forever. I have a git hook that rejects any commit containing the line Co-authored by Claude
the13yesterday at 10:08 PM
Default or mandatory gift authorship?
sourcegrifttoday at 12:31 AM
Co-authored-by iPhone
wutwutwattoday at 12:03 AM
Does anyone happen to know, what, if any, are the ownership/copyright/intellectual property liabilities and/or rights that come from a `co-authored by copilot/claude/codex/whatever`
Right now these companies are dealing with legal troubles from taking other's code/IP without honoring the license or copyright.
My theory that could be a bit of stretch is; if they can eventually replace all that copyright'd code that is trained into these models with versions their agent services created during the millions of uses daily, they can train future versions on code they wrote. If they hold any ownership stake or usage rights on that code, due to those co-authored lines, which are saying "this agent and by extension the company that owns it was a part of creating this code", they effectively will have laundered the license away from the original owners and removed any way to pursue legal action because they won't even be using the stuff stolen anymore, and worse yet, if they now have their own copyright or other legal grounds due to their agents co-authoring all new code, they could start going after smaller ai companies for the same thing individuals were going after them for.
I know that's a pessimistic outlook, but I feel like the co-authored lines are being placed there for more than marketing exposure. It's a commit message after all, how much could that help marketing. It's the ownership/author attribution aspect that concerns me.
This is not just a joke, it is a legal nightmare. You may be giving away the copyright ownership, or at least part of it, to Microsoft.
booleandilemmayesterday at 9:09 PM
The day I see it does this is the day I switch to zed, or whatever.
awesome_dudeyesterday at 9:01 PM
I personally don't mind if an AI inserts it's "Co-Authored by" tag into commits it has worked on - it's transparency, I used its help and it should get credit for good work, or disdain for bad.
But, just inserting the tag because it's being used for git commands - there's a line there.
bborudyesterday at 11:53 PM
Microsoft is enshittifying VS Code. I have already started looking for a lifeboat.
Imagine what this is going to look like in 2 years.
gneggghtoday at 6:26 AM
"microsoft locked as spam and limited conversation to collaborators 6 hours ago" :)
bsuvctoday at 12:45 AM
In typical Microsoft form, they locked further comments on the GitHub PR.
villgaxtoday at 10:02 AM
dmitrivMS should be fired by microsoft if they wanna take ownership of this legal fiasco
I got tired of Claude adding their signatures to my commits against my instructions (the settings schema changed at some point), so I added a commit-msg hook that blocks multi-line commits. Easy and works like a charm, and would block this sort of M$ intrusion.
What a despicable behaviour from M$.
tiberriver256yesterday at 11:45 PM
Poor Courtney
alansaberyesterday at 10:12 PM
Finally the usage metrics look amazing, the masses have woken up
I do at work because nobody listens to me, but at home never ever have I used VS Code. Use just Codium.
pelasacoyesterday at 9:13 PM
Wasn’t it discussed here that no copyrights apply to code generated by AI? I’m asking myself whether adding "Co-authored-by: Copilot" means the code is not protected by the GPL, or even allows Microsoft to own your code...
deletedyesterday at 8:54 PM
deletedyesterday at 8:49 PM
simianparrottoday at 5:23 AM
... they don't require code review by at least one other person before merging..?
If this is indicative of practices over at MS these days, it explains a lot.
deletedyesterday at 9:00 PM
te_chrisyesterday at 9:39 PM
Claude code and codex do this all the time too. Fucking annoying.
morkalorkyesterday at 9:08 PM
Well, that's good news for all the developers working at companies with delusional management proclaiming "100% of code will be written by AI in 6 months"!
altuntoday at 11:12 AM
[dead]
mohamedabdallahtoday at 8:24 AM
[flagged]
henry2023today at 2:52 AM
[dead]
samagragunetoday at 9:12 AM
[dead]
samagragunetoday at 9:12 AM
[dead]
iqfareezyesterday at 11:56 PM
[dead]
eddyaipttoday at 12:44 AM
[dead]
c0baltyesterday at 8:53 PM
Growth hacking at its best /s
Scarbuttyesterday at 9:01 PM
"chat.disableAIFeatures": true
preommryesterday at 8:58 PM
I really hope the editor wars don't start again. I've been happily using VsCode for years now. More than happy in fact, it's one of the best pieces of software I've ever used, as evidenced by how AI companies basically started as a VsCode fork.
But this is going full-throttle on enshittification.
WTF happened at microsoft (github, openai partnership, copilot pricing) that all this shit just ramped up to a 11?
2OEH8eoCRo0yesterday at 8:57 PM
If you're angry about this then what are you going to do about it?