Windows 11 Keeps a Bit for Every Coding Agent You Run

A researcher asked an AI to skim the Windows 11 binaries for undocumented features and got handed a string list: codex.exe, claude.exe, cursor.exe, gcc.exe, python.exe. The list lives inside a signed Microsoft DLL called MissionControlAggregator.dll. It is not decoration. The component uses those names to classify what you work with, stores the result on disk, and hands it to Windows Diagnostics.

Xusheng Li followed the references and published the full trace. The short version: four CLI slots check copilot.exe, claude.exe, codex.exe and agy.exe, with extensionless twins for the WSL path. Five desktop slots check github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe. A wider group covers the usual local toolchain: node, python, dotnet, gcc, clang, gdb, javac, devenv, code. Some slots verify the signer as well. Node has to come from the Node.js Foundation, Python from the Python Software Foundation, .NET and Visual Studio from Microsoft.

What the DLL actually does

It does not walk the process table. It subscribes to events Windows already emits: KernelProcess.AppStateChangeSummary, Win32kTraceLogging.AppInteractivitySummary, and on the WSL route Microsoft.Windows.Lxss.Manager.Exec. A match flips a slot in local state. A timer later compresses the slots into bitsets and emits one ETW event named Segments.SubCohorts: twelve developer-tool categories, four CLI agents, five desktop agents.

The transform also discards data. Source events carry focus time, interaction counters and resource usage, none of which survives into the report. What ships is a bitmap of which tools appeared during the window, and nothing else.

Static analysis alone would not prove anything leaves the machine. Li ran it. On a Parallels Windows 11 ARM64 VM, build 26200.9974, the feature gate CLICodingAgentUsage (ID 62580080) was already enabled as a service experiment, without him touching it. A Codex run set bit 2. State persisted to C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\MissionControlAggregator$, and the event showed up in DiagTrack’s upload queue with CliAgentSubCohorts: [4], which is 1 << 2. A copy of cmd.exe renamed gcc.exe set developer-tool slot 3 the same way.

To check your own box, the listener session is inspectable:

Get-EtwTraceProvider -SessionName Diagtrack-Listener `
  -Guid '{2839ff94-8f12-4e1b-82e3-af7af77a450f}'
Get-EtwTraceProvider -SessionName Diagtrack-Listener `
  -Guid '{00de11a2-ec06-58e5-1a2b-21bb21dbee4b}'

Optional is a UX word

On a clean Windows 11 Home ARM64 install from the current ISO, region set to the United States, the Diagnostics toggle already read “Include Optional” before any settings were touched, and AllowTelemetry was 3. Optional, in practice, means on. The upload path is live for anyone who accepted defaults at OOBE, which is most people.

The payload is small and that is exactly what makes the design worth arguing about. A bit names the tool. It survives every attempt to hide inside the application, because the signal comes from app-state and process events rather than from anything the tool can control. Join it to a device and a diagnostics pipeline and you get a longitudinal record of which agents a machine adopted and when.

A company that ships one of the five desktop agents on that matcher list also maintains the allowlist that identifies which competitor’s agent you run. Shrinking the payload to a bitmap does not soften that. It sharpens it, because the bit still carries the name.

There is a second reading, less conspiratorial. Cohort telemetry like this is how platform teams decide where to spend compatibility work, and a bitmap is a defensible minimum. agy.exe sitting next to codex.exe shows a taxonomy updating faster than any documentation process could track. I do not think this is a data grab. I think it is a product decision made by the group that also competes in the category, and nobody wrote that down in a place a customer would read.

What you can turn off, and what stays

Decline optional diagnostics during setup, or flip “Send optional diagnostic data” off later under Settings, Privacy and security, Diagnostics and feedback. That kills the upload.

It does not kill the matchers, and it does not clean out AggregatorStorage. The local bitmap keeps being written. For a development machine that is the honest limit of the control: you can decline the report, not the classification. Enterprise fleets have one more move, since the feature gate is a service experiment and can be pinned in policy, but that route assumes an admin who already knows the gate exists.

A test that needs no trust in either side: diff the matcher strings in MissionControlAggregator.dll across two feature updates. If the list is frozen, this was a one-off experiment that shipped early and will fade. If it grows toward local runtimes and self-hosted agents, then the classifier is being built for something broader than diagnosis, and the toolchain inventory becomes a product surface with a privacy policy attached.

The write-up, with Binary Ninja screenshots, ETW captures and the upload-queue dump, is at Xusheng Li’s investigation. Fifteen minutes on your own box beats my opinion.

Press ⌘K to search & switch themes