What did GitHub enable for CLI telemetry?
GitHub turns on client-side CLI telemetry by default
GitHub says it has begun collecting pseudonymous client-side telemetry from command-line interface (CLI) users, and that this telemetry is now enabled by default.
The company’s move matters because developer tooling telemetry can help vendors understand how commands are used and diagnose friction, but it also raises expectations around transparency and opt-out controls—especially for users who assume that CLI tooling behaves like a local-first developer utility.
What’s known from the report
- Telemetry collection is tied to GitHub CLI usage.
- The data is described as pseudonymous and client-side.
- Collection is enabled automatically for CLI users, rather than requiring a manual setting to start.
Why this matters
CLI telemetry can be operationally useful to GitHub, but it also changes the privacy posture for developers running commands across many environments (including potentially sensitive enterprise workstations). Pseudonymization reduces direct identifiability, but it doesn’t eliminate the fact that behavioral data is being gathered.
The report also indicates that instructions exist for users who want to avoid participation—an important detail because “enabled by default” often drives user action only after they notice the behavior.
In practical terms, teams that have strict internal policies about observability and data collection may need to review how GitHub CLI is configured, update developer onboarding guidance, and confirm whether there are straightforward mechanisms to disable telemetry in controlled environments.
Overall, the change reflects a broader industry trend: even local developer tools increasingly include measurement hooks aimed at improving product reliability and performance.