Windows 11 telemetry now has a new line in a very specific ledger. Security researcher Xusheng Li, who works on Binary Ninja, reports that one Windows 11 build keeps a daily yes-or-no flag for coding agents such as Codex, Claude Code and Copilot, and queues it as optional diagnostic data. Everything below is his work on one ARM64 virtual machine plus Microsoft's own documentation. I did not run any of it on a Windows machine, and Microsoft had not commented when I looked on Tuesday.
TL;DR
- Li found exact comparisons with program names such as
codex.exe,claude.exe,copilot.exeandcursor.exeinsideMissionControlAggregator.dll(his post). - The component listens to events Windows already produces, keeps one bit per slot and appears to discard run time and focus time. Li found no prompt text or source code in the report.
- He found the report in the diagnostics upload queue flagged
isRequired: false, which means optional. Queued is what he saw. He did not capture it leaving the machine. - Microsoft's required events list names a second event from the same component,
IsDeveloper. Nothing links it to the agent bits. - One build, one researcher, no Microsoft explanation yet. How many PCs run this is unknown.
What Windows 11 telemetry reportedly records about coding agents
Li asked an AI to search recent Windows binaries for undocumented features. One lead was a list of agent names inside a system file. He followed the references and found a component that matches executable names: four command-line slots for copilot.exe, claude.exe, codex.exe and agy.exe, with extensionless equivalents on the WSL route, and five desktop slots for github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe. The same file checks twelve developer-tool categories fed by names like node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, javac.exe, devenv.exe and code.exe. The feature guard is called CLICodingAgentUsage (id 62580080), and on Li's VM it was already enabled as a service experiment.
For credit: this is Xusheng Li's research, published under CC BY-NC 4.0. I quote short excerpts and link the original.
How the coding agent check works
The component does not scan your disk. Li reports that it subscribes to events Windows already emits: an app-state summary for Windows programs, an app-interactivity summary for desktop apps, and the WSL launcher's exec events for Linux binaries. A matching name sets a slot in saved state. About once a day the component turns the slots into a bitmap and emits a small report.
Here is the bit idea in one table. Li confirmed that Codex is CLI slot 2 and that the report value for a Codex sighting was 4, which is 1 << 2. The other weights below assume the slots follow the order he lists them, so treat them as an illustration.
| Position | Weight | Slot (assumed order) |
|---|---|---|
| 0 | 1 | copilot |
| 1 | 2 | claude |
| 2 | 4 | codex |
| 3 | 8 | agy |
The source events also carry run time, focus time, interaction counters and resource use. Li's reading is that this component discards them and records only which slots were seen. The timestamps in the report describe the collection window.
How does Windows tell Codex from anything else?
It compares the file name. Li copied the Windows command prompt, renamed the copy codex.exe, ran it, and the Codex bit was set. A second copy renamed gcc.exe set the compiler and debugger category. That category is shared by GCC, Clang and related tools, so the group shares one bit and tools such as GCC and Clang cannot be told apart.
Two consequences follow. A fake can set a bit, and a real agent under another name would likely go uncounted, though Li did not test that second case. A bit says "something with this name ran", nothing richer.
Is Windows 11 telemetry like this optional?
Li found the event in DiagTrack's upload queue with "privacy": { "isRequired": false }. In Microsoft's terms that makes it optional diagnostic data. On his clean Windows 11 Home ARM64 install with the region set to the United States, the diagnostic data toggle already read Include Optional and AllowTelemetry was 3. His conclusion is that, unless you changed it, the report is queued for upload.
Microsoft's own configuration page lists optional diagnostic data as including "App activity, such as which programs are launched on a device, how long they run, and how quickly they respond to input." Its support page adds that app activity helps prioritize app-compatibility testing and feature improvements for the apps used most, and that some optional data is collected from only a small percentage of devices. Whether a census of coding agents is the purpose here is not stated.
What stays on if you turn optional diagnostic data off?
Microsoft's required events list for Windows 11 versions 25H2 and 24H2 includes Microsoft.Windows.MissionControlAggregator.Segments.Cohorts, described as classifying users into cohorts based on app usage, with IsDeveloper as the only cohort being reported. Required data is the floor on Home and Pro. The "off" setting exists only on Windows Server, Enterprise and Education.
I want to be careful here. The documentation does not say what feeds that flag, whether it fires on a given PC, or whether it has anything to do with the agent bitmap. Li's post does not mention it. Turning optional data off should keep the per-agent report home. Nobody has published a run with the switch off.
What nobody knows yet
- How many machines run this feature.
- Why the first version of Li's post said a baseline virtual machine from the public ISO had the feature disabled by image default, and why that sentence is gone from the current version. I found no explanation, and I draw no conclusion about the default.
- Whether anything leaves the machine. Li saw the report queued and did not capture it leaving the machine.
- What Microsoft uses it for. It sells Copilot, one of the agents on the list, so a competitor census is a fair question. Nobody has shown it is used that way.
How to check and change the setting
On Windows 11, open Settings, then Privacy & security, then Diagnostics & feedback, and look at Send optional diagnostic data. On a work PC, an administrator may manage it through policy, and the options may be hidden or locked. Microsoft's Diagnostic Data Viewer shows events while it is open; I have not verified that it displays this particular event.
The Windows setting covers Windows components. Claude Code, Codex and Cursor have their own telemetry controls, and Microsoft's page says third-party apps collect diagnostic data under their own settings.
Verdict: NEEDS REVIEW
I stamped it NEEDS REVIEW on the show. The evidence is one build on one machine, and Microsoft has not said what each bit is for, who receives it, or why a developer flag sits on the required list. The optional switch exists, so use it on purpose. What would you do on your dev machine?
FAQ
Does Windows 11 telemetry record which coding agents I run?
One researcher reports that a component in one Windows 11 build keeps a bit for each of several coding agents and queues it as optional diagnostic data. Microsoft has not confirmed or explained it, and the rollout is unknown.
Can I turn it off?
The reported per-agent event is optional, so turning off Send optional diagnostic data in Settings should keep it from being sent. Nobody has published a test with the switch off, and required data stays on for Home and Pro.
Does it read my prompts or code?
Li found no prompt text or source code in the report. It records a bitmap of slots seen in a reporting window.
Does the Windows setting cover Codex or Claude Code telemetry?
No. Those tools have their own controls. The Windows setting applies to Windows components.
Sources
- Xusheng Li, Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use (CC BY-NC 4.0)
- First published version of Li's post, Internet Archive capture, Nov 16 2026 23:00 UTC
- Li's X thread
- Hacker News discussion
- Microsoft Learn, Configure Windows diagnostic data in your organization
- Microsoft Learn, Required diagnostic events and fields for Windows 11, versions 25H2 and 24H2
- Microsoft Support, Diagnostics, feedback, and privacy in Windows
Cover portrait: Brian Smale and Microsoft, 2017, CC BY-SA 4.0 via Wikimedia Commons, cropped and adapted into the cover artwork by The Daily Diff. He did not author, approve or react to this report. The name-tag image is original artwork by The Daily Diff.
This article expands on an episode of **The Daily Diff, a five-minute daily video on what shipped and what broke in tech.
Watch the episode · Subscribe on YouTube · the written diff lands in your inbox every morning at thedailydiff.dev.

Top comments (0)