GitHub CLI

“It is the equivalent of GitHub's `gh` binary that wraps their API for an easier DX than cURL”

“My agents can now attach screenshots and screen captures to PRs they create directly, without using workarounds or third party services”

“I have been able to merge and get some things done via command line.”

“just about anything I'd want to do on GitHub, I can do straight from the command line”

“it knows how to track a running CI workflow efficiently without having to try three different methods”

“it already knows how to operate the CLIs well”

“gh and claude code itself have some of the nicest auth flows i've experienced”

“gh gives everything i need out of the box”

“default off with a plain schema would have landed much better than pseudoanonymous by default”

“I do not trust Microsoft with any telemetry, I am not invested in helping them improve their product”

“Why does github need a CLI? Some people just seem to want to make their own lives harder...”

“They could fix issues prior to a release if they wished to without opt-out client side telemetry.”

“already it seems to be a pain to deal with some repos on github without using gh”

“Reading the justification the main thing they seem to want to know is if gh is being driven by a human or an agent”

“that let's Claude Code associate a feature branch to a pull request”

“they just want to increase tracking by knowing what transit as well to Gitlab, Codeberg and such”

“I give it five years before the GH CLI is the only way to interact with GitHub repos.”

“having the cli made automating (or interacting with agents) github-specific tasks possible”

“one of the most powerful tools you can give a coding agent”

“gh is insanely powerful, especially if you let your coding agent use it. It’s one of my top tools.”

“You can use it to auth with GITHUB_TOKEN instead of ssh or http. Which is how my agents get access.”

“restore flags that have been "accidentally" reset and set any new flags that they added for "different" telemetry”

“I'm curious why corporate development teams always feel the need to spy on their users?”

“the GitHub CLI has some very useful commands”

“the GitHub CLI is quite good and helps automate many things in GitHub”

“CLI is great because now I can tell my AI agent to do it.”

“Github MCP is 2–3x more expensive to use than CLI.”

“gh cli and linear mcp is enough for any model to get most of the why context”

“I just do some click here, click there, copy paste and gh cli is ready.”

“Agents know how to use head, tail, jq and so on to only extract the parts it needs.”

“the github cli is very robust and does the job of the MCP with a fraction of the token cost”

“It gives me a permanent record and makes it easy to reference and close the issue once the PR is ready.”

“Using the gh CLI worked far better than the GitHub MCP.”

“is great for interacting with github in the terminal”

“Combined with the GitHub CLI, this gives agents everything they need to achieve the same result.”

“Make sure the gh cli isn’t storing oauth credentials in plaintext as it can silently do.”

“I wouldn't say that's better. Now your .config directory contains a github token that can do more than just repo pull/push”

“the GitHub CLI's Login with HTTPS [4] to do repository push/pull.”

“invoking the CLI tool (which is pre-installed on the runners) with "gh release create ..."”

“stores a highly privileged OAuth token in plain text in the HOME directory”