CLI tool
cli/cli avatar
cli/cli

GitHub CLI: The Official Terminal Client for GitHub Workflows

GitHub describes it as GitHub’s official command line tool. The repository metadata lists Go as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

47,029 stars9,328 forksGoMIT

At a glance

What is it?
GitHub CLI (gh) brings pull requests, issues, and other GitHub concepts to the terminal, standing separate from git rather than wrapping it. This review covers its mechanism, installation, verification, and where it fits or fails for engineers.
Who is it for?
Adopt gh if you work daily with GitHub pull requests, issues, or releases and want to stay in the terminal without switching to the web UI. It is also a strong fit for CI environments where GitHub-hosted runners already include it.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • cli/cli47,029 ★ · +1,181
Star history
Repository2026-08-132026-11-15
cli/cli45.8k47k

1,181 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What gh Solves and Who It Serves

The problem gh addresses is the context switch between a terminal and the GitHub web interface. Developers working on pull requests, issues, or releases often need to check status, comment, or merge without leaving their editor or terminal. gh brings these GitHub concepts directly to the command line, sitting next to git rather than replacing it. The tool targets individual developers on macOS, Windows, and Linux, plus teams using GitHub Enterprise Cloud or supported GitHub Enterprise Server versions. It also serves CI pipelines: GitHub-hosted runners come with gh pre-installed, updated weekly, which removes a setup step for automation. The README positions gh as the official tool, distinct from the older unofficial hub, and that official status matters for teams that want a supported path.

Standalone Design vs. hub's Proxy Approach

The most important architectural choice is that gh is a standalone tool, not a git proxy. The README explicitly contrasts this with hub, which behaves as a proxy to git. That means gh does not intercept or wrap git commands; it has its own command surface for GitHub-specific operations. This design keeps git itself untouched, avoiding the surprises that can come from a tool that silently changes git's behavior. The trade-off is that you must learn gh's commands separately, whereas hub aimed to extend git's existing commands. The README points to a detailed comparison document, but the core difference is clear: gh is a separate binary with its own workflows, which can feel more explicit but also adds a second tool to learn.

The Mechanic: How gh Talks to GitHub

The repository is written in Go, which aligns with a single static binary distribution. The README does not detail the internal API layer, but the tool's behavior implies it communicates with GitHub's REST and GraphQL APIs to fetch and mutate pull requests, issues, and other resources. The agent skill feature, introduced via the gh skill command, shows a mechanism for coding agents to drive gh. That skill is installed with gh skill install cli/cli gh --scope user and updated with gh skill update gh. This suggests gh now exposes a structured interface for automation beyond human typing. The verification workflow is another visible mechanism: gh at verify checks a downloaded release's provenance against the GitHub API, using Sigstore for PKI. That command loads a digest and attestation, then confirms the workflow that built the binary. This is a concrete data flow: fetch attestation, verify signature, confirm the source repository and build workflow.

Getting It Running: Installation Paths

Installation is straightforward across platforms, with official package managers listed. On macOS, Homebrew and precompiled binaries from the releases page are the primary routes. On Linux, Debian, Raspberry Pi and Ubuntu have their own packages, while Amazon Linux, CentOS, Fedora, openSUSE, RHEL, and SUSE use RPM packages. Windows users can use WinGet or grab a precompiled binary. There is also a devcontainer feature for GitHub Codespaces, added via the JSON snippet "ghcr.io/devcontainers/features/github-cli:1" in a devcontainer file. For GitHub Actions, the tool is pre-installed on hosted runners, but if you need a specific version, the workflow must install it manually using the same platform-specific instructions. Building from source is possible, with a dedicated document, but the README does not give the exact build commands. Recent releases are v2.103.3 on 2026-10-26, v2.103.2 on 2026-10-23 and v2.103.1 on 2026-10-23.

Binary Verification: A Real Security Feature

Starting with v2.93.0, releases are immutable, meaning the release assets cannot be changed after publication. Since v2.50.0, gh has produced Build Provenance Attestation, which gives a cryptographically verifiable chain back to the source repository, git revision, and build instructions. The README gives two verification options. If gh is already installed, you run gh at verify -R cli/cli gh_2.62.0_macOS_arm64.zip, and it loads the digest and attestation from the GitHub API, then prints a verification success message. If gh is not installed, you can use cosign with a bundle file, specifying the OIDC issuer and certificate identity. This is a meaningful feature for security-conscious teams, as it allows you to confirm that a downloaded binary was built from the official cli/cli repository and not tampered with. The example output shows a specific SHA256 digest and the workflow that produced it, which is a concrete audit trail.

Agent Skills: A New Interface for Automation

The README introduces an agent skill, which is a notable addition. An agent skill is a packaged set of instructions that a coding agent can use to drive a tool. The gh skill is installed via gh skill install cli/cli gh --scope user, and updated with gh skill update gh after each release. This suggests that gh is not only for interactive terminal use but also for AI-driven coding agents. The README links agentskills.io for the agent skill concept and does not detail what the skill contains; it is installed from cli/cli with gh skill install. This is a thin area of documentation, so it is hard to assess how mature the skill is. The user scope recommendation implies it is designed for a single user's environment, not a shared CI setup. For engineers evaluating gh, this feature could be relevant if they use coding agents, but the lack of detail means you should check the skill's content before relying on it. It is an experimental-looking extension rather than a core feature.

Limitations and When It Is the Wrong Tool

The most obvious limitation is that gh is not a git proxy, so it will not transparently extend git commands. If you are used to hub's approach, gh requires you to learn its own command syntax. The README does not list specific unsupported features, but the scope is GitHub-specific: it brings pull requests, issues, and other GitHub concepts, not generic git functionality. For users on GitHub Enterprise Server versions that are no longer supported, gh is not supported, which is a hard boundary. Another limitation is that the README does not document the full command set; it points to the manual at cli.github.com/manual. That means the README alone is insufficient for learning the tool, and you must consult external documentation. The agent skill is also underdocumented in the README, which could be a gap for teams wanting to rely on it. For non-GitHub workflows, such as GitLab or Bitbucket, gh is simply the wrong tool, as it has no support for those platforms.

Maintenance, Upgrade Cost, and License

The project is actively maintained: the last push was on 2026-11-02, and recent releases include v2.103.3 on 2026-10-26 and v2.103.2 and v2.103.1 on 2026-10-23. Upgrades are straightforward: on macOS, brew upgrade gh; on Linux, the package manager handles updates; on Windows, WinGet can update. For CI, the hosted runners update gh weekly, which reduces maintenance but also means you cannot pin a version without manually installing it. The README notes that if a specific version is needed, the workflow must install it, which adds a maintenance step. The license is MIT, which is permissive and allows commercial use, modification, and redistribution with attribution. There is no mention of a contributor license agreement or additional terms. The project is not archived and has a trunk default branch, which suggests active development. The verification feature adds a small upgrade cost: you must decide whether to verify each binary, but the gh at verify command makes it trivial if gh is already installed.

Editorial conclusion

Adopt gh if you work daily with GitHub pull requests, issues, or releases and want to stay in the terminal without switching to the web UI. It is also a strong fit for CI environments where GitHub-hosted runners already include it. Do not adopt it if you need a git proxy like hub, or if you work primarily with GitHub Enterprise Server versions that are no longer supported. Before adopting, verify your platform's installation path (Homebrew, WinGet, or package manager) and, for security-sensitive environments, confirm the binary's provenance using gh at verify or cosign, as described in the README. The tool's value is concrete: it is the official, MIT-licensed CLI that continues to ship frequent releases, with the latest v2.103.3 on 2026-10-26.

Frequently asked questions

What is the CLI in GitHub CLI?

gh is GitHub's official command line tool. It brings pull requests, issues and other GitHub concepts to the terminal next to where you already work with git, and it is a standalone tool rather than a proxy to git like the older hub project.

How do I use the GitHub CLI?

Usage instructions are in the manual at cli.github.com/manual. For a coding agent, the tool ships a skill command that installs and updates the agent skill: gh skill install cli/cli gh --scope user, then gh skill update gh after a release.

How do I install the GitHub CLI on macOS, Linux and Windows?

macOS offers Homebrew or a precompiled binary, Linux and Unix offer Debian, Raspberry Pi and Ubuntu packages or rpm packages for Amazon Linux, CentOS, Fedora, openSUSE, RHEL and SUSE, and Windows offers WinGet or a precompiled binary. Building from source is covered in docs/install_source.md.

How do I verify a downloaded GitHub CLI release?

If gh is already installed, run gh at verify against the downloaded archive. Since v2.93.0 releases are immutable, and since version 2.50.0 they carry build provenance attestations signed with Sigstore, which can also be checked with cosign verify-blob-attestation and the attestation bundle.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Community

Where developers are discussing it

Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 1 in the last 30 days; newest first.

Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/cli-cli.svg)](https://hysenlabs.com/projects/cli-cli)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/cli-cli.svg)](https://hysenlabs.com/projects/cli-cli)

Was this useful?