Windows 11 logs AI coding tools by default

A translucent digital mesh overlaying a cluttered developer desk, with faint glowing outlines highlighting specific tool silhouettes — a terminal, a compiler icon, an AI chip — while thin streams of l

A recently uncovered feature in Windows 11 logs the use of AI-powered coding agents and common developer tools, storing and potentially transmitting the data to Microsoft. The telemetry is part of a broader diagnostics system that activates by default unless users explicitly opt out during setup or later in settings.

The data collection is handled by a component called MissionControlAggregator.dll, which monitors process executions through Windows event channels. It specifically checks for executables associated with tools like GitHub Copilot (copilot.exe), Anthropic’s Claude (claude.exe), OpenAI’s Codex (codex.exe), Cursor (cursor.exe), and standard development environments including python.exe, node.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, and code.exe (VS Code). Some checks also verify the publisher: Python Software Foundation for python.exe, Microsoft Corporation for .NET and Visual Studio tools, and Node.js Foundation for node.exe. The compiler/debugger group (including GCC and Clang) has no publisher verification in this telemetry path.

How the tracking works

The system does not actively scan running processes. Instead, it subscribes to existing Windows diagnostic events: KernelProcess.AppStateChangeSummary and Win32kTraceLogging.AppInteractivitySummary for Windows applications, and Microsoft.Windows.Lxss.Manager.Exec for WSL (Windows Subsystem for Linux) processes. A match on executable name — such as codex.exe or gcc.exe — triggers a flag in the component’s internal state.

Each detected tool sets a bit in a bitmask stored locally at C:\ProgramData\Microsoft\Diagnosis\AggregatorStorage\MissionControlAggregator$. The report, named Segments.SubCohorts, is emitted via ETW (Event Tracing for Windows) and includes no usage duration, focus time, or resource metrics — only presence during the reporting window. The bitmasks cover:

  • 4 CLI agent slots: copilot.exe, claude.exe, codex.exe, agy.exe
  • 5 desktop agent slots: github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe
  • 12 broader developer tool categories, including scripting runtimes, compilers, debuggers, and IDEs

The feature is guarded by a service experiment flag: CLICodingAgentUsage (feature ID 62580080).

Data flow to Microsoft

The telemetry remains local unless optional diagnostic data is enabled. In a default US Windows 11 Home ARM64 installation (build 26200.9974) tested using the official ISO, this setting was enabled as ‘Include Optional’ without user intervention. The registry value AllowTelemetry was set to 3, confirming transmission of optional data.

When enabled, the Segments.SubCohorts event appears in DiagTrack’s upload queue (EventStore.db) with a privacy flag isRequired: false, indicating it is optional. Independent verification shows the JSON payload containing the bitmasks is queued for transmission to Microsoft via the Connected User Experiences and Telemetry (DiagTrack) service.

The public ISO’s baseline image had the CLICodingAgentUsage feature disabled by default, suggesting Microsoft may be rolling it out selectively via service experiments, not universally across all installations.

Scope and limitations

The tracking is based primarily on executable filenames. For some tools — including Python, Node.js, .NET, and Visual Studio — the component also checks the digital publisher signature. However, tools in the compiler/debugger category (e.g. gcc.exe, clang.exe) are grouped under a shared category and do not require publisher verification in this telemetry path.

Testing confirmed that renaming cmd.exe to codex.exe or gcc.exe triggers the respective flags, proving the mechanism is active and responsive to naming alone. This suggests false positives are possible, but also confirms detection works through standard Windows event pipelines.

What it means

For developers and organisations in the UK, UAE, US, and Kazakhstan, this telemetry raises concerns about data sovereignty and operational transparency. Even locally run AI coding tools, which do not contact external servers, are logged and potentially reported. While Microsoft states such data improves system reliability and developer experience, the lack of upfront disclosure and opt-in by default contradicts principles of data minimisation and user control.

Businesses relying on Windows 11 in regulated environments should audit their diagnostic settings and consider disabling optional telemetry. Founders and IT teams should treat any executable name matching Microsoft’s list as potentially logged, especially in shared or cloud-hosted desktop environments.

Microsoft’s documentation confirms optional diagnostics can be disabled via Settings → Privacy & security → Diagnostics & feedback. Enterprises can also use Group Policy or Intune to enforce telemetry levels. Given the default setting, most individual users and small teams are likely transmitting this data unknowingly.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *