Researcher Xusheng Li reports that a Windows 11 component matches selected coding-agent and developer-tool executable names, then records matching categories in a Segments.SubCohorts event. Li found the event in DiagTrack’s local upload queue, where it was marked as optional diagnostic data. His account describes a queued event, not a confirmed server receipt. Li’s technical account details the tests behind the finding.

A category bit records a name match, not a coding session.

What does the reported event record?

Li traced the checks to MissionControlAggregator.dll and a feature called CLICodingAgentUsage. In his test, the event contained bitmaps for four command-line agent slots, five desktop-agent slots, and 12 developer-tool categories. Those bits indicate which categories were observed during a collection window; they do not measure how long a tool was used.

Category groupReported slots or categoriesWhat the value represents
Command-line coding agents4Agent-name categories represented in the bitmap
Desktop coding agents5Desktop-agent categories represented in the bitmap
Developer tools12Broader developer-tool categories represented in the bitmap

Li says the event he inspected contained category bitmaps rather than prompt text or source code. The component also appeared to discard richer input details, such as runtime and interaction counters.

How does executable-name matching work?

Binary Ninja analysis interface showing executable-name strings, including `codex.exe`, `claude.exe`, `copilot.exe`, and `cursor.exe`, alongside a MissionControlAggregator reference.

The component uses executable-name checks against existing Windows application events and events from the Windows Subsystem for Linux (WSL). In a controlled test, Li renamed a copy of cmd.exe to codex.exe; that name was enough to set the Codex CLI bit. The match therefore identified a filename, not whether the file was the genuine Codex CLI. Li’s test used Windows 11 ARM64 build 26200.9974 and MissionControlAggregator.dll version 10.0.26100.9818.

What does the local queue show, and where can you change the setting?

Windows setup privacy page with the “Include Optional” diagnostic-data switch selected.

Li found Segments.SubCohorts in DiagTrack’s local upload queue, marked isRequired: false. A queue entry records the event at the local staging point; Li’s observation does not document a completed transfer to Microsoft.

Microsoft documents the Windows 11 control under Settings → Privacy & security → Diagnostics & feedback. Turn off Send optional diagnostic data to stop selecting optional diagnostics; required diagnostic data remains. Microsoft says Windows stays secure and operates normally with required diagnostics only, and an organization may restrict the setting on a managed device. Microsoft’s Windows diagnostics guidance describes the control.

In a clean, US-configured Windows 11 Home ARM64 setup, Li observed Include Optional selected. That observation describes the setup he examined.