On November 16, 2026, researcher Xusheng Li published a reverse-engineering write-up of a Windows 11 component that can record which coding agents and developer tools ran on a PC.
The report he captured is a daily seen bitmap of matching executable names, not a log of prompts or source code. The work is one researcher's reverse engineering, and the feature has not been shown to be active on every Windows 11 install.
Optional diagnostic data was already on in the US Windows 11 Home test he ran. Microsoft's diagnostics page says you choose that setting when you set up the device. I could not find a public Microsoft response as of November 17, 2026.
The Hacker News thread had 661 points and 519 comments as of 1:46 PM Europe/London on November 17, 2026. I am going by Li's post, not a test I ran on my own machine.
What a researcher found in a Windows 11 component
Li started from executable names embedded in MissionControlAggregator.dll, including claude.exe, codex.exe, cursor.exe, and copilot.exe. The feature that gates the new agent checks is named CLICodingAgentUsage.
The match list is longer than those four names. Four CLI-agent slots check copilot.exe, claude.exe, codex.exe, and agy.exe, plus extensionless equivalents on the WSL path. Five desktop-agent slots check github.exe, claude.exe, codex.exe, cursor.exe, and antigravity.exe.
The same component also groups ordinary developer tools, such as python.exe, node.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, and code.exe, into twelve broader categories.
Li tested a Parallels Windows 11 ARM64 VM, build 26200.9974, where the feature was already enabled as a service experiment, and a clean US Windows 11 Home ARM64 install for the diagnostic-data default. A service experiment is not the same thing as a setting that is on for every install.
Secondary recaps followed on November 17. They restate Li's findings, and none of the ones I found reports an independent reproduction.
6 things to check about what your dev machine reports on your agent use
The six checks below are my structure, drawn from Li's write-up and Microsoft's diagnostics page, not a list Microsoft published.
- Whether optional diagnostic data is on
- Whether this component is actually running on this machine
- Which names the component matches, including WSL
- What actually leaves the machine: a daily seen bitmap
- Name-only matching can fire on a renamed executable
- Managed devices, region, and what official docs do and do not say
1. Whether optional diagnostic data is on
The agent-usage report Li captured was marked optional, not required ("isRequired": false). On a clean install of Windows 11 Home ARM64 with the region set to the United States, he found the Diagnostic data toggle already enabled and labeled Include Optional, and AllowTelemetry set to 3.
He did not test other regions. Microsoft's support page describes optional diagnostic data as extra detail about the device, and says it may include websites browsed, device activity (sometimes called usage), and enhanced error reporting.
Microsoft also says it collects some optional data from only a sample of devices, and the Diagnostic Data Viewer shows whether a device is in that sample.
The same guide also says: "When you set up your Windows device for the first time, you can choose to send optional diagnostic data to Microsoft." The page does not name this aggregator or coding agents, and the text I opened does not state a single worldwide default.
Check whether Send optional diagnostic data is still on under Settings, Privacy & security, Diagnostics & feedback.
2. Whether this component is actually running on this machine
DiagTrack, the Connected User Experiences and Telemetry service, was running Automatic on Li's VM. The service started AggregatorHost.exe, and that child process loaded MissionControlAggregator.dll.
CLICodingAgentUsage was already on as a service experiment. He had not turned it on himself. A blog post about one VM is not proof that the same component is loaded on this PC.
Li describes the process and DLL he observed. From an admin prompt, tasklist /m MissionControlAggregator.dll shows whether AggregatorHost.exe has the DLL loaded, which is the check Li ran.
3. Which names the component matches, including WSL
The match list is broader than the four best-known agents. The CLI slots include agy.exe. The desktop slots include antigravity.exe and github.exe. Everyday tools sit in twelve categories.
WSL exec events can also feed the CLI matchers, and a normal Windows codex.exe can reach those matchers through the app-state summary path. Some tool checks also compare a publisher name. The GCC and Clang group does not, on the path Li describes.
If the feature is on, check which tools on this machine could turn on a bit.
4. What actually leaves the machine: a daily seen bitmap
The report is named Segments.SubCohorts (event Microsoft.Windows.MissionControlAggregator.Segments.SubCohorts, version 0.1.5 in his capture). ReportCohorts<12,4,5> turns matches into bits for twelve tool categories, four CLI agents, and five desktop agents.
An on Codex bit means a matching name was seen in the window. The bit does not mean Microsoft received prompts, source, or how long the tool ran. Li says the source events contain runtime and focus data, and that this component appears to discard those details.
He found no prompt text or source code in the report. The window is roughly daily. The honest description is a usage bitmap, not a keylogger.
5. Name-only matching can fire on a renamed executable
Li copied cmd.exe to codex.exe and ran it. The name alone turned on the Codex CLI bit. A gcc.exe copy turned on the shared compiler and debugger category, not a unique GCC bit.
A match is a filename match, not proof that the real product ran. Local state, if you look at it, only tells you that a matching name appeared.
6. Managed devices, region, and what official docs do and do not say
Li's default-on finding is for a US clean install he tested. Other regions are untested in his post. On a work PC, an administrator may lock diagnostic settings, which can mean a user cannot turn optional data off.
Microsoft's public diagnostics page explains required versus optional data and the Settings path. The page also says that if the options are unavailable, the device may be managed by a workplace or organization. The page does not document this aggregator, the agent name list, or the bitmap.
No Microsoft comment on the finding was found on November 17, 2026. The review questions are whether this is a personal device you can reconfigure, or a managed one, and whether Microsoft has said anything new since the post.
What this finding does not show
The post does not show that Microsoft is collecting prompts or source code in this report. The post does not show that every Windows 11 install is uploading agent-usage bits.
Turning off optional diagnostic data is the opt-out Li describes for this report. The switch is broader than coding agents alone. Privacy concerns about a seen bitmap of developer tools are still real, and they should be stated without inflating the evidence.
Microsoft's Diagnostic Data Viewer, linked from the same Settings page, is the official way to look at what a PC is sending. The viewer shows events in real time while it runs, not a history.
Choose Qodo when the review should follow the code, not the OS log
Windows diagnostic data is about what the operating system may report. Review is about the code an agent or a person writes. Whichever agent ran on the machine, Qodo, the AI code review platform, can review the change locally inside your coding agents and again on the pull request, with full codebase context.
In the Qodo portal, under Configurations, Custom instructions, or in .pr_agent.toml under [review_agent] as issues_user_guidelines and compliance_user_guidelines, a team can add instructions for the kinds of changes agents often open.
The same checks can live in a pr_compliance_checklist.yaml file at the repository root, which Qodo uses during code review to surface violations as findings. Qodo flags; your team decides.
Windows diagnostic settings stay in Settings, or with your administrator. The finding is not about Qodo. I have also written about how teams write a policy for Copilot, Cursor, and Claude Code in review, which is a different question from what the operating system reports.
Qodo is the AI code review platform with high-precision PR review, full codebase context, enforceable rules, and local review inside your coding agents.
FAQ
Is Windows 11 logging which coding agents I run?
A Windows 11 component can record a daily seen bitmap of matching agent and tool names when the feature is active and optional diagnostic data is on. The claim comes from Li's reverse engineering, not from a Microsoft announcement.
Does this upload go out on every Windows 11 PC?
The finding has not been shown to be active on every install. Li found the feature already enabled as a service experiment on his VM, and found optional diagnostic data already on in one US Home test.
Does Microsoft receive my prompts or source code in this report?
Li found a seen bitmap, not prompts or source. He also says the component appears to discard runtime and focus details that were present in the source events.
How do I turn off optional diagnostic data?
During setup, you can decline optional diagnostics. Later, go to Settings, Privacy & security, Diagnostics & feedback, and turn off Send optional diagnostic data. Microsoft's diagnostics and privacy page documents the path.
Which agent and tool names does the component match?
The CLI slots are copilot.exe, claude.exe, codex.exe, and agy.exe, plus extensionless WSL names. The desktop slots are github.exe, claude.exe, codex.exe, cursor.exe, and antigravity.exe. Twelve broader categories cover ordinary developer tools.
Does a match prove that Cursor, Claude, or Codex actually ran?
No. Li copied cmd.exe to codex.exe and the name alone turned on the Codex CLI bit. A match is a filename match.
Does this also see tools inside WSL?
WSL exec events can feed the CLI matchers. A native Windows codex.exe can also reach those matchers, so the path is not limited to WSL.
Is cursor.exe on the CLI list?
No. cursor.exe is a desktop-agent slot, not a CLI slot.
Is the agent-usage report required diagnostic data?
No. The report Li captured was marked optional ("isRequired": false), so it is sent only when optional diagnostic data is on.
Can I confirm what my PC is sending?
Microsoft's Diagnostic Data Viewer is available from the same Settings page. The official diagnostics and privacy page explains how to install and use it.
Has Microsoft commented?
I could not find a public Microsoft response as of November 17, 2026.


Top comments (0)