GitHub Desktop Now Supports Multiple Accounts Per Host

GitHub Desktop 3.7.0 ends the one-account-per-host rule: add a personal and a work account at once, and Desktop automatically uses the right one for each repository.

GitHub social preview graphic illustrating platform improvements
Image: GitHub.

GitHub Desktop can now stay signed in to more than one account on the same host at once, GitHub announced on November 19, 2026, ending years of workarounds for developers who juggle a personal GitHub.com account alongside a work or open-source account on the same service. The feature ships in GitHub Desktop 3.7.0: you add every account you use under Settings, and Desktop automatically picks the right credentials for each repository when you clone, publish, fetch or push — no more signing out of one account to sign into another, and no more maintaining two separate installs just to keep identities apart.

Quick facts: GitHub Desktop multi-account support

  • Shipped in GitHub Desktop 3.7.0, announced on the GitHub Changelog on November 19, 2026.
  • You can sign in to multiple accounts on the same host — GitHub.com, GitHub Enterprise Server or GHE.com — with no fixed limit on how many.
  • Each repository is linked to a specific account, so Git operations (clone, publish, push, pull) automatically use the right credentials.
  • Existing single-account users are migrated automatically and see no change in behavior.
  • It was one of the most requested features in the GitHub Desktop community, tracked publicly as issue #3707 since 2018.

What GitHub announced on November 19

GitHub Desktop is GitHub's official point-and-click Git client, aimed at developers who want a visual alternative to the command line for committing, branching and reviewing diffs. Until this release, Desktop enforced a strict one-account-per-host rule: if you had a personal account and a separate work or client account on GitHub.com, switching between them meant signing all the way out and back in every time, which made it painful to work across both in the same session.

GitHub Desktop 3.7.0 removes that restriction. According to the official GitHub Changelog post, you can now add as many accounts as you need for a single host, and Desktop keeps them all signed in simultaneously rather than forcing a single active session.

How multiple accounts work in Desktop

The feature is built around linking repositories to accounts, not just linking accounts to the app in general:

  • Each repository you clone or add can be associated with one specific signed-in account.
  • Clone, publish and other Git operations on that repository automatically use that account's credentials — you don't have to manually switch active accounts first.
  • When you clone or add a repository that more than one of your signed-in accounts can access, Desktop asks you which account to use. If only one account has access, Desktop picks it for you automatically.
  • You can change which account a repository uses at any time, either from that repository's settings or from the right-click context menu in the repository list.

Existing Desktop users don't need to do anything to benefit from the change. GitHub says current repositories are migrated automatically to whichever account was already being used for them, so single-account users will not notice any disruption.

Getting started: adding a second account

On Mac, open Settings from the GitHub Desktop menu and go to the Accounts pane; on Windows, open Options from the File menu and go to the same pane. From there, click "Add GitHub.com account" or "Add GitHub Enterprise account" and follow the sign-in prompts in your browser — you don't need to sign out of your existing account first. The Accounts pane then lists every account you've added, grouped by hostname, with GitHub.com accounts in one group and GitHub Enterprise Server or GHE.com accounts in another.

The feature supports every host type Desktop already connects to: GitHub.com, a self-hosted GitHub Enterprise Server instance, and GHE.com (GitHub's managed Enterprise Cloud offering) — so it works for developers juggling a personal account and a corporate Enterprise account, not just two separate GitHub.com logins.

How Desktop decides which account to use

Under the hood, the feature works by assigning each repository to exactly one account on its host, and Desktop uses that assignment for GitHub API requests and for HTTPS authentication on every push, pull and fetch. According to GitHub's documentation, assignment happens differently depending on how you add a repository:

  • Cloning from the GitHub tab: an Account dropdown appears in the "Clone a Repository" window whenever more than one account is signed in, and it lists only the repositories that account can access.
  • Cloning by URL, or adding a local repository: Desktop checks which of your signed-in accounts can access it. If exactly one can, that account is assigned automatically; if several can, you're asked to choose (public repositories always prompt when multiple accounts exist on the host); if none can, the repository is added unassigned, which will cause a private-repository clone over HTTPS to fail.
  • Publishing a repository: an Account dropdown appears in the "Publish Repository" window, pre-selecting the assigned account if it's currently signed in.

If a repository ever needs credentials and has no assigned account yet — for example, the first time Git needs to push, or when a pull request refreshes — Desktop opens a "Repository account" window to ask. You can also change an existing repository's assigned account at any time, either through Repository → Repository settings → Remote, or by right-clicking the repository in the repository list and choosing Account. One detail worth flagging: the account assignment controls authentication only — it does not change the commit author name or email, which are still controlled separately through your Git configuration.

GitHub Copilot features inside Desktop, such as AI-generated commit messages, follow the same assignment logic: they use the repository's assigned account if that account has Copilot access, and fall back to another signed-in account that does if it doesn't.

What happens when you sign out of an account

Signing out is handled from the same Accounts pane in Settings or Options, with a "Sign Out" (or "Sign out") button next to each account. If any repositories are assigned to the account you're signing out of, Desktop shows a confirmation window with a "Clear repository account assignments" checkbox. Leaving it unchecked — the default — keeps those assignments in place, so they apply again automatically the moment you sign back in. Checking it clears the assignments instead, and Desktop will ask you to choose an account again the next time those repositories need credentials. GitHub's documentation also notes that if an account's authentication token becomes invalid and Desktop removes the account on its own, any repositories assigned to it keep that assignment rather than being reset, so they're ready to reconnect as soon as you sign back in.

There are a few hard edges worth knowing about. A private repository with no account able to access it can't be cloned over HTTPS at all. Public repositories always trigger the account-choice prompt once more than one account is signed in to a host, even though, in principle, no authentication is strictly required to clone a public repo. And background fetches — the periodic checks Desktop runs to keep a repository's status current — never pop open the account picker; if credentials are missing at that point, the fetch simply waits until you take an action that does trigger the prompt.

Why this was one of Desktop's most-requested features

Before GitHub Desktop 3.7.0After GitHub Desktop 3.7.0
One active account per host at a timeMultiple accounts signed in simultaneously per host
Switching accounts required a full sign-out/sign-inDesktop auto-selects the right account per repository
Ambiguous repo access required manual account switching firstDesktop prompts you to pick an account only when more than one applies
Some developers ran two separate Desktop installs to stay separatedA single install handles personal, work and open-source identities

The request for this feature dates back to a GitHub Desktop community issue filed in 2018, and the changelog post itself describes it as "one of the most requested features" from that community. The pain point is a familiar one: developers increasingly maintain a personal GitHub account for side projects and open source, plus a separate account tied to an employer's organization — sometimes on GitHub.com, sometimes on a self-hosted Enterprise Server. Command-line Git has long supported per-repository credentials through tools like SSH config aliases or credential helpers, so this update largely brings Desktop's workflow in line with what power users were already doing manually from the terminal.

Rollout and availability

The update is part of the general GitHub Desktop 3.7.0 release and is available now through the normal Desktop auto-update mechanism, or as a fresh download for new users. GitHub's own documentation on using multiple accounts in GitHub Desktop walks through the account picker and repository-settings flow in more detail, and is the authoritative reference if you run into an edge case, such as a repository that becomes inaccessible after an account is removed.

This release lands a little over a month after GitHub brought Gemini 4 Neon into GitHub Copilot, part of a broader stretch of GitHub platform updates this quarter that also includes GitHub Event Streams moving into public preview.

Bottom line

If you've been maintaining two GitHub Desktop installs, or constantly signing out and back in to switch between a personal and a work account, GitHub Desktop 3.7.0 removes the reason to. Update to the latest version, add your other account under Settings → Accounts, and let Desktop handle the credential switching automatically from there.

Frequently asked questions

What version of GitHub Desktop added multiple account support?

GitHub Desktop 3.7.0, announced via the official GitHub Changelog on November 19, 2026.

How many accounts can I add to GitHub Desktop per host?

GitHub hasn't stated a fixed limit. You can add multiple accounts for a single host — such as GitHub.com — and Desktop keeps all of them signed in at once.

Do I have to manually switch accounts before cloning a repository?

No. Each repository is linked to a specific account, and Desktop automatically uses that account's credentials for Git operations. If several signed-in accounts could access a repository you're adding, Desktop asks you to choose; otherwise it picks automatically.

Will this change anything for people who only use one GitHub account?

No. GitHub says existing repositories are migrated automatically to the account already in use, so single-account users see no change in behavior.

Does this work with GitHub Enterprise Server or GHE.com, or only GitHub.com?

It works across all host types Desktop supports: GitHub.com, self-hosted GitHub Enterprise Server, and GHE.com.

How do I add a second account in GitHub Desktop?

Open Settings (Options on Windows), go to the Accounts tab, and sign in with the additional account. The account picker then appears automatically whenever you clone or add a repository that more than one signed-in account can access.

Sources

Frequently asked questions

What version of GitHub Desktop added multiple account support?

GitHub Desktop 3.7.0, announced via the official GitHub Changelog on November 19, 2026.

How many accounts can I add to GitHub Desktop per host?

GitHub hasn't stated a fixed limit. You can add multiple accounts for a single host — such as GitHub.com — and Desktop keeps all of them signed in at once.

Do I have to manually switch accounts before cloning a repository?

No. Each repository is linked to a specific account, and Desktop automatically uses that account's credentials for Git operations. If several signed-in accounts could access a repository you're adding, Desktop asks you to choose; otherwise it picks automatically.

Will this change anything for people who only use one GitHub account?

No. GitHub says existing repositories are migrated automatically to the account already in use, so single-account users see no change in behavior.

Does this work with GitHub Enterprise Server or GHE.com, or only GitHub.com?

It works across all host types Desktop supports: GitHub.com, self-hosted GitHub Enterprise Server, and GHE.com.

How do I add a second account in GitHub Desktop?

Open Settings (Options on Windows), go to the Accounts tab, and sign in with the additional account. The account picker then appears automatically whenever you clone or add a repository that more than one signed-in account can access.

Sources

More on GitHub Desktop →GitHub DesktopGitHubGitdeveloper toolsversion control
Felix Moreau
Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Software & Guides

See all