GitHub Enables Telemetry Collection by Default for CLI Users, Raises Privacy Concerns

GitHub has quietly rolled out a new feature that enables client-side telemetry collection by default in its command-line interface (CLI). The update, which began with the v2.91.0 release on April 22, 2026, aims to gather usage data to improve the CLI and better understand how features are utilized, particularly as AI agents become more prevalent.

What Changed Technically

• Telemetry Enabled by Default: GitHub's CLI now collects pseudonymous client-side telemetry out of the box. This means that every time you use the CLI, it sends usage data back to GitHub.
• No Standalone Announcement: The change was announced via an update to the telemetry documentation and a brief mention in the release notes, rather than a dedicated blog post or press release.
• Data Collection Goals: According to GitHub, the data will help them understand feature usage patterns, prioritize development efforts, and evaluate whether features are meeting real user needs. The telemetry is particularly focused on interactive workflows and AI-driven interactions.

Key Details

• What Data Is Collected?:
  • Usage Patterns: Information about which commands and features you use.
  • Error Logs: Data about any errors or issues encountered during CLI usage.
  • Performance Metrics: Insights into how the CLI performs in different scenarios.
• Pseudonymous Data: The data collected is pseudonymized, meaning it's associated with a unique identifier but not directly linked to your personal information.

Implementation and Transparency

• Open Source Repository: GitHub's CLI is open source, so you can review the telemetry implementation in the cli/cli repository. However, the documentation does not provide a comprehensive list of data points collected.
• Logging for Inspection: If you want to see exactly what data would be sent, you can enable logging. This allows you to inspect the telemetry payload before it's transmitted.

Opt-Out Instructions

If you prefer not to share your usage data with GitHub, you can opt out by running the following command:

gh config set analytics opted-out true

This will disable telemetry collection for your CLI sessions.

Privacy Concerns and Community Reaction

While the addition of telemetry is a common practice in software development, enabling it by default without clear communication has raised concerns among privacy-conscious developers. The lack of a detailed list of data points collected adds to these concerns.

• Transparency Issues: Users expect clear and upfront information about what data is being collected and why.
• Opt-Out Visibility: Making opt-out instructions more prominent could help alleviate some of the privacy concerns.

GitHub's Stance

A GitHub spokesperson provided the following statement:

"GitHub CLI now includes client-side usage telemetry, beginning with the v2.91.0 release today, to better understand how developers use the tool across both interactive and increasingly agentic workflows. Telemetry is enabled by default with a clear opt-out. These insights will help the team identify friction points and prioritize the features that matter most, particularly as usage patterns evolve with the rise of AI agents. GitHub CLI is open source, so you can review the telemetry implementation in the cli/cli repository."

Conclusion

Enabling telemetry by default without a clear announcement or detailed documentation has sparked a debate within the developer community. While data collection can provide valuable insights for product improvement, it's crucial to maintain transparency and respect user privacy. If you're concerned about your data, consider opting out and staying informed about future updates.