Windows 11 quietly tracks which AI coding agents you run
A security researcher has found an undocumented component in Windows 11. It records whether programs like Codex, Claude, Copilot or Cursor run on your PC. If optional diagnostics are turned on, the result goes into Microsoft's telemetry upload queue.

What's going on
Windows 11 has a built-in component that records whether certain AI coding agents and developer tools run on your PC. The list includes OpenAI's Codex, Anthropic's Claude, Microsoft's Copilot and Cursor. If optional diagnostics are turned on, this information can be sent to Microsoft. The finding comes from Xusheng Li, a security researcher and developer on the analysis tool Binary Ninja. He posted a first hint on X on November 16, 2026, and followed it with a detailed technical write-up. Cyber Security News reported on it. The feature isn't documented, and Microsoft hasn't explained it so far.
AI coding agents are programs that write code on their own, run commands in the terminal and edit files. For many developers they're now part of the daily routine.
How it was found
Ironically, Li found the feature with the help of AI. He had an AI assistant comb through current Windows files for undocumented features. In the system file MissionControlAggregator.dll, the assistant came across a list of program names. It included codex.exe, claude.exe, copilot.exe and cursor.exe, along with common developer tools such as python.exe, dotnet.exe, gcc.exe (a C compiler) and code.exe (Visual Studio Code).
Li then took the file apart in Binary Ninja, a tool for disassembling and analyzing compiled programs (reverse engineering). It showed that the names are used in simple comparisons. The checks are switched on by a feature flag, an internal switch Microsoft can use to enable features on specific devices. It's called CLICodingAgentUsage. CLI stands for command line interface, meaning programs you run from the command line.
What the component actually does
The DLL doesn't actively scan running programs. Instead, it listens to events Windows generates anyway, such as KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary. It also picks up launch events from WSL, the Windows Subsystem for Linux, which lets Linux programs run on Windows. But the check isn't limited to Linux tools. A plain Windows build of codex.exe also triggers a match.
When a program name matches the list, the component sets a bit, a yes/no flag, in its saved state. Later it sends a report called Segments.SubCohorts via Event Tracing for Windows (ETW), Windows' built-in event logging system. According to Li, the report only contains yes/no flags: no run time, nothing about how long a program was in the foreground, and no prompt text. Even so, Cyber Security News points out that a list of the AI tools a developer uses is private information.
The name "SubCohorts" suggests users are sorted into groups, such as "uses Codex" or "uses compilers". That's an interpretation, though. Microsoft hasn't confirmed it.
Proof in testing
Li examined a Windows 11 ARM64 virtual machine on build 26200.9974. The feature was already on there, and the telemetry service DiagTrack was running. DiagTrack launched AggregatorHost.exe, which in turn loaded the DLL. For his test, Li copied the command prompt cmd.exe and renamed the copy codex.exe. The name alone was enough to set the Codex bit: a report then showed the entry CliAgentSubCohorts with the value 4. A copy named gcc.exe set a separate bit for developer tools.
So Windows only checks the file name, not whether an AI agent is actually running.
A local log entry doesn't prove that data leaves the device, though. So Li dug further. He found that a DiagTrack listener subscribes to the report, and that it showed up in DiagTrack's upload queue. There it was marked as "not required". That means Microsoft classifies it as optional diagnostic data. Windows distinguishes between required data, which is needed for security and basic operation, and optional data, which reveals more about how you use the device.
| Check | Result according to Li |
|---|---|
| Test system | Windows 11 ARM64, VM, build 26200.9974 |
| Feature flag CLICodingAgentUsage | active on the test system |
| Data collected | yes/no bits only, no prompts, no run time |
| Classification | optional diagnostic data |
| Clean install of Windows 11 Home (US) | optional diagnostics on by default, AllowTelemetry = 3 |
| VM from public ISO | coding agent feature off |
On a fresh US install of Windows 11 Home, optional diagnostics were on by default, with AllowTelemetry set to 3, the highest level. On a comparison machine set up from the public installation image (ISO), the coding agent feature was off. So there's no evidence that it runs on every Windows PC. Microsoft apparently enables it only on a subset of devices.
How to turn it off
If you don't want this, open Settings → Privacy & security → Diagnostics & feedback and turn off "Send optional diagnostic data". According to Microsoft's own privacy guide, your device stays secure and works normally with required data alone. The same guide explicitly lists device activity as something optional data may include, which fits this case. On managed company PCs the setting is often hidden. IT departments should check their policies.
Why this matters for security
Cyber Security News puts the finding in a broader context. AI coding tools are a popular target for attackers. Info-stealers, malware that grabs credentials and files, now specifically hunt for stored Claude, Cursor and Codex data on developer machines. A record of who uses which agent isn't a secret key. But it does show which devices are likely to hold valuable code and access tokens.
The bottom line
The finding is technically well documented, but its scope is limited. It's about a handful of yes/no flags, not monitoring of your input or code. The data counts as optional telemetry and can be turned off with a single switch. Two other points are more troubling. The feature is undocumented, and optional diagnostics were on by default, at least on a fresh US install of Windows 11 Home. If you never knowingly agreed, you probably had no idea.
The obvious explanation is that Microsoft wants to know which rival agents developers use. The company has its own horse in the race with Copilot, and Windows keeps gaining more agent features. Cyber Security News suspects product planning is the goal. That's unconfirmed, and Microsoft has yet to comment. It's also unclear how many devices actually have the feature flag turned on and what Microsoft does with the data. Until then, it's worth checking your own diagnostics settings.
Sources
- Bing News (en-US) cybersecuritynews.com
- thewindowsclub.com thewindowsclub.com
- markets.businessinsider.com markets.businessinsider.com
- networkworld.com networkworld.com
- dev.to #ai dev.to
Ask the AI assistant
Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.
The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.
Comments
What do you think? Already tried it? Write it here, no sign-up needed.
Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.