Watch the video, transcript and sources
https://www.youtube.com/watch?v=kcoco35F8pQ
+ One Windows build keeps a daily yes-or-no flag per coding agent
- Microsoft has not explained it, and we ran nothing ourselvesA researcher named Xusheng Li, who works on Binary Ninja, says a Windows 11 component keeps one bit for each coding agent it sees: Copilot, Claude, Codex and agy on the command line, plus GitHub, Claude, Codex, Cursor and Antigravity on the desktop. He found it by asking an AI to search new Windows files for undocumented features. Everything below about how it behaves is his report on one ARM64 virtual machine, plus Microsoft's own documentation. We did not run it on a Windows machine.
What it keeps
The names sit in a system file called MissionControlAggregator.dll, where Li found exact comparisons with executable names. The component does not scan your disk. It reads events Windows already produces, such as app state summaries and Linux launches under WSL. Those events carry run time and focus time. Li says the component appears to discard them and keep only a bitmap: one position per slot. Codex sits at position two, so a Codex sighting makes the row read four. About once a day the component emits a small report. Li found no prompt text and no source code in it.
That is a smaller record than Windows is allowed to collect. It is still a record of which tools a person uses to do their job.
Does it leave the PC?
Li forced a report by moving the saved reporting window back twenty-five hours and restarting the diagnostics service. A stand-in program set one bit. He then found the event in the diagnostics upload queue, with "privacy": { "isRequired": false }. That flag marks it as optional diagnostic data.
On his clean Windows 11 Home install in the United States, the diagnostic data toggle already read Include Optional. His reading is that the report is queued for upload unless you change it. He saw it queued. He did not capture it leaving the machine, so the supported claim is that the report was queued.
Microsoft's own page lists app activity, such as which programs are launched on a device, under optional data. It also says it uses app activity to prioritize compatibility testing and feature work for the apps people use most. A census of coding agents would fit that sentence. The documentation does not say that is the purpose here.
What the optional switch does not obviously cover
Microsoft's required events list for Windows 11 versions 25H2 and 24H2 names a second event from the same component: Microsoft.Windows.MissionControlAggregator.Segments.Cohorts. It classifies users by app usage, and the only cohort reported is called IsDeveloper. Required data is the floor on Home and Pro; the "off" setting exists only on Server, Enterprise and Education.
Nobody has shown that this flag fires on a given PC, and nothing documents what feeds it. We do not claim it uses the agent bits.
What nobody knows yet
How many machines run this. Li's first version of the post said a baseline virtual machine from the public ISO had the feature disabled by image default. That sentence is not in the current version, and we found no explanation. Microsoft's page says some optional data is collected from only a small percentage of devices, and Li's build called the feature a service experiment. We found no Microsoft statement on Tuesday.
How Windows decides a program is Codex
This is the part that answers the question we opened with. Li copied the Windows command prompt, renamed the copy codex.exe, and ran it. The Codex bit flipped. A copy renamed gcc.exe set the compiler bit. The check looks at a file name, and a file name can go on anything. A real agent under another name would likely go uncounted, though Li did not test that.
What to do
If you run agents on Windows, open Settings, then Privacy & security, then Diagnostics & feedback, and look at optional diagnostic data. On a work PC an admin may control it through policy. The Windows setting covers Windows; Claude Code, Codex and Cursor have their own telemetry controls.
Verdict: NEEDS REVIEW — one build, one researcher, and no Microsoft explanation of what each bit is for.
Sources
Xusheng Li, "Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use" (CC BY-NC 4.0): https://xusheng.dev/posts/windows-coding-agent-telemetry/
The same post as first published, Internet Archive capture of Nov 16, 23:00 UTC: https://web.archive.org/web/20261116230024/https://xusheng.dev/posts/windows-coding-agent-telemetry/
Li's X thread: https://x.com/CrackmesOne/status/2122147747390468384
Hacker News discussion: https://news.ycombinator.com/item?id=50524736
Microsoft Support, Diagnostics, feedback, and privacy in Windows: https://support.microsoft.com/en-us/windows/privacy/diagnostics-feedback-and-privacy-in-windows
Microsoft Learn, Configure Windows diagnostic data in your organization: https://learn.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization
Microsoft Learn, Required diagnostic events and fields for Windows 11, versions 25H2 and 24H2: https://learn.microsoft.com/en-us/windows/privacy/required-diagnostic-events-fields-windows-11-24h2
Visual credits: thumbnail portrait of Satya Nadella by Brian Smale and Microsoft, 2017, CC BY-SA 4.0 via Wikimedia Commons, cropped and adapted by The Daily Diff; he did not author, approve or react to this report. Source recordings and excerpts: Xusheng Li, xusheng.dev, CC BY-NC 4.0, excerpt.
And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.

