500xEngineer.

All postsSHORT2 min read

Windows 11 Coding-Agent Reporting: What a Researcher Found

Xusheng Li reports optional Windows 11 diagnostics recording which agents were seen. Here's what he tested, the limits, and how to stop optional uploads.

Windows 11 may report which coding agents you've used to Microsoft, according to a researcher. Xusheng Li published his reverse-engineering write-up on Nov 16, 2026. The control to check is optional diagnostic data.

Video not loading? Watch the Short on YouTube

What the researcher found

Li reports that a Windows 11 component called MissionControlAggregator.dll checks coding-agent file names. His write-up lists these matches:

Category File names
CLI agents claude.exe, codex.exe, copilot.exe, agy.exe
Desktop agents github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe

He also found checks for developer tools including node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe and code.exe.

According to Li, the report uses bitmaps for observed agent slots and developer-tool categories. He says this component appears to discard runtime, focus time and interaction counters. The report is labelled optional diagnostic data. When optional diagnostics are allowed, he says Windows queues it for upload to Microsoft.

The write-up reached the Hacker News front page with 532 points at the recorded check.

How it was tested

In Li's test, he copied cmd.exe to a file named codex.exe. That set the Codex bit. The file name alone was enough to trigger the match in his test.

He also tested a clean US install of Windows 11 Home ARM64, where optional diagnostic data was enabled by default.

What is and is not known

This is one researcher's reverse-engineering and testing. His baseline VM from the public ISO had the coding-agent feature disabled by image default. That limits the conclusion: the report doesn't establish that this feature is active on every Windows PC.

Li found no prompt text or source code in this report. That finding applies to the report he examined. No Microsoft statement about the agent-specific finding was found as of Nov 17, 2026.

Microsoft's support page says optional diagnostic data may include device activity information. Its explanation of diagnostics doesn't confirm Li's specific finding.

How to check your setting

Follow the Microsoft diagnostics guide:

To stop optional uploads:

  1. Open Settings, Privacy and security.
  2. Open Diagnostics and feedback.
  3. Turn off Send optional diagnostic data.

This only stops optional uploads; the write-up doesn't show it stops local detection.

Li gives the same route to turn off optional diagnostics. You can also decline optional diagnostic data during setup. Changing the setting costs nothing. Microsoft says your device remains just as secure and works normally when you choose to stop sending optional diagnostic data.

The builder angle (my opinion, no income guaranteed)

I'd sell small teams a dev machine privacy checkup. Check the diagnostic setting on every PC, list installed coding agents, and move API keys out of plain text.

My suggested deliverable is a checklist showing each machine's setting, agent inventory and where its API keys live. That's a service idea, with no income guaranteed. Li's report doesn't claim Microsoft collected those keys.

Daily email

Get each breakdown in your inbox.

One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.

Read past emails on Substack

Sources

All postsWatch on YouTube