Windows 11 telemetry now tracks specific coding agents and developer tools
Reverse engineering reveals Windows 11 collects bitmaps of used AI coding agents and dev tools via MissionControlAggregator, uploading them as optional diagnostic data.
A recent investigation into Windows 11 binaries has uncovered a new telemetry component that actively monitors which coding agents and developer tools users execute. The component, identified within MissionControlAggregator.dll, records usage of specific executables like codex.exe and cursor.exe, then reports this data to Microsoft if optional diagnostics are enabled.
What happened
Researcher Xusheng Li used AI assistance to analyze recent Windows binaries for undocumented features. This analysis highlighted a list of executable names embedded in MissionControlAggregator.dll, including popular AI coding agents such as copilot.exe, claude.exe, codex.exe, and cursor.exe. The list also contained standard developer tools like python.exe, dotnet.exe, gcc.exe, and code.exe. Further investigation revealed that these names are not merely static references but are part of an active monitoring system.
The component functions by subscribing to existing Windows event traces rather than scanning processes directly. It listens for application state changes and interactivity summaries. When a match is found against the hardcoded list of executables, the system sets a specific bit in an internal state structure. This state is persisted locally and periodically compiled into a diagnostic report. If the user has not opted out of optional diagnostic data, this report is queued for upload to Microsoft servers.
Li verified this behavior on a Windows 11 ARM64 virtual machine running build 26200.9974. The feature, identified by the ID CLICodingAgentUsage (feature ID 62580080), was enabled by default in the tested US configuration. The telemetry service DiagTrack was running automatically, hosting the AggregatorHost.exe process which loaded the relevant DLL. Tests confirmed that renaming a generic executable to codex.exe or gcc.exe triggered the corresponding bits in the diagnostic output.
How it works
The detection mechanism relies on string comparisons within the MissionControlAggregator.dll. The code contains explicit checks for four CLI agent slots (copilot.exe, claude.exe, codex.exe, agy.exe) and five desktop agent slots (github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe). It also checks for broader developer tool categories, including compilers and runtimes like Node.js, Python, and .NET. Some checks verify the publisher signature, such as ensuring python.exe is from the Python Software Foundation, while others, like the GCC/Clang group, do not.
Data collection flows through Event Tracing for Windows (ETW). The aggregator consumes events from KernelProcess.AppStateChangeSummary for standard Windows apps and Microsoft.Windows.Lxss.Manager.Exec for Windows Subsystem for Linux (WSL) processes. Instead of logging detailed usage metrics like runtime or focus time, the component discards this granular data. It only records a bitmap indicating whether a specific tool category was observed during the reporting window.
These bitmaps are emitted in a TraceLogging event named Segments.SubCohorts. The event structure uses integer values to represent sets of tools. For example, a value of 4 in the CLI agent field corresponds to the third bit being set, indicating codex.exe was detected. This compact format allows the system to report tool usage without transmitting large volumes of raw log data.
Key details
- The monitoring component is located in
MissionControlAggregator.dlland runs insideAggregatorHost.exe. - It tracks specific AI agents like
cursor.exe,copilot.exe, andclaude.exe, alongside tools likegcc.exeandpython.exe. - Data is collected via ETW events
KernelProcess.AppStateChangeSummaryand WSL execution logs. - Reports are generated as bitmaps in
Segments.SubCohortsevents, not as detailed usage logs. - The feature is controlled by feature ID
62580080(CLICodingAgentUsage) and was active by default in the tested US Windows 11 setup. - Local state is saved in
C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\MissionControlAggregator$.
Why it matters
For developers, this revelation highlights a significant expansion in the scope of default Windows telemetry. While previous telemetry often focused on system performance or crash data, this component specifically targets the software development workflow. It identifies not just that a developer is working, but which specific AI assistants and compilers they prefer. This level of granularity could inform Microsoft’s competitive strategy in the developer tools market, providing real-world adoption metrics for rival products.
Privacy-conscious engineers must recognize that "optional" diagnostic data is enabled by default in many configurations. The data uploaded does not include source code or prompts, but it does create a persistent record of tool usage patterns. For teams with strict intellectual property policies or those using proprietary internal tools, understanding exactly what metadata leaves the workstation is crucial for compliance and security auditing.
What you can do
- Check your current telemetry setting by navigating to Settings → Privacy & security → Diagnostics & feedback.
- Disable "Send optional diagnostic data" to prevent the
Segments.SubCohortsreports from being uploaded. - Monitor the
DiagTrackservice status using PowerShell commands likeGet-Service DiagTrackto see if it is running. - Inspect local telemetry storage at
C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\to view cached reports. - Use ETW tracing tools to observe
Microsoft.Windows.MissionControlAggregatorevents if you need to audit what is being generated locally. - Review organizational group policies that may enforce telemetry settings across enterprise Windows deployments.



