Windows 11 quietly logs which coding agents you run
Xusheng Li found that a Windows 11 component named MissionControlAggregator.dll watches which coding agents and developer tools you run and records them as a bitmap of categories. It does not capture prompts, source code, or how long each tool stays open. What it does capture is the tooling itself: CLI agents like copilot, claude, and codex, desktop agents including cursor and antigravity, and ordinary developer tools such as node, python, and gcc, sorted into twelve categories. Some checks also require a matching publisher, for example the Python Software Foundation, before a tool counts.
The discovery came from reverse engineering. Li asked an agent to scan recent Windows binaries for undocumented strings, then followed the executable names into comparison functions with Binary Ninja. The component does not scan running processes itself; it subscribes to existing Windows diagnostic events and feeds the application names they already contain into the matchers. Li confirmed the behavior on an ARM64 Windows 11 VM by copying cmd.exe to codex.exe and gcc.exe and watching the report get built, then found it queued for upload in DiagTrack's local event store. A feature flag called CLICodingAgentUsage controls it, and it was already on in the test build as a service experiment, though the public ISO's baseline had it off.
The reach is narrow in what Li verified: one ARM64 VM, one US install. But the collection runs when "optional" diagnostic data is enabled, which was on by default in the US setup he tested. The setting lives under Settings, Privacy and security, Diagnostics and feedback.
Why it matters
Even without prompts or code, the list of coding agents and tools you use reveals a lot about how you work and what you build. If that is not something you want sent to Microsoft, this is the week to check whether optional diagnostics are turned off on your machine.