Text of code.claude.com › docs › en › github-enterprise-server as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Claude Code with GitHub Enterprise Server - Claude Code Docs

Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. GitHub Enterprise Server support is available for Team and Enterprise plans. GitHub Enterprise Server (GHES) support lets your organization use Claude Code with repositories hosted on your self-managed GitHub instance instead of github.com.

Once an Owner connects your GHES instance, developers can run cloud sessions and get automated code reviews without any per-repository configuration. Plugin marketplaces hosted on your instance are also supported; credential requirements vary by surface, as described in Plugin marketplaces on GHES . For repositories on github.com, see Use Claude Code in the cloud and Code Review . To run Claude in your own CI infrastructure, see GitHub Actions .

What works with GitHub Enterprise Server The table below shows which Claude Code features support GHES and any differences from github.com behavior. Feature GHES support Notes Cloud sessions ✅ Supported An Owner connects the GHES instance once; developers use claude --cloud or claude.ai/code Code Review ✅ Supported Same automated PR reviews as github.com Claude Security ✅ Supported Available in public beta for Enterprise plans at claude.ai/security Teleport sessions ✅ Supported Move sessions between cloud and terminal with --teleport Plugin marketplaces ✅ Supported Credential requirements differ by surface.

See Plugin marketplaces on GHES Contribution metrics ❌ Not supported Requires repositories hosted on github.com. The analytics dashboard still shows usage metrics for work in GHES repositories GitHub Actions ✅ Supported Requires manual workflow setup; /install-github-app is github.com only GitHub MCP server ❌ Not supported The GitHub MCP server does not work with GHES instances Admin setup An Owner connects your GHES instance to Claude Code once.

You need the Owner or Primary Owner role in your Claude organization and permission to create GitHub Apps on your GHES instance. The guided setup generates a GitHub App manifest and redirects you to your GHES instance to create the app in one click. If your environment blocks the redirect flow, an alternative manual setup is available. 1 Open Git providers settings Go to Organization settings > Git providers and find the GitHub Enterprise section.

2 Start the guided setup Click Connect , or Add instance if an instance is already connected, then select Set up automatically . Enter a display name of up to 20 characters for the connection and your GHES hostname, for example github.example.com . If your GHES instance uses a self-signed or private certificate authority, paste the CA certificate in the optional field. 3 Create the GitHub App Click Continue to GitHub Enterprise .

Your browser redirects to your GHES instance with a pre-filled app manifest. Review the configuration and click Create GitHub App . GHES redirects you back to Claude with the app credentials stored automatically. 4 Install the app on your repositories From the GitHub App page on your GHES instance, install the app on the repositories or organizations you want Claude to access. You can start with a subset and add more later.

5 Enable Code Review Go to claude.ai/admin-settings/claude-code and enable Code Review for your GHES repositories using the same configuration as github.com. GitHub App permissions The manifest configures the GitHub App with the permissions and webhook events below, which together cover cloud sessions, Code Review, Claude Security, and plugin marketplaces: Permission Access Used for Contents Read and write Cloning repositories and pushing branches Pull requests Read and write Creating PRs and posting review comments Issues Read and write Responding to issue mentions Checks Read and write Posting Code Review check runs Actions Read Reading CI status for auto-fix Commit statuses Read Reading CI status from providers that report commit statuses instead of check runs Repository hooks Read and write Creating a webhook on a plugin marketplace repository when Sync automatically is turned on for a marketplace in Organization settings > Plugins & skills Metadata Read Required by GitHub for all apps Organization members Read Matching the Claude GitHub App on github.com, which uses it to check a connecting user’s organization role when linking an installation The app subscribes to pull_request , issue_comment , pull_request_review_comment , pull_request_review , check_run , and status events.

GitHub applies a manifest only when the app is created, so an app created from an earlier version of the manifest keeps the permissions and events it was created with. If your app is missing any of the permissions or events above, add them in the app’s settings on your GHES instance. GitHub then asks an owner of each installation to approve the new permissions, and the installation keeps its old permissions until they do.

Manual setup If the guided redirect flow is blocked by your network configuration, click Connect or Add instance , then select Add manually instead of Set up automatically . Create a GitHub App on your GHES instance with the permissions and events above , then enter the connection details in the form: a display name, your GHES hostname and optional port, and the app’s ID, client ID, client secret, webhook secret, and private key.

The form also accepts an optional custom CA certificate and read replica hostnames. Claude generates the app’s webhook URL when you save the connection. After you click Add configuration , open the connection’s More options menu, select Copy webhook URL , and paste the URL into the app’s webhook settings on your GHES instance. Use the same webhook secret you entered in the form. Network requirements For Anthropic-hosted sessions, your GHES instance must be reachable from Anthropic infrastructure so Claude can clone repositories and post review comments.

If your GHES instance is behind a firewall, allowlist Anthropic’s outbound IP addresses . Sessions in a self-hosted environment clone from inside your network instead, unless the runner opts into the Anthropic git proxy , which fetches from Anthropic’s side and needs the same reachability. Hosted pre-session flows, such as the repository picker, run on Anthropic’s side before a session starts. They need your GHES instance to be reachable from Anthropic infrastructure even when the session runs in a self-hosted environment.

The SCM connector isn’t available, so those flows can’t reach a GHES host that’s only routable internally. Developer workflow Claude Code detects your GHES hostname automatically from the git remote in your working directory. Clone a repository from your GHES instance as you normally would, replacing github.example.com and the repository path with your GHES hostname and repository: git clone git@github.example.com:platform/api-service.git cd api-service Then start a cloud session.

Claude detects the GHES host from your git remote and routes the session through your organization’s configured instance: claude --cloud "Add retry logic to the payment webhook handler" The session clones your repository from GHES and pushes changes back to a branch. Monitor progress at claude.ai/code . See Use Claude Code in the cloud for the full cloud session workflow including diff review, auto-fix, and cloud scheduled tasks.

Teleport sessions to your terminal Pull a cloud session into your local terminal with claude --teleport . Teleport verifies you’re in a checkout of the same GHES repository before fetching the branch and loading the session history. See teleport requirements for details. Plugin marketplaces on GHES Host plugin marketplaces on your GHES instance to distribute internal tooling across your organization. The marketplace structure is identical to github.com-hosted marketpla

The rest of this page is on the live site.