How to Check Windows 11 Coding Agent Telemetry

Nighttime home workspace with a closed laptop, keyboard, and notebook under a desk lamp.

Windows 11 coding agent telemetry can record which coding agents and developer tools you run and queue a bitmap for upload when optional diagnostic data is on. This checklist covers what is collected, how to verify it, and how to stop the optional upload. Optional diagnostic data is enabled by default unless you opt out, and a tested build already had the agent checks running.

Updated November 17, 2026

Key Takeaways

  • MissionControlAggregator stores a bitmap of coding agents and tools.
  • A tested US setup left optional diagnostics on; AllowTelemetry was 3.
  • Li found no prompts or source code in the report.
  • Turn off Send optional diagnostic data; required data still sends.

What does coding agent telemetry actually record?

MissionControlAggregator.dll is loaded by AggregatorHost.exe, which DiagTrack, the Connected User Experiences and Telemetry service, starts. It does not scan running processes. For Windows programs it consumes KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary, which supply application identities that handlers parse and pass to the matchers.

For WSL it consumes Microsoft.Windows.Lxss.Manager.Exec and ExecCritical, using the imageName field. A regular Windows codex.exe can reach the CLI-agent checks through the app-state route, so matching is not limited to programs inside WSL.

Xusheng Li published the finding on Nov. 16, 2026. Feature CLICodingAgentUsage, ID 62580080, guards the agent checks. Four CLI slots check copilot.exe, claude.exe, codex.exe, and agy.exe, with extensionless WSL names. Five desktop slots check github.exe, claude.exe, codex.exe, cursor.exe, and antigravity.exe.

The same component also checks node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, and code.exe, among others. Those checks feed 12 broader developer-tool categories. The Node.js slot expects Node.js Foundation, Python expects Python Software Foundation, and the .NET and Visual Studio slots expect Microsoft Corporation. The compiler and debugger group containing GCC and Clang has no additional publisher check in this path.

A successful match sets a bit in Segments.SubCohorts. ReportCohorts turns those slots into bitsets for 12 tool categories, four CLI agents, and five desktop agents. Li found no prompt text or source code in this report, and executable names are not written into it.

The source events include runtime, time in focus, interaction counters, and resource usage. This component appears to discard those details and record only a bitmap of which agents were observed. Timestamps describe the collection window, not how long each agent was used. In a test, the name alone was enough for a renamed cmd.exe to be recognized as Codex.

What is matched Names in the component What the report stores
CLI agents copilot.exe, claude.exe, codex.exe, agy.exe, plus extensionless WSL names CliAgentSubCohorts bit. Codex test value 4
Desktop agents github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe DesktopAgentSubCohorts bit
Other developer tools node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, code.exe, among others Category bit. gcc.exe test value 8
Not written into this event Prompts, source code, executable names Not found in the report. Runtime, focus time, interaction counters, and resource usage appear discarded

How do you verify coding agent telemetry on your machine?

The feature is not on every image. LavX News reported that a public Windows 11 Home ARM64 ISO, region set to the United States, had the coding-agent feature disabled by image default. On build 26200.9974, DLL 10.0.26100.9818, CLICodingAgentUsage was already enabled as a service experiment, and DiagTrack was running with startup type Automatic.

Use Li’s administrative PowerShell commands to see whether that component is loaded:

  1. Open Start > Settings > Privacy & security > Diagnostics & feedback. On the default US setup, AllowTelemetry was 3, which confirmed optional diagnostic data was enabled. Setup labeled that choice Include Optional. The control is Send optional diagnostic data.
  2. Run Get-Service DiagTrack | Format-Table Name,Status,StartType -AutoSize.
  3. Run Get-Process AggregatorHost | Format-Table ProcessName,Id -AutoSize.
  4. Run Get-CimInstance Win32_Service -Filter “Name=’DiagTrack'” | Format-List Name,State,StartMode,ProcessId and Get-CimInstance Win32_Process -Filter “Name=’AggregatorHost.exe'” | Format-List ProcessId,ParentProcessId. AggregatorHost’s parent should be the DiagTrack process.
  5. Run tasklist /m MissionControlAggregator.dll. A listing under AggregatorHost.exe means the DLL is loaded.

Value 3 is what Li recorded after that US setup; repeat the Settings check yourself. Microsoft says Diagnostic Data Viewer instructions are on that page. The viewer shows data being sent and whether the device is in a sample.

How do you stop the optional upload?

Li found the agent event in DiagTrack’s upload queue with isRequired set to false. Windows queues it for Microsoft unless you declined optional diagnostic data during setup or turned it off in Settings. That Settings control is the supported stop described in the sources.

  • During setup, decline optional diagnostics.
  • On an existing PC, turn off Send optional diagnostic data under Settings, Privacy & security, Diagnostics & feedback.
  • Leave required diagnostic data in place. It is the minimum Microsoft describes for keeping the device reliable, secure, and operating normally.

Microsoft’s diagnostics, feedback, and privacy guide states:

Regardless of whether you choose to send Optional diagnostic data, your device will be just as secure and will operate normally.

What should Home and Pro users check?

Li’s clean US test was Windows 11 Home. Optional data was on by default, with AllowTelemetry at 3. On Home, the Settings toggle is the supported change.

Microsoft’s Windows Privacy Compliance guide covers Windows 11 Professional, Enterprise, and Education. Administrators set privacy controls with Group Policy, MDM, or registry settings. If they have, Settings can show an alert that says “Some settings are hidden or managed by your organisation,” and you can change only what policy allows.

The bitmap can show that Claude, Codex, Cursor, or Copilot appeared in a reporting window. Li found no prompts in the report, and still described the collection as a privacy issue. Microsoft says the specific diagnostic items it collects can change, so repeat the Settings check after major updates. Pair that check with how you lock down Claude Code secrets in Git.

Frequently asked questions

Does this report include prompts or source code?

Xusheng Li found no prompt text or source code in the report. It stores a bitmap of agents and tool categories, not executable names or how long each tool ran.

Is the coding-agent feature on every Windows 11 PC?

No. A public Windows 11 Home ARM64 ISO had it disabled by image default. It was already enabled on build 26200.9974 with DLL 10.0.26100.9818.

What did AllowTelemetry 3 confirm?

On the default US setup Li tested, AllowTelemetry was 3, which confirmed optional diagnostic data was enabled. Setup labeled that choice Include Optional.

Does turning off optional data weaken Windows?

Microsoft says the device will be just as secure and will operate normally without optional diagnostic data. Required diagnostic data is still collected.

Notice an error?

Help us improve our content by reporting any issues you find.