GitHub CLI begins collecting client-side user telemetry
Briefly

GitHub CLI begins collecting client-side user 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."
"What's less acceptable is turning telemetry on by default and not being particularly clear on what telemetry might be harvested by the CLI."
"If you want to see exactly what would be sent without actually sending it, you can enable logging."
GitHub has started collecting pseudonymous client-side telemetry from users of its command-line interface (CLI) by default. This change was not widely announced but was included in updated documentation and release notes. The telemetry aims to help GitHub understand feature usage and improve the CLI, including insights for AI agents. While the intention is to enhance user experience, the lack of clarity regarding the specific data collected raises privacy concerns. Users can enable logging to inspect the data that would be sent.
Read at Theregister
Unable to calculate read time
[
|
]