Microsoft Windows 11 Secretly Tracks Which AI Coding Agents Developers Use Through Telemetry

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Windows 11 has a built-in component that notes which AI coding agents and developer tools you run. It sends that data to Microsoft if optional diagnostic data is on.

Security researcher Xusheng Li, who works on Binary Ninja, shared the first finding on X on November 16, 2026. He then published a full technical write-up.

Windows 11 AI Agent Tracking

Li asked an AI helper to look through recent Windows files for undocumented features. It flagged a list of names inside MissionControlAggregator.dll, including codex.exe, claude.exe, copilot.exe, and cursor.exe.

The same list held common tools like python.exe, dotnet.exe, gcc.exe, and code.exe. Li opened the file in Binary Ninja and found that the names were used in simple comparisons. A feature flag called CLICodingAgentUsage guards the new checks.

Binary Ninja Agent Strings (Image Source: Xusheng)

The DLL does not scan your running programs. It listens to events Windows already creates, such as KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary.

It also reads WSL launch events. A normal Windows copy of codex.exe can trigger a match, so the check is not limited to Linux tools.

When a name matches, the component sets a bit in its saved state. Later, it sends a report called Segments.SubCohorts through Event Tracing for Windows. The report holds only yes-or-no flags, not runtime, focus time, or prompt text. Even so, a list of the AI tools a developer uses is private information.

Li checked a Windows 11 ARM64 virtual machine on build 26200.9974. The feature was already on, and the DiagTrack telemetry service was running. DiagTrack started AggregatorHost.exe, which loaded the DLL. To test it, he copied cmd.exe and renamed it codex.exe.

The name alone was enough to set the Codex bit. A report then showed CliAgentSubCohorts with a value of 4. A copy renamed gcc.exe set a separate developer-tool bit.

Li did not stop at the local event, because local logs alone prove nothing. He found that a DiagTrack listener was subscribed to the report. The report also appeared in DiagTrack’s upload queue, marked as not required.

That means Microsoft treats it as optional diagnostic data. On a clean US install of Windows 11 Home, optional data was on by default, and AllowTelemetry was set to 3. A baseline VM from the public ISO had the coding-agent feature off. So this is not proven to be active on every Windows PC.

Windows Optional Diagnostic Settings
Windows Optional Diagnostic Settings (Image Source: Xusheng)

Open Settings, then Privacy & security, then Diagnostics & feedback. Turn off Send optional diagnostic data. Microsoft’s own diagnostics and privacy guide says your device stays secure and works normally with only required data.

It also says optional data can include device activity, which fits this case. Managed work PCs may hide this setting, so IT teams should check their own policies.

AI coding tools already draw attention from bad actors. Cyber Security News recently reported that info-stealing malware now targets Claude, Cursor, and Codex data saved on developer machines.

It also covered new threats against AI coding tools that steal credentials. A record of who uses which agent is not a secret key, but it shows where valuable code and tokens may sit.

Microsoft has not yet explained why it collects this data. It may be for product planning, since Windows is adding more agent features.

Until the company speaks, developers should check their diagnostic settings, read Li’s evidence, and decide what they are comfortable sharing.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.

The post Microsoft Windows 11 Secretly Tracks Which AI Coding Agents Developers Use Through Telemetry appeared first on Cyber Security News.