GitHub - cli/cli: GitHub’s official command line tool
Important
GitHub CLI's PGP signing key rotation for Linux package repositories is effective September 5, 2026; users experiencing package installation or update problems can find solutions in the
.
gh is GitHub on the command line. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with git and your code.
GitHub CLI is supported for users on GitHub.com, GitHub Enterprise Cloud, and
supported GitHub Enterprise Server versions
, with support for macOS, Windows, and Linux.
Documentation
For
installation options see below
, for usage instructions
.
Agent skills
An
is available for driving gh from coding agents. Install or update it with the built-in gh skill command:
# Install the skill (user scope recommended) gh skill install cli/cli gh --scope user # Update the skill after a `gh` release gh skill update ghContributing
If anything feels off or if you feel that some functionality is missing, please check out the
. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.
If you are a hubber and are interested in shipping new commands for the CLI, check out our
Installation
on
For additional macOS packages and installers, see
Amazon Linux, CentOS, Fedora, openSUSE, RHEL, SUSE
on
For additional Linux & Unix packages and installers, see
on
For additional Windows packages and installers, see
Build from source
See here on how to
.
GitHub Codespaces
To add GitHub CLI to your codespace, add the following to your
:
"features": { "ghcr.io/devcontainers/features/github-cli:1": {} }GitHub Actions
have the GitHub CLI pre-installed, which is updated weekly.
If a specific version is needed, your GitHub Actions workflow will need to install it based on the
,
, or
instructions above.
For information on all pre-installed tools, see
Verification of binaries
Starting with v2.93.0, releases of gh are published as immutable releases. For more information, see
.
Since version 2.50.0, gh has been producing
, enabling a cryptographically verifiable paper-trail back to the origin GitHub repository, git revision, and build instructions used. The build provenance attestations are signed and rely on Public Good
for PKI.
There are two common ways to verify a downloaded release, depending on whether gh is already installed or not. If gh is installed, it's trivial to verify a new release:
Option 1: Using gh if already installed:
$ gh at verify -R cli/cli gh_2.62.0_macOS_arm64.zip Loaded digest sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc for file://gh_2.62.0_macOS_arm64.zip Loaded 1 attestation from GitHub API ✓ Verification succeeded! sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc was attested by: REPO PREDICATE_TYPE WORKFLOW cli/cli https://slsa.dev/provenance/v1 .github/workflows/deployment.yml@refs/heads/trunk
Option 2: Using Sigstore
:
To perform this, download the
for the downloaded release and use cosign to verify the authenticity of the downloaded release:
$ cosign verify-blob-attestation --bundle cli-cli-attestation-3120304.sigstore.json \ --new-bundle-format \ --certificate-oidc-issuer="https://token.actions.githubusercontent.com" \ --certificate-identity="https://github.com/cli/cli/.github/workflows/deployment.yml@refs/heads/trunk" \ gh_2.62.0_macOS_arm64.zip Verified OK
Comparison with hub
For many years,
was the unofficial GitHub CLI tool. gh is a new project that helps us explore what an official GitHub CLI tool can look like with a fundamentally different design. While both tools bring GitHub to the terminal, hub behaves as a proxy to git, and gh is a standalone tool. Check out our
to learn more.