Windows 11 Tracks Coding Agents and Developer Tools ~ Ibrahim Kaya
×
Cybersecurity

Windows 11 Tracks Coding Agents and Developer Tools

İbrahim Kaya Published: Updated: 2 min read
Windows 11 Tracks Coding Agents and Developer Tools
Contents

Reverse-engineering analyses of Windows 11 binaries show that the operating system catalogs AI coding assistants and developer tools executed on the system. An executable list embedded inside a core system library checks which development tools are active in the background.

Monitored binaries in MissionControlAggregator.dll

Inspection of MissionControlAggregator.dll in Binary Ninja reveals hardcoded executable names matched against active processes. Dedicated slots track CLI agents such as copilot.exe, claude.exe, codex.exe, and agy.exe, alongside extensionless counterparts running in WSL (Windows Subsystem for Linux). Desktop slots also check for cursor.exe, github.exe, and antigravity.exe.

The monitoring also covers standard runtimes and compilers, including node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, and code.exe. Some checks verify publisher certificates from organizations like the Node.js Foundation or Python Software Foundation, while compilers like GCC match on executable name alone.

powershell
PS> Get-Service DiagTrack | Format-Table Name,Status,StartType -AutoSize
Name      Status  StartType
----      ------  ---------
DiagTrack Running Automatic

PS> tasklist /m MissionControlAggregator.dll
Image Name           PID  Modules
==================== ==== ============================================
AggregatorHost.exe   1500 MissionControlAggregator.dll

How Windows collects process events

The component subscribes to Event Tracing for Windows (ETW) rather than polling the process list continuously. It consumes KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary for native Windows applications, and monitors Microsoft.Windows.Lxss.Manager.Exec for WSL tasks.

A service experiment named CLICodingAgentUsage (Feature ID: 62580080) controls this pipeline. When a target binary runs, the component records the match in an internal bitset and saves the state locally:

plaintext
C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\MissionControlAggregator$

Data upload and privacy impact

The aggregator periodically packages these bitsets into an ETW event named Segments.SubCohorts. The payload maps twelve tool categories, four CLI agents, and five desktop agents into compact bitmasks. Each detected tool flips a single bit within the reporting cohort without sending process arguments or file paths.

json
{
  "name": "Microsoft.Windows.MissionControlAggregator.Segments.SubCohorts",
  "ext": {
    "privacy": {
      "isRequired": false
    }
  },
  "data": {
    "Version": "0.1.5",
    "CliAgentSubCohorts": 4,
    "DesktopAgentSubCohorts": 0
  }
}

Records in DiagTrack's local EventStore.db database indicate that this event falls under Optional Diagnostic Data. Unless the user disables optional diagnostics, Windows uploads this tool summary to Microsoft servers. The payload does not include source code or prompt text, but cataloging local developer setups at the operating system level still creates privacy concerns.