Security

Windows 11 telemetry: how to stop it logging your coding agents

Key takeaways

  • A Windows component called MissionControlAggregator.dll flags use of agents such as Codex, Claude and Cursor
  • The report is optional diagnostic data, which was on by default in the US setup tested
  • The report is queued for upload only when optional diagnostic data is allowed
  • No prompt text or source code was found in the report

After reading this, you will be able to check whether a Windows 11 machine is reporting your coding agent and developer tool usage to Microsoft, and switch that reporting off. Expect the settings change to be quick; the optional verification takes longer. Difficulty: easy for the setting, moderate for the verification.

What you need before starting

  • A Windows 11 machine you have administrator rights on.
  • For the settings change, nothing else.
  • For verification, an administrative PowerShell prompt and some comfort reading service and process listings.
  • Optionally, a virtual machine, so any test files stay away from production kit.

No paid tools are needed. The findings below come from a researcher who reverse engineered the component using Binary Ninja, and a corroborating report was published by WindowsForum.

What the researcher found

A system library called MissionControlAggregator.dll contains lists of executable names. Four command-line agent slots check for copilot.exe, claude.exe, codex.exe and agy.exe. Five desktop-agent slots check for github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe. The same component also looks for node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe and code.exe, among others.

It does not scan processes itself. It listens to existing Windows events, including KernelProcess.AppStateChangeSummary, and on WSL (Windows Subsystem for Linux) the Lxss Exec events. A match sets a flag, and a report called Segments.SubCohorts emits those flags as a bitmap. The researcher found no prompt text or source code in it, and the timestamps describe the collection window, not how long an agent ran.

Detection is by file name alone. Copying cmd.exe to codex.exe was enough to set the Codex bit. A copy named gcc.exe set the compiler and debugger category, which covers GCC, Clang and related tools as one bit.

Step-by-step process

Step 1: Check your diagnostic data setting (2 minutes)

Open Settings, then Privacy & security, then Diagnostics & feedback. In the researcher's clean US install of Windows 11 Home ARM64, the toggle was already enabled and labelled Include Optional before any privacy choices were changed, and AllowTelemetry was 3. If yours matches, the report is eligible for upload.

Step 2: Turn off optional diagnostic data (1 minute)

Switch off Send optional diagnostic data on the same page. The agent-usage report is treated as optional diagnostic data, so it is queued for upload only when optional diagnostic data is allowed. On new machines, decline optional diagnostics during setup instead.

Step 3: Confirm the component is present (optional, 10 minutes)

In an administrative PowerShell session, check that the DiagTrack service (Connected User Experiences and Telemetry) is running. In the researcher's Windows 11 build 26200.9974 virtual machine it was set to Automatic and spawned a child process, AggregatorHost.exe, which loaded MissionControlAggregator.dll. The feature that guards the agent checks is named CLICodingAgentUsage, feature ID 62580080, and it was already enabled as a service experiment.

Step 4: Verify the queue (advanced)

The researcher inspected DiagTrack's EventStore.db and decompressed the JSON batches in its AsimovEvents table, finding the Segments.SubCohorts event queued for upload with optional data allowed. Do this on a test machine, not a work laptop.

Common mistakes to avoid

  • Assuming only WSL is affected. A regular Windows codex.exe reaches the checks through the app-state route.
  • Reading the bitmap as usage time. It records that a tool was observed in a window, nothing more.
  • Testing on your daily machine. Renamed binaries such as a fake codex.exe will trip the detection and clutter your state.
  • Believing a policy default applies everywhere. The researcher only confirmed the default for a US-region setup; check your own machines.

Tips that make a difference

  • Check images, not just machines. If you deploy Windows from a standard build, set diagnostic data once in the image rather than relying on each user.
  • Remember the data is categorical. Seeing one bit set for a compiler category says little about which compiler, but a Codex or Claude bit points to an executable with that name.

What this means for the UK and US

For IT teams in firms that restrict AI tooling, a quiet record of which agents appear on endpoints is both a potential privacy issue and, arguably, a source of information users may not have chosen to share. Teams comparing agent-heavy workflows, such as those described in Claude Code Projects, may want to know which of those tools leave a trace in Windows diagnostics.

Next steps

Audit diagnostic data policy across your fleet, document the decision, and review whether other optional categories need the same treatment. If your developers handle sensitive code, consider the wider exposure of agent tooling too; the Claude Code secrets leak shows how developer tool metadata and files can travel further than intended.

Summary

You now know what Windows 11's MissionControlAggregator component records, why a renamed file is enough to trigger it, how to check whether optional diagnostic data is enabled, and how to turn it off under Settings, Privacy & security, Diagnostics & feedback.

Frequently asked questions

Does Windows 11 track which coding agents I use?

Yes. A Windows component recognises executable names such as codex.exe, claude.exe, copilot.exe and cursor.exe, records them as a bitmap, and queues the report for upload when optional diagnostic data is allowed.

Is the coding agent telemetry on by default?

In the clean US install of Windows 11 Home ARM64 tested, the Diagnostic data toggle was already set to Include Optional and AllowTelemetry was 3, so yes.

Does the report contain my prompts or source code?

The researcher found no prompt text or source code in the report. It carries a bitmap of which tools were observed during a roughly daily window, not usage time.

How do I stop Windows sending this data?

Turn off Send optional diagnostic data under Settings, Privacy & security, Diagnostics & feedback, or decline optional diagnostics during setup.

More from Future Technology HQ