GitHub CLI Telemetry Hits HN's Nerve: Opt-Out Is the Real Fight

Original: GitHub CLI now collects pseudoanonymous telemetry View original →

Read in other languages: 한국어日本語
AI Apr 23, 2026 By Insights AI (HN) 1 min read Source

What GitHub changed in the conversation

A Hacker News thread about GitHub CLI telemetry reached 403 points and 295 comments. The official GitHub CLI page says gh sends pseudonymous telemetry so the team can understand feature usage as agentic adoption grows. That framing is exactly why the thread became heated: the CLI is not just a desktop app, it runs in terminals, scripts, CI jobs, servers, and developer workstations with very different expectations.

What the telemetry page says

GitHub says users can inspect would-be payloads with GH_TELEMETRY=log or gh config set telemetry log. The sample payload includes fields such as command, flags, architecture, OS, version, timestamp, whether the command ran in a TTY, invocation ID, device ID, and an agent field. To opt out, users can set GH_TELEMETRY=false, use another falsy value, set DO_NOT_TRACK=true, or run gh config set telemetry disabled. Environment variables take precedence over config.

Why HN reacted sharply

Community discussion did not deny that product telemetry can guide engineering priorities. The pushback was about defaults and context. Several commenters focused on CI/CD and server environments, where unexpected outbound requests can be a networking, compliance, or reproducibility problem even before privacy enters the picture. Others argued that a command-line tool used for source control workflows should bias toward explicit consent because it is often embedded deep in automation.

The broader developer-tool lesson

The practical takeaway is that telemetry design is now part of developer experience. Logging mode, documented opt-out switches, and open-source implementation help, but they do not erase the trust cost of turning collection on by default. The HN thread shows how quickly developers evaluate a tool not only by what it collects, but by how easy it is to prove, disable, and keep disabled across machines and pipelines.

GitHub CLI telemetry documentation | Hacker News discussion

Share: Long

Related Articles

Comments (0)

No comments yet. Be the first to comment!

Leave a Comment

© 2026 Insights. All rights reserved.