Researcher: Windows 11 can tell Microsoft which coding agents you use
Xusheng Li reports that a Windows 11 diagnostics component can identify coding agents and developer tools by program name and add this information to the optional diagnostic data sent to Microsoft. Users can switch off sending optional data.
On 16 November Xusheng Li published a blog post in which Li reverse-engineered the MissionControlAggregator.dll library in Windows 11. Li says AI found a list of coding agent and developer tool names in Windows files.
Detection relies on the program name
The library compares the names of programs in use against its lists. It checks four CLI agents: copilot.exe, claude.exe, codex.exe and agy.exe. It checks five desktop agents: github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe. The agent checks run only when the CLICodingAgentUsage feature is enabled.
The library also identifies developer tools and sorts them into 12 categories. The tools include node.exe, python.exe, dotnet.exe, gcc.exe and code.exe.
The component does not scan running processes itself. It reads program launches in WSL, the Windows Subsystem for Linux, and app events that Windows logs anyway. These events also contain run times and usage counts. Li said, however, that the component appears to store only a bitmap, in which each agent’s or tool category’s bit shows whether it was detected during the reporting period. Li found no prompts or source code in the report.
The name alone was enough to identify Codex. Li copied the Windows command interpreter cmd.exe to a file named codex.exe, and the component marked Codex as used. Some checks also require the correct publisher, such as the Python Software Foundation for Python. The GCC and Clang category does not check the publisher. WindowsForum, which covered the findings, notes that the Codex bit does not prove that the real Codex was used on the machine.
The report reached the upload queue
The report is generated roughly once a day. To get it immediately, Li moved the start of the stored reporting period back by 25 hours. Li found the report in the upload queue of DiagTrack, the Windows diagnostics service, marked as optional diagnostic data. WindowsForum said this does not prove that Microsoft’s servers received the report, nor does it show that the report is sent when optional data is switched off.
The feature was enabled as a service experiment on Li’s Windows 11 ARM64 virtual machine, although Li had not turned it on. On a machine built from a public installation image, it was off by default, so Li does not claim the feature is active on all installations. WindowsForum said Microsoft collects some optional data from only a subset of devices, but the sampling rules for this report are unknown.
When Li installed a clean copy of Windows 11 Home ARM64 from the latest official image with the region set to the United States, optional diagnostic data was already switched on. Li says this default applies at least to that installation.
Optional data can be switched off
Li says users can switch off sending optional diagnostic data. In English-language Windows the setting is under Settings → Privacy & security → Diagnostics & feedback → Send optional diagnostic data. Users can also leave optional data unselected during installation.
Citing Microsoft’s guidance, WindowsForum says Windows works normally with required diagnostic data alone. On work or school computers, administrators may block changes to the setting, and Windows Insider preview builds require optional data. The site also notes that changing the setting does not guarantee that data already stored on the machine is deleted.
Read more: How an agent works · Agent map