Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams

The Copilot app now takes GHES accounts

Written November 14, 2026

The Copilot app now works with GitHub Enterprise Server repositories, issues and pull requests. Version 1.2.0 or later, one sign-in rule, one missing piece.

What changed

GitHub Enterprise Server support in the GitHub Copilot app is generally available as of November 13. The feature was previously an opt-in preview. A team running its own GitHub Enterprise Server instance can now bring that work into the Copilot app: add a GHES account and work with remote repositories, issues, and pull requests from the server, in the same app already used for GitHub.com work. For enterprise teams, this removes the split where the app covered hosted repositories but stopped at the boundary of their own instance.

The sign-in rule comes first

The setup order matters, and GitHub states it as a requirement rather than a suggestion. You need to sign in with a GitHub.com or GHE.com account first. Only then do you add the server account: go to Settings, then Accounts, then Add account, and choose GitHub Enterprise Server. A user who opens the app expecting to start from their GHES account will not get there — the hosted account sign-in is the first step, and the GHES account is added on top of it. Admins writing setup instructions for their teams should put that order at the top, because it is the step most likely to be done backwards.

Version and scope

GHES support is available in GitHub Copilot app version 1.2.0 and later, so an older install needs an update before the account option is usable. What the GHES account brings into the app is the working material of a server instance: remote repositories, issues, and pull requests. That is the material a team member needs to pick up server-side work inside the app rather than switching back to the browser for every issue or review. GitHub's Copilot GHES documentation carries the sign-in detail for teams that need more than the announcement covers.

From opt-in preview to a standard feature

The move from opt-in preview to general availability changes how a team rolls this out. During the preview, using GHES in the app meant opting in; now the support is part of the standard product, available to any team on app version 1.2.0 or later with a GHES account to add. That makes this a fleet update question rather than a pilot question: the work is getting the app updated on the machines that need it and getting each user's accounts added in the right order. Teams that tried the preview can treat the setup as settled and extend it to the rest of the group without a separate enrolment step.

The missing piece

One feature does not come across, and GitHub states the limit in the same breath as the launch: cloud sessions are not available for GHES. Work tied to a GHES account stays within what the app can do with the server's repositories, issues, and pull requests directly. A team whose workflow leans on cloud sessions for hosted repositories should not assume the same pattern carries to its server work. Plan GHES use around the local side of the app, and treat cloud sessions as a GitHub.com-side capability for now.

What to do

Update the Copilot app to 1.2.0 or later on each machine that needs GHES access. Sign in with the GitHub.com or GHE.com account first, then add the GitHub Enterprise Server account under Settings, Accounts, Add account. Open a repository, an issue, and a pull request from the server to confirm the account is working end to end, and set expectations with the team on cloud sessions before anyone builds them into a GHES workflow: for server accounts, that piece is not there.

Related playbooks

Sources

Back to: Teams playbooks hub · Also: GitHub Enterprise now includes Copilot at $0 a seat · Copilot retires six more models on December 14