GitHub CLI now collects pseudoanonymous telemetry
cli.github.com
GitHub CLI now collects pseudoanonymous telemetry
1–10 of 368 posts
Re: GitHub CLI now collects pseudoanonymous telemetry
#2> Removes the env var that gates telemetry, so it will be on by default.
Re: GitHub CLI now collects pseudoanonymous telemetry
#3export GH_TELEMETRY=false
export DO_NOT_TRACK=true
gh config set telemetry disabled (starting from version 2.91.0, which this announcement refers to)
Re: GitHub CLI now collects pseudoanonymous telemetry
#4tl;dr for opt-out as per https://cli.github.com/telemetry#how-to-opt-out (any of these work individually): export GH_TELEMETRY=false export DO_NOT_TRACK=true gh config set telemetry disabled (starting from version 2.91.0, which this announcement refers to)
gh version 2.90.0 (2026-04-16) https://github.com/cli/cli/releases/tag/v2.90.0
$ gh config set telemetry disabled
! warning: 'telemetry' is not a known configuration key
Re: GitHub CLI now collects pseudoanonymous telemetry
#5Re: GitHub CLI now collects pseudoanonymous telemetry
#6tl;dr for opt-out as per https://cli.github.com/telemetry#how-to-opt-out (any of these work individually): export GH_TELEMETRY=false export DO_NOT_TRACK=true gh config set telemetry disabled (starting from version 2.91.0, which this announcement refers to)
$ gh --version gh version 2.90.0 (2026-04-16) https://github.com/cli/cli/releases/tag/v2.90.0 $ gh config set telemetry disabled ! warning: 'telemetry' is not a known configuration key
Also note that even though you get a warning about an unknown config key, the value is actually set so you're future-proof. Check `grep telemetry ~/.config/gh/config.yml`