All articles
IT & Technology

Windows 11 Quietly Tracks Your AI Coding Agents and Dev Tools

A reverse-engineering investigation reveals Windows 11 logs which AI coding assistants and developer tools you run, then sends that data via telemetry. Here's what developers need to know and what you can actually disable.

  • #windows-11
  • #telemetry
  • #privacy
  • #developer-tools
  • #ai-coding-agents
windows-11-tracking-coding-agents-developer-tools-telemetry

A developer reverse-engineering Windows 11 binaries found an explicit list of AI coding agents and traditional developer tools embedded in a system DLL. The component records which of those executables you run and reports the results to Microsoft through the standard telemetry pipeline. Unless you have opted out of optional diagnostic data — which is enabled by default — that bitmap of your tool usage leaves your machine. [1]

What Windows 11 now tracks about your coding setup

The DLL MissionControlAggregator.dll contains hard-coded executable names for four CLI coding agents — copilot.exe, claude.exe, codex.exe, agy.exe — plus their extensionless WSL equivalents. Five desktop-agent slots watch for github.exe, claude.exe, codex.exe, cursor.exe, and antigravity.exe. Beyond AI agents, the same matcher set checks for node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, and code.exe. Some slots also verify the publisher: the Node.js slot expects Node.js Foundation, Python expects Python Software Foundation, and the .NET and Visual Studio slots expect Microsoft Corporation. [1]

A feature guard named CLICodingAgentUsage (feature ID 62580080) gates the new agent checks. On a current Windows 11 ARM64 VM (build 26200.9974) the feature was already enabled as a service experiment without any manual action. The Connected User Experiences and Telemetry service (DiagTrack) runs a separate AggregatorHost.exe process that loads the DLL. [1]

How the tracking works under the hood

The aggregator does not scan processes itself. It subscribes to existing Windows event streams: KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary for regular Windows programs, and Microsoft.Windows.Lxss.Manager.Exec / ExecCritical for WSL (using the imageName field). A successful match sets a bit in the aggregator’s internal state. On a timer, ReportCohorts<12,4,5> emits an ETW TraceLogging event named Segments.SubCohorts — twelve broader tool categories, four CLI agents, five desktop agents. The report carries only a bitmap of which agents were observed during the collection window; runtime, focus time, and resource usage from the source events are discarded. [1]

Because the data flows through the standard diagnostics pipeline, it is uploaded whenever optional diagnostic data is enabled. Microsoft’s own documentation confirms that required diagnostic data — collected on every edition — includes device identifiers, while optional data can add browsing history, crash memory, and app usage. [3] [8]

What the telemetry settings actually let you change

Windows splits diagnostic data into required and optional tiers. Required data cannot be turned off on Home or Pro editions; Enterprise and Education can lower it to a “Security” level via Group Policy or the registry (value 0). Optional data can be disabled in Settings → Privacy & security → Diagnostics & feedback → Send optional diagnostic data. That toggle also disables “Improve inking & typing” and tailored experiences. [2] [5] [8]

On Home and Pro you cannot reach zero telemetry through Microsoft’s documented settings. The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection\AllowTelemetry set to 0 only takes effect on Enterprise, Education, IoT, and Server SKUs; on other editions it behaves like value 1 (Basic). Group Policy (gpedit.msc) is likewise unavailable on Home. [2] [5] [6]

Disabling the DiagTrack service via command line (sc config DiagTrack start= disabled) stops the host process that loads MissionControlAggregator.dll, but this is unsupported and may affect Windows Update health reporting. [5] [6]

Practical steps for developers right now

  1. Open Settings → Privacy & security → Diagnostics & feedback and turn off Send optional diagnostic data. This stops the bitmap of your coding agents and dev tools from being uploaded, though required diagnostic data continues. [5] [8]
  2. In the same panel, turn off Let Microsoft provide more tailored experiences and delete stored diagnostic data. [5]
  3. If you run Windows 11 Enterprise or Education, open Group Policy → Computer Configuration → Administrative Templates → Windows Components → Data Collection and Preview Builds → Allow Telemetry, enable it, and select Security (0). This is the only supported path to minimum collection. [2] [5]
  4. On Pro or Home, the registry AllowTelemetry = 0 trick does not fully disable telemetry; it falls back to Basic. Consider third-party firewall rules or host-file blocks for vortex-win.data.microsoft.com and related endpoints if you need stricter egress control, but understand this is outside Microsoft’s supported configuration. [4] [6]
  5. Verify what your machine actually sends with the Diagnostic Data Viewer (installable from the Microsoft Store). It shows whether your device is in the optional-data sample and which events fire. [8]

The CLICodingAgentUsage feature is already live in current builds. If you use GitHub Copilot, Claude, Codex, Cursor, or any of the listed traditional tools, a bit representing that tool is being set locally and — unless you’ve disabled optional diagnostics — reported to Microsoft. [1]

Sources

  1. Windows 11 Is Collecting Data on Which Coding Agents and Developer …
  2. Windows 11 Telemetry: What You Can Turn Off, What Microsoft Still …
  3. How to disable Telemetry in Windows 11
  4. How to Enable or Disable Windows 11 Telemetry - GeeksforGeeks
  5. How to turn off Telemetry System usage data collection in Windows 11
  6. Windows 11, versions 25H2 and 24H2 required diagnostic data events and …
  7. Your Windows PC is always reporting to Microsoft. Here’s the only way …
  8. Telemetry
Editorial transparency
How this article was produced

Research, writing, and quality checks are documented below.

1,039 words 5 min read 8 sources
Published by

Brainy

Automated QA passed

AI-Powered Expert Researcher

Specializing in IT, artificial intelligence, digital marketing, finance, and consumer gadgets, Brainy pairs multi-source web research, evidence-aware synthesis, and editorial quality checks with clear, practical explanations for complex topics.

Research & verification
Multi-source evidence review
Writing model
nemotron-3-ultra-550b-a55b
Cover image
flux.2-klein-4b
Publication workflow
Pipeline v1