Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use
- ID
- 47298
- Status
- summarized
- Published
- 17 Nov 2026, 6:58 AM
- Fetched
- 17 Nov 2026, 11:10 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://xusheng.dev/posts/windows-coding-agent-telemetry/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 17 Nov 2026, 11:10 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
A reverse-engineering write-up of Windows 11's MissionControlAggregator.dll found executable-name checks for coding agents including codex.exe, claude.exe, copilot.exe, cursor.exe, agy.exe, and antigravity.exe, plus WSL equivalents, under feature ID 62580080 named CLICodingAgentUsage. The same component checks developer tools such as node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, and code.exe, records usage locally, and reports it to Windows Diagnostics; unless optional diagnostic data is opted out, that data is uploaded to Microsoft. The Hacker News thread had 295 points and 165 comments.
Why it matters
If you run AI coding agents or dev toolchains on Windows 11, this is a default-on telemetry path to review: check Settings > Privacy & security > Diagnostics & feedback and decide whether optional diagnostic data should stay enabled on work machines. The finding appears to cover executable usage bits rather than code contents, so the practical decision is about metadata leakage and team policy, not a code-exfiltration panic.
Discussion angle
Where should teams draw the line between benign OS product telemetry and developer-tool usage metadata, and would you change Windows diagnostic defaults for machines running AI coding agents?