Windows 11 diagnostics record which coding agents and developer tools run
Original title: Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use
MissionControlAggregator sets usage bits and uploads them with optional diagnostic data, which is on by default.
A reverse-engineering write-up of MissionControlAggregator.dll finds comparisons against coding-agent and developer-tool executable names. Matches are stored as bits and emitted in a Segments.SubCohorts ETW report, then uploaded to Microsoft through Windows Diagnostics unless optional diagnostic data is disabled. The author observed the feature already enabled on a Windows 11 ARM64 VM, with DiagTrack running and AggregatorHost.exe loading the DLL. The report does not appear to include prompt text or source code.
Unconfirmed: Findings come from reverse engineering one Windows 11 ARM64 build; Microsoft has not confirmed the telemetry scope.
- CLI slots include copilot.exe, claude.exe, codex.exe, and agy.exe.
- Desktop slots include github.exe, claude.exe, codex.exe, cursor.exe, and antigravity.exe.
- Feature CLICodingAgentUsage, ID 62580080, was enabled without a manual opt-in.
- Observed DLL version 10.0.26100.9818 on Windows 11 build 26200.9974.
- Some checks also match publishers such as Python Software Foundation.
- Vendors
- Microsoft
From the original article
7 min read at xusheng.dev
Reverse engineering Windows 11's MissionControlAggregator reveals coding-agent and developer-tool usage bits in a diagnostic ETW report. I recently asked AI to help me look through the latest Windows binaries for undocumented features and functionality. Among the leads it turned up, one list immediately caught my attention: coding agents such as codex.
By cwaffles · xusheng.dev
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.