Windows 11 telemetry records coding-agent and developer-tool use
Reverse engineering of MissionControlAggregator.dll found that Windows 11 records bitmap indicators showing which coding agents and developer tools were observed, including Codex, Claude, GitHub Copilot, Cursor, Python and .NET. The researcher verified on a US-configured Windows 11 Home ARM64 installation that the report entered DiagTrack's upload queue when optional diagnostic data was enabled, which was the default in that setup. The report contained no prompt text or source code, and its timestamps represented collection windows rather than per-tool usage duration. Behavior in other regions, editions or configurations was not established.
The investigation documents a working telemetry path that can queue information about which AI coding assistants and developer tools a user has run for upload to Microsoft. This has privacy implications even though the report contains no prompt text or source code and does not record each tool's usage duration.
Reverse engineering Windows 11's MissionControlAggregator reveals coding-agent and developer-tool usage bits in a diagnostic ETW report.
I recently asked AI to help me look through the latest Windows binaries for undocumented features and functionality. Among the leads it turned up, one list immediately caught my attention: coding agents such as codex.exe, claude.exe, copilot.exe, and cursor.exe, alongside familiar developer tools such as python.exe, dotnet.exe, gcc.exe, and code.exe.
Why would a Windows system DLL need a list of coding agents and developer tools?
The names were in MissionControlAggregator.dll. I asked the agent to follow the references and dig into what the DLL actually does. That led from a handful of string comparisons to a running Windows component that records which coding agents and developer tools have been used, saves that information locally, and reports it to Windows Diagnostics. And unless you have opted out of the “optional” diagnostic data (which is enabled by default), the data is uploaded to Microsoft.
I shared the initial finding on X. This post includes more details about the investigation behind it.
Following the names
Opening the DLL in Binary Ninja made the first lead easy to see. These were explicit executable names embedded in a Windows component:
#Microsoft#Windows 11#Windows MissionControlAggregator#Codex#Claude#GitHub Copilot#Cursor#Python#Visual Studio Code#.NET