Windows 11 Diagnostic Component Tracks Coding Agents and Developer Tools Under Feature ID 62580080
Reverse engineering of Windows 11's MissionControlAggregator.dll found embedded checks for coding agents and developer tools. The component records usage from Windows and WSL events and uploads it to Windows Diagnostics when optional diagnostic data is enabled. The finding matters because OS-level telemetry can create a detailed developer tooling profile by default.
The report says the component, MissionControlAggregator.dll, contains explicit checks for coding agents and developer tools, including copilot.exe, claude.exe, codex.exe, agy.exe, github.exe, cursor.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe and code.exe. Some checks also verify publishers, such as Node.js Foundation, Python Software Foundation and Microsoft Corporation. The agent checks are tied to feature ID 62580080, named CLICodingAgentUsage. The list is not limited to AI agents; it also covers compilers, debuggers and editors.
The analysis says the DLL does not scan processes directly. It subscribes to existing Windows events: KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary for Windows programs, and Microsoft.Windows.Lxss.Manager.Exec and ExecCritical for Windows Subsystem for Linux. The handlers pass application identities to the executable-name matchers. A normal Windows codex.exe can therefore reach the CLI-agent checks through the app-state summary route, not only through WSL events. The component saves persistent state to disk and sends cohort data in an Event Tracing for Windows report.
The finding sits inside Windows diagnostics, not a separate product. Windows Diagnostics collects optional telemetry to improve features and reliability, and users can opt out of the optional diagnostic data setting. The report says the data is uploaded unless that option is disabled. Because the tracked names include both AI coding agents and mainstream developer tools, the component creates a usage profile across several parts of a developer's machine, including command-line tools, editors, compilers and WSL activity.
The stakes are privacy and intellectual property. A list of coding-agent and tool usage can reveal what software a person or company uses, which projects they touch and how they work, even without capturing code or prompts. For developers on managed Windows machines, the report shows that OS-level telemetry can build a detailed productivity and tooling profile by default unless optional diagnostics are turned off. It also raises questions about enterprise compliance and data governance.
Developers and companies using Windows are affected because OS telemetry can profile coding-agent and tool use without capturing code or prompts. The default-on optional diagnostic data setting means privacy and compliance controls need to address this OS-level signal.
Sources (1)
- [1]Original source(https://xusheng.dev/posts/windows-coding-agent-telemetry/)