[neobrain]

tl;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)

[fenaer]

$ 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

[rethab]

v2.91.0 is the one that's going to introduce it: https://github.com/cli/cli/releases/tag/v2.91.0

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`

[NeckBeardPrince]

> gh config set telemetry false > ! warning: 'telemetry' is not a known configuration key

What's strange is if you check your `~/.config/gh/config.yml` it will put `telemetry: disabled` in there. But it will put anything in that `config.yml` lol.

> gh config set this-is-some-random-bullshit aww-shucks > ! warning: 'this-is-some-random-bullshit' is not a known configuration key

But in my config.yml is

this-is-some-random-bullshit: aww-shucks

[nottorp]

... don't forget to recheck this info every update, restore flags that have been "accidentally" reset and set any new flags that they added for "different" telemetry