Inter-office memo
- To
- Everyone running coding agents on Windows 11
- From
- Mo, Chief Executive
- Date
- November 16, 2026, 6:13 PM CST
- Re
- Windows 11 and your coding agents
Windows 11 can tell Microsoft which coding agents you run. How to check and stop it
On November 16, 2026, researcher Xusheng Li reported that Windows 11 can note which of Claude, Codex, GitHub Copilot, Cursor and Antigravity you run and, with optional diagnostic data on, send Microsoft a record of which ran each day or so, without prompts or code. Microsoft hasn’t commented. Turning off Send optional diagnostic data in Settings stops the upload.
What Li found
Xusheng Li, a developer of the Binary Ninja reverse-engineering tool at Vector 35, posted the first finding on X late on November 15, US time, and published his full analysis on November 16, 2026. Looking through recent Windows system files, he found a list inside MissionControlAggregator.dll, a Windows component: “coding agents such as codex.exe, claude.exe, copilot.exe, and cursor.exe, alongside familiar developer tools such as python.exe, dotnet.exe, gcc.exe, and code.exe.”
Following the code, he found a component that “records which coding agents and developer tools have been used, saves that information locally, and reports it to Windows Diagnostics.” It doesn’t scan your processes itself. It listens to records Windows already keeps about programs starting and apps in use, and to WSL’s records of Linux programs starting. The agent checks sit behind a feature with a plain name: CLICodingAgentUsage.
Then he tested it. He copied cmd.exe to a file named codex.exe and ran it: “The name alone was enough for the component to recognize it as Codex.” With optional diagnostic data on, he found the resulting report in the queue that Windows’ telemetry service, DiagTrack, uploads to Microsoft:
{
"name": "Microsoft.Windows.MissionControlAggregator.Segments.SubCohorts",
"ext": { "privacy": { "isRequired": false } },
"data": {
"Version": "0.1.5",
"CliAgentSubCohorts": [4],
"DesktopAgentSubCohorts": [0],
"FlushedFromSave": true
}
}
The 4 is the Codex bit. His conclusion: “unless you have opted out of the ‘optional’ diagnostic data (which is enabled by default), the data is uploaded to Microsoft.”
What Windows looks for
By Li’s reading, the component has four slots for command-line agents, five for desktop agents and twelve categories of developer tools:
| Group | Names Li found | How Windows sees them |
|---|---|---|
| Command-line agents | copilot.exe, claude.exe, codex.exe, agy.exe, and the same names without .exe in WSL |
Windows’ records of programs starting, and WSL’s records of Linux programs starting |
| Desktop agents | github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe |
Windows’ records of the apps you interact with |
| Developer tools | node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, code.exe and others |
The same records, grouped by category; Node.js, Python, .NET and Visual Studio are also checked for their publisher |
The names match Anthropic’s Claude, OpenAI’s Codex, GitHub and its Copilot, Cursor, and Google Antigravity, whose command-line tool is agy. No other agent is on the lists, though one that runs on Node.js or Python would count under that developer tool. Because the check goes by the program’s file name, it doesn’t matter how an agent starts: from a terminal, an editor or another app.
What it sends, and what it doesn’t
The report is small. Each agent gets a bit, set if Windows saw it during a reporting window of about a day. The records it reads include “runtime, time in focus, interaction counters, and resource usage,” Li writes, but the component “appears to discard those details and record only a bitmap of which agents were observed,” and “the report’s timestamps describe the collection window, not how long each agent was used.” He “found no prompt text or source code in this report.”
It’s still tied to your PC. Microsoft’s privacy page says Windows diagnostic data “is transmitted to Microsoft and stored with one or more unique identifiers that can help us recognize an individual user on an individual device and understand the device’s service issues and use patterns.” With optional data on, it adds, “Microsoft may use or combine Windows diagnostic data with data from other Microsoft products.” Li’s view: “collecting which agents and developer tools someone uses already has significant privacy implications.”
Who it affects
Three things have to line up, by Li’s evidence:
- The component. His PC ran build 26200.9974, which is Windows 11 version 25H2 with Microsoft’s November 10 update, on an ARM64 virtual machine.
- The feature switched on. On that PC, “
CLICodingAgentUsagewas already enabled as a service experiment. I had not manually enabled the feature.” A fresh install from Microsoft’s ISO “had the coding-agent feature disabled by image default, so the evidence does not support saying that it is active on every Windows installation.” - Optional diagnostic data on. In a clean install of Windows 11 Home from the latest ISO, with the region set to the United States, “the Diagnostic data toggle was already enabled and labeled Include Optional.”
Here is what each Windows setting sends, by Microsoft’s documentation, with the agent report as Li describes it:
| Diagnostic data setting | Who can choose it | What Microsoft says it covers about your apps | The agent report |
|---|---|---|---|
| Off | Windows Enterprise, Education and Server only | “No Windows diagnostic data sent” | Not uploaded |
| Required | Every edition; the least Home and Pro can send | “which apps are installed on a device,” and details such as “the total uptime for an app” | Not uploaded: it’s marked optional |
| Optional | Every edition; on in Li’s US setup | “App activity, such as which programs are launched on a device, how long they run, and how quickly they respond to input” | Queued for upload |
By his reading of the code, Linux programs started in WSL go through the same checks, so Claude Code or Codex run inside WSL count too. Macs and Linux PCs aren’t affected: this is a Windows component.
How to check yours
- Look at your setting. Open Settings > Privacy & security > Diagnostics & feedback and see whether Send optional diagnostic data is on. If the options are greyed out and the page says “Some settings are hidden or managed by your organization,” your IT department sets it.
- Watch for the report. On the same page, under View diagnostic data, turn on the Diagnostic Data Viewer and install it from the Microsoft Store. It only shows data sent while viewing is on, so use your PC as usual for a day or two, then search it for
MissionControlAggregator. The report is the eventMicrosoft.Windows.MissionControlAggregator.Segments.SubCohorts. Microsoft warns that viewing “can use up to 1 GB” of disk, so turn it off when you’re done. - See whether the component is loaded. In a terminal run as administrator, Li’s command
tasklist /m MissionControlAggregator.dlllistsAggregatorHost.exeif it is. That shows the component running, not whether the agent checks are switched on.
How to turn it off
- Turn off Send optional diagnostic data on that page. The report is optional data, so that stops the upload. Microsoft says that either way, “your device will be just as secure and will operate normally.”
- Delete what’s already gone. Under Delete diagnostic data, select Delete. Microsoft notes this “does not delete the diagnostic data that is associated with your Microsoft account, nor does it stop your diagnostic data from being sent”; for the former, use the Microsoft privacy dashboard.
- On work PCs, set it by policy. Admins can set Allow diagnostic data under Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds to Required, or the MDM policy
System/AllowTelemetryto1. Enterprise and Education can turn diagnostic data off entirely, with0. - On a new PC, decline it at setup. Windows asks about optional diagnostic data during setup, and in Li’s test the answer was already yes.
What Microsoft hasn’t said
- Anything about it. We found no statement from Microsoft by the evening of November 16, and the notes for its November 10 update don’t mention the component.
- What “Mission Control” is, and what Microsoft uses the report for.
- How many PCs have the feature on. Li saw it switched on as a “service experiment” on one ARM64 machine, and tested the default for optional data in one region, the US.
- Whether the data reaches GitHub, which Microsoft owns and which makes Copilot, one of the agents on the list.
We’ll update this memo if Microsoft explains the component or changes it.
8.Questions.
Does Windows 11 tell Microsoft which coding agents I use?
- It can. Xusheng Li found that Windows 11 build 26200.9974 checks for Claude, Codex, GitHub Copilot, Cursor and Antigravity by their program names and, with optional diagnostic data on, queues a report of which it saw for upload to Microsoft. The check sits behind a feature Windows had switched on for his PC; a fresh install from Microsoft’s ISO had it off.
Does it send my prompts or code to Microsoft?
- Not in this report, by Li’s analysis. It holds one bit per agent and per category of developer tool for each reporting window, and he “found no prompt text or source code” in it. Microsoft says Windows diagnostic data is stored with identifiers “that can help us recognize an individual user on an individual device.”
How do I turn it off?
- Go to Settings > Privacy & security > Diagnostics & feedback and turn off Send optional diagnostic data. Windows marks the report as optional data, so, as Li describes it, that stops the upload. On a work PC, your IT department may set this for you.
Which agents and tools does Windows look for?
- By Li’s reading, copilot.exe, claude.exe, codex.exe and agy.exe as command-line agents, also inside WSL, and github.exe, claude.exe, codex.exe, cursor.exe and antigravity.exe as desktop apps. Developer tools such as Node.js, Python, .NET, GCC, Clang, Java, Visual Studio and VS Code are counted by category.
How can I tell whether my PC sends it?
- Turn on the Diagnostic Data Viewer under Settings > Privacy & security > Diagnostics & feedback, use your PC as usual for a day or two, then search the viewer for MissionControlAggregator. An event named Microsoft.Windows.MissionControlAggregator.Segments.SubCohorts is the report.
What has Microsoft said?
- Nothing about this report, as far as we could find by the evening of November 16, 2026. Its documentation already says optional diagnostic data includes “app activity, such as which programs are launched on a device, how long they run, and how quickly they respond to input.”