Windows 11 checks a short list of names before it checks almost anything else on your computer. Seven of those names are AI coding tools: Claude, Codex, GitHub Copilot, Cursor and three more1.
A developer named Xusheng Li found the list buried inside a Windows system file. He posted his findings on Nov. 16. Word spread to X the same day12.
Seven tools made the list
Li reverse-engineered a Windows 11 file called MissionControlAggregator.dll. Inside it, he found a feature Microsoft calls CLICodingAgentUsage, feature ID 625800801.
The feature checks for seven programs by name, each one a coding agent's own process: codex, claude, copilot, cursor, antigravity, github and agy. Windows knows each by its exact file name, codex.exe and the rest1.
It checks nine plain developer tools too, the same way. Python, Node, dotnet, GCC, Clang, GDB, Java's compiler, Visual Studio and VS Code round out the sixteen1.
Windows 11's Watchlist Names 7 AI Coding Tools Among 16 Programs
Programs Windows 11's MissionControlAggregator checks for by name, one cube per program, reported by Xusheng Li
Each cube is one program Windows 11 checks for. Magenta cubes are AI coding agents such as Claude, Codex and Cursor; gray cubes are plain developer tools such as Python and GCC.
Source: xusheng.dev [1]. Chart by Ryan Elliott Dennis.
The numbers behind this chart
| Item | Value |
|---|---|
| AI coding agents | 7 |
| Plain developer tools | 9 |
| Whole | 16 |
Each hit becomes one bit in a small report. One number. That's all a bitset is, marking which of the sixteen programs it saw running1.

How the report reaches Microsoft
Windows stores that bitset inside a folder called AggregatorStorage. A long-running service named DiagTrack manages it. DiagTrack already watches crashes and update failures on every Windows 11 machine1.
The feature leans on ETW, short for Event Tracing for Windows. That's a logging system built into the operating system itself.
Two existing Windows logging events feed it. Both already watch ordinary app activity on their own, unchanged for this new use1.
Li found the report follows a daily boundary, give or take. It also catches activity inside WSL, short for Windows Subsystem for Linux. Many developers use WSL to run these same coding agents1. One system, two entry points.
The coding-agent report leaves the computer only when a setting called optional diagnostic data stays on. It ships on by default in the US setup Li tested1.
Crackmes.one, a hacking-puzzle site's account on X, posted Li's find the same day it went live. "Windows 11 build 26200.9974 checks codex.exe, claude.exe, copilot.exe, cursor.exe, antigravity.exe, github.exe and agy.exe through MissionControlAggregator, then reports agent bitsets in ETW," the account wrote2.
Crackmes.one@CrackmesOneI found that Windows starts to collect your coding agent usage information. Windows 11 build 26200.9974 checks codex.exe, claude.exe, copilot.exe, cursor.exe, antigravity.exe, github.exe and agy.exe through MissionControlAggregator, then reports agent bitsets in ETW. pic.twitter.com/AYqA6xpLQZ
The post drew 3,127 favorites within a day of going up, and 113 replies traded instructions for turning the setting off2.

The case for alarm
Li found the feature. Whatever the report leaves out, he still calls it a privacy problem on its own.
"Although I found no prompt text or source code in this report, collecting which agents and developer tools someone uses already has significant privacy implications," Li wrote1.
His point rests on one plain fact. Every diagnostic feature Microsoft shipped before this one stayed silent on which AI agent a person chose. Claude, Codex and Cursor rival Copilot directly, and this list names them all1.
Read as a business risk, the same list could tell Microsoft which coding agent a whole engineering team standardized on. The detail usually sits inside a vendor contract instead of a public filing.
The Hacker News discussion of Li's post topped 410 points and 263 comments within a day3. One reply told readers to turn the setting off through Group Policy instead of the Settings app. A later Windows update can quietly switch Settings back on, the reply warned.
The Telemetry Report Draws 410 Hacker News Points in a Day
Engagement on the find's two biggest threads, counted a day after Xusheng Li's post went up
Each bar is one count from one platform: the first two bars are reactions to Crackmes.one's post on X, the last two are the Hacker News discussion of Li's report.
Sources: Crackmes.one on X [2]; Hacker News [3]. Chart by Ryan Elliott Dennis.
The numbers behind this chart
| Item | Value |
|---|---|
| X favorites | 3,127 |
| X replies | 113 |
| HN points | 410 |
| HN comments | 263 |
Microsoft calls this kind of logging routine
Microsoft's own support page calls this kind of logging routine. It says the goal is fixing bugs and guiding feature work. The company has tracked which programs people launch for years, on any machine sending optional data45.
"App activity information helps us prioritize app-compatibility testing and make feature improvements to apps and features that are used the most," Microsoft's support page says4.
Read that way, the coding-agent list extends an app-launch log Windows already keeps. The log now stretches to cover seven programs that only became common this year5.
Li's own report backs part of that defense. The upload stayed limited to a count of which programs had run. Prompt text and source code stayed out of it1.
What to do
Open Settings, then Privacy & security, then Diagnostics & feedback. Turn off optional diagnostic data if your choice of AI coding agent is information you want to keep off Microsoft's servers4.
Set the same choice through Group Policy on a shared or office machine. The Hacker News thread's warning holds: Settings alone can drift back on after an update, a path Group Policy blocks for good3.
Ask your AI coding tool's maker what it already collects. This question will return. The list names seven agents today. Windows updates its binaries often enough to add more1.
Check that setting on every machine your team issues, your own laptop included. A policy written for one computer leaves the other hundred a company runs still exposed.
By the numbers
- 16 programs: total names Windows 11's MissionControlAggregator checks for, developer tools and AI coding agents combined1.
- 7 AI coding agents: named directly inside the check, among them claude.exe, codex.exe, copilot.exe and cursor.exe1.
- Build 26200.9974: the Windows 11 build where Li found the feature active1.
- Feature ID 62580080: Microsoft's internal label for the check inside its own code1.
- 3,127 favorites: how many times people liked Crackmes.one's post about the find within a day2.
- 113 replies: how many answers that post drew in the same day2.
- 410 points and 263 comments: the size the Hacker News discussion reached a day after it posted3.
What to watch
Watch whether Microsoft changes the setting's default, or says anything at all about a feature an outside researcher found first. Silence invites the next build to get the same treatment.
Track the list of sixteen programs itself. A new name added next year would say more about which coding agents Microsoft watches than any public statement could.
Count on Li or another researcher checking the next Windows build, while Microsoft's own statement on the feature remains pending.
Sources
- Xusheng Li, "Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use," xusheng.dev, Nov. 16, 2026, https://xusheng.dev/posts/windows-coding-agent-telemetry/
- Crackmes.one, post on X, Nov. 16, 2026, https://x.com/CrackmesOne/status/2122147747390468384
- Hacker News, "Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use" (discussion), Nov. 16, 2026, https://news.ycombinator.com/item?id=50524736
- Microsoft, "Diagnostics, feedback, and privacy in Windows," Microsoft Support, Nov. 7, 2026, https://support.microsoft.com/windows/28808a2b-a31b-dd73-dcd3-4559a5199319
- Microsoft, "Configure Windows diagnostic data in your organization," Microsoft Learn, Sept. 11, 2025, https://learn.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization




