GoKawiilTelemetry
GitHub CLI sends pseudoanonymous telemetry to help us improve the product. We want you to understand what is being sent and why.
Why we collect telemetry
As agentic adoption of GitHub CLI grows, our team needs visibility into how features are being used in practice. We use this data to prioritize our work and evaluate whether features are meeting real user needs.
For example, when we ship a new subcommand, we want to understand whether anyone is using it and how. If adoption is low, we know we need to revisit the feature's discoverability or design. If a subcommand sees high usage with certain flags, that tells us where to invest in a better experience.
Reviewing telemetry
GitHub CLI is open source, you can review the telemetry implementation in the cli/cli repository. However, if you want to see exactly what would be sent without actually sending it, you can enable logging mode using either an environment variable, or configuration option.
Environment variable:
export GH_TELEMETRY=log
CLI config:
... continue reading