
GitHub CLI
CLIGitHub 官方命令行:在终端里管理 PR、Issue、Release 与 Actions 工作流,多数命令支持 --json 输出便于 agent 解析,并提供官方 agent skill。需先 gh auth login 登录。
GitHub CLI
GitHub CLI, or the gh CLI, 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.
[!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 public announcement.

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 see the manual.
Agent skills
An agent skill 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 gh
Contributing
If anything feels off or if you feel that some functionality is missing, please check out the contributing page. 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 doc on internal contributions
Installation
macOS
For additional macOS packages and installers, see community-supported docs
Linux & Unix
- Debian, Raspberry Pi, Ubuntu
- Amazon Linux, CentOS, Fedora, openSUSE, RHEL, SUSE
- Precompiled binaries on releases page
For additional Linux & Unix packages and installers, see community-supported docs
Windows
For additional Windows packages and installers, see community-supported docs
Build from source
See here on how to build GitHub CLI from source.
GitHub Codespaces
To add GitHub CLI to your codespace, add the following to your devcontainer file:
"features": {
"ghcr.io/devcontainers/features/github-cli:1": {}
}
GitHub Actions
GitHub-hosted runners 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 macOS, Linux & Unix, or Windows instructions above.
For information on all pre-installed tools, see actions/runner-images
Verification of binaries
Starting with v2.93.0, releases of gh are published as immutable releases. For more information, see Immutable releases.
Since version 2.50.0, gh has been producing Build Provenance Attestation, 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 Sigstore 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
ghif 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
cosign:To perform this, download the attestation 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, hub 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 more detailed explanation to learn more.
相關資源

GitHub MCP Server
MCPGitHub 官方 MCP 服务器:让 agent 读写仓库与代码,管理 Issue 和 PR,查看 Actions 工作流与代码扫描告警。可接托管远程服务或用 Docker 本地运行,需个人访问令牌或 OAuth 授权。
github/github-mcp-server33.7k
GitHub Copilot CLI
CLIGitHub 官方终端编码 Agent,与 Copilot 编码代理共用同一套 harness,默认内置 GitHub MCP,可用自然语言处理仓库、Issue 与 PR,每步操作执行前需确认。需要 Copilot 订阅。
github/copilot-cli11.3k
GitHub
Plugin接入 GitHub 官方远程 MCP 服务器,在 Claude Code 里管理 Issue 与 PR、评审代码、搜索仓库并调用 GitHub API;需要配置 GITHUB_PERSONAL_ACCESS_TOKEN。
anthropics/claude-plugins-official40.3k
Claude Code
CLIAnthropic 官方终端编码 Agent:读懂代码库、修改代码、执行命令、处理 git 流程,支持插件、MCP 与无头模式(claude -p)。需要登录 Claude 账号或配置 API Key。
anthropics/claude-code151k
Cline CLI
CLICline 官方命令行版,与 VS Code 插件共用 Agent 核心,支持 plan/act 模式、MCP、检查点与子代理;--yolo、--json 可无人值守跑在 CI 与脚本里。可登录 Cline、ChatGPT 订阅或自带 API Key。
cline/cline70.4k
GitLab
Plugin接入 GitLab 官方远程 MCP 服务(Beta),让 Claude 操作仓库、合并请求、CI/CD 流水线、议题与 Wiki;连接 GitLab.com,需在顶级群组开启 MCP 访问并经浏览器 OAuth 授权。收录于 Anthropic 官方插件市场。
anthropics/claude-plugins-official40.4k