The News, Explained
GitHub announced on November 19, 2026 that GitHub Desktop supports signing in to multiple accounts on the same host. The announced release is version 3.7.0. GitHub Desktop provides a visual interface for recording code changes and exchanging them with online repositories. People using personal and work accounts on GitHub.com can reduce the need to sign out of one account before using another. Source Source
A host is the server or service address providing a repository. The feature covers GitHub.com, GitHub Enterprise Server and GHE.com, with no fixed limit on accounts added for one host. A repository groups a project’s files and change history. Desktop assigns each repository one account on its host. Source Source
That account authenticates the app’s requests to GitHub and Git operations that upload or download changes over HTTPS, a connection method used to communicate with repositories. When cloning from a URL or adding a local repository, Desktop selects the account automatically if only one signed-in account can access it. If several can, the user chooses. Every account can access a public repository, so multiple signed-in accounts on its host always prompt a choice. Source
For example, suppose someone signed in with personal and work accounts brings a public project onto their computer. The public status prompts a choice between those accounts rather than automatically selecting the work account. If no account can access a repository, it remains unassigned; cloning a private repository over HTTPS fails. Cloning means bringing a remote repository onto the computer. Source
Add accounts under GitHub Desktop → Settings → Accounts on macOS, or File → Options → Accounts on Windows. To change a repository’s account, select Account in the Remote pane of Repository Settings, then save. The choices are accounts signed in on that host. Existing repositories are automatically assigned to the account previously used on their host. Source Source
Authentication and commit authorship are managed separately. A commit records a set of file changes, with the author name and email configured in Git. Changing a repository’s account assignment preserves those author details. Someone matching work-related author information therefore needs to consider repository authentication and Git author settings separately. Source
Copilot features, such as generating commit messages, have another selection rule. They use the repository’s account when it has Copilot access. Otherwise, they use another signed-in account that has access. Understanding the account selected for authentication therefore also involves understanding which account can be used for AI features. Source
OYOPICK’s Take
We see the practical value in making an authentication account explicit for each project inside the app. People moving between personal and work projects can reduce repeated sign-ins while choosing an account per repository. Authentication, the author of a change record and Copilot usage follow different rules, making a clear visual distinction between the three valuable.
The possibility of Copilot using another signed-in account deserves to appear alongside the account choice. If future repository screens clearly show both the authentication account and the account used for AI features, people switching between roles could use the feature with greater confidence.