Windows 11 telemetry and your coding agents
You open the terminal, call your favorite coding agent and get to work. What few people imagine is that the operating system itself might be noting which agent it was. That's what an analysis published by Xusheng showed: Windows 11 telemetry collects data about which coding agents and development tools are installed and in use on the machine.
For developers, this matters. Your stack says a lot about you, about your employer and about the project you work on.
What Windows 11 telemetry is collecting
Based on what the author documented, Windows doesn't stop at the usual generic data (system version, crashes, drivers). It also identifies dev tools and, in particular, AI coding agents. In other words: the system knows you use agent X in the terminal, editor Y and runtime Z, and sends that signal to Microsoft as part of diagnostics.
It's worth being precise here. The post doesn't say Windows reads your source code or your prompts. What shows up is inventory and usage: which tools exist and which ones run. Sounds like little, but it isn't.
I recommend reading the original article. It shows how the author reached these conclusions, and I won't repeat the technical details here as if they were mine.
Why this matters for developers
"Come on, it's just the program's name." Think again.
Coding agents are now the most contested market in software. Microsoft owns GitHub Copilot and VS Code. It competes directly with almost every agent you install. So knowing how many Windows devs use the competition, how often and on what kind of machine is worth a lot of money.
Three practical problems:
- Competitive intelligence. An operating system that measures usage of its own maker's competitors is a textbook conflict of interest.
- Corporate context. On a company machine, the tool list shows how the team works. Some companies ban certain agents by internal policy. Now there's an outside record that knows whether that rule is being followed.
- Vague consent. You accepted "diagnostic data" during setup. Nobody read that thinking "sure, tell Microsoft which AI I use to code".
Your tool list is a portrait of your work, even without a single line of code.
Is it illegal? Probably not. Is it weird? Yes
Here's the annoying part: everything suggests it's covered by the terms of use. Windows telemetry has existed since Windows 10, and "optional diagnostic data" has always included information about installed apps and app usage. Software inventory isn't new.
What changes is the focus. Counting how many people open Paint is one thing. Building a specific category for coding agents at a time when that market is worth billions is another. The same collection becomes a different conversation depending on what it's for.
Under Brazil's LGPD (much like GDPR in Europe), software usage data tied to an identifiable device is personal data. The legal basis is usually consent or legitimate interest. If it were up to me, I'd be skeptical that "legitimate interest" is a good justification for measuring competitors. But I'm not a lawyer, and that debate goes deep.
How to see and reduce what Windows sends
You can act today, without paranoia and without wiping your machine. The simplest path:
- Go to Settings > Privacy & security > Diagnostics & feedback.
- Turn off Send optional diagnostic data. That leaves only the required data.
- Turn off Tailored experiences and Improve inking and typing.
- Turn on the Diagnostic Data Viewer if you want to see with your own eyes what's going out.
If you use Windows Pro, Enterprise or Education, you can go further with Group Policy. From PowerShell as administrator:
# 0 = Security (Enterprise/Education only), 1 = Required
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection" -Force | Out-Null
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection" `
-Name "AllowTelemetry" -Value 1 -Type DWord
On Home, the lowest value accepted in practice is the required level. 0 is only honored on enterprise editions.
Two honest warnings. First: the "required" level still sends data, and the analysis doesn't make it clear at which level the dev tool collection happens. Second: big Windows updates sometimes turn options back on. Check again after every feature update.
To block it at the network level, some people use DNS (Pi-hole, NextDNS) with lists of telemetry domains. It partly works, but it breaks things now and then, like Windows Update and the Store. Only worth it if you know what you're doing.
What about WSL, does it help?
A lot of people here run everything inside WSL. Bun, Node, Postgres and the agent in the Ubuntu terminal. The natural question is whether Windows sees what happens in there.
As far as I know, WSL has its own telemetry (which you can turn off in .wslconfig in some versions), and Windows sees the processes on the outside, like wsl.exe and the terminal. Seeing the exact binary you run inside the distro is another level entirely. I didn't see proof either way in the material, so I won't claim anything. If this matters to you, test it with the Diagnostic Data Viewer.
The real point is something else: the editor almost always runs on Windows. If you use VS Code, Cursor or any native IDE, it's on the outside. And many agents today ship as editor extensions.
What changes in my workflow
To be honest, I'm not leaving Windows over this. I'm also not going to pretend it doesn't matter.
What I did and recommend:
- Telemetry at the minimum on every work machine, checked after every major update.
- Sensitive client projects in a separate environment. A VM, a devcontainer or a Linux machine. The operating system is part of your exposure surface too.
- Review your tools' own telemetry. The irony: many coding agents collect much more than Windows. Prompts, code snippets, file paths. Before complaining about Microsoft, open your agent's settings and search for
telemetry.
That last point is the one that bugs me most. We get outraged (rightly) at the operating system reporting which apps we use, and at the same time we send the whole repository to a cloud model without reading the retention policy. Both deserve the same attention.
A concrete example: in VS Code, you can turn off the editor's telemetry with one line in settings.json.
{
"telemetry.telemetryLevel": "off"
}
This doesn't affect extensions that send data on their own. Each agent has its own setting, and it's worth checking them one by one.
My take
The collection itself doesn't scare me. What bothers me is the lack of transparency. If Microsoft wants to know which agents devs use, it should ask, publish exactly what it collects and let you turn it off with one click, on any edition. Doing it quietly, in a market where it has skin in the game, burns the little trust Windows has won back with devs in recent years thanks to WSL and Terminal.
Meanwhile, we do the basics: check, turn off what we can and isolate what's sensitive. It's not paranoia, it's hygiene. It's the same care I try to have in my own products, collecting only what's needed. If you want to see how that looks in practice, take a look at the projects I maintain.
LinkedIn summary
Windows 11 might be keeping notes on which AI agent you use to code. An analysis by Xusheng showed that telemetry collects which coding agents and dev tools are installed and running on your machine. It doesn't read your code, but it takes a full inventory of your stack. Sounds minor until you remember Microsoft owns Copilot and competes with almost every agent you install. The collection itself doesn't scare me. What bothers me is the lack of transparency, in a market where Microsoft has skin in the game. What I did: telemetry at the minimum, sensitive projects in a separate environment, and a review of the agents' own telemetry, which often collects far more than Windows does. I wrote the full step by step on the blog. Have you checked what your machine has been sending? #Privacy #Windows11 #SoftwareDevelopment #AI #DataProtection