GitHub announced on November 2, 2026 that GitHub Desktop can now sign users in with short-lived access tokens that renew on their own. The change applies to version 3.6.10 and newer, and it is reaching eligible accounts on github.com in stages rather than all at once.
For developers who rely on the desktop client to clone, commit and push, the update shrinks the window in which a stolen credential stays useful. Because the app handles renewal in the background, the extra protection should not add new prompts or steps to a normal working day.
What Changed in GitHub Desktop
Until now, a sign-in from GitHub Desktop produced a credential that stayed valid for a long time. With this release, accounts that qualify receive a token with a limited lifetime instead, and the client swaps it for a fresh one when needed.
The renewal covers both kinds of traffic the app generates:
- Calls to the GitHub API, such as loading pull requests, issues and repository details.
- Git operations, including fetch, pull and push against hosted repositories.
GitHub has also updated its Desktop documentation, which now notes that signing in to GitHub.com from the app produces an expiring credential. The reason given is simple: a compromised token can only be abused for a limited period.
Rollout Details and Who Gets It
The feature is not switched on for everyone yet. GitHub says it is being enabled gradually across github.com, and that this includes organizations on GitHub Enterprise Cloud. Accounts that sign in to GitHub Enterprise Server are outside this rollout.
A few points matter for people who already use the app:
- Upgrading to 3.6.10 does not sign you out. Your current session keeps working.
- Tokens you already have are not converted to the new type automatically.
- The short-lived token is handed out at sign-in, once the rollout covers your installation.
In practice, this means an existing long-lived credential can stay in place until you sign in again. Simply installing the update is not enough to move to the new model.
Why Short-Lived Tokens Matter
Developer machines hold a lot of valuable secrets, and Git credentials are among the most useful to an attacker. A token lifted from a laptop, a backup or a careless log file can grant read and write access to private code for as long as it stays valid.
Limiting the lifetime of that credential does not stop theft, but it cuts down how much damage follows. An expired token is worthless, so a leak discovered late becomes far less serious. This is the same idea behind expiring tokens in CI systems and cloud identity tools.
The move also fits a broader push by GitHub to tighten supply chain security this year. Recent changes have targeted risky workflow triggers, pinned workflow dependencies and alert prioritization, and client authentication is a natural next area.
What It Means for Developers
If you use GitHub Desktop daily, the best step is to upgrade to 3.6.10 or later and then sign out and back in. That should give you a short-lived token as soon as the rollout reaches your account, rather than leaving an older credential in use.
Teams that manage many developer laptops may want to add this to their onboarding notes. A fresh sign-in after the upgrade is a low-cost way to reduce exposure across the whole group, especially for accounts with access to sensitive repositories.
If you see authentication problems after the change, the Desktop docs suggest signing out and signing in again as the first fix. They also explain how to open the app logs from the Help menu, and they cover messages such as bad credentials or an empty token that the app could not find in the system keychain.
Keep in mind that this update only covers GitHub Desktop. Personal access tokens you created by hand, credentials used by scripts, and tokens stored by other Git clients follow their own rules, so review their expiry settings separately.
How to Get Started
Download the newest GitHub Desktop build from the official site, or let the app update itself. Then follow these steps:
- On macOS, open GitHub Desktop, choose Settings and go to the Accounts pane. On Windows, use File, then Options, then Accounts.
- Sign out of your github.com account, then pick Sign Into GitHub.com again.
- Complete the browser-based sign-in, including any two-factor prompt, and return to the app.
Enterprise Server users can continue to sign in as before, since their instances are not part of this change. GitHub asks for feedback through the GitHub Desktop repository or its support channel. If you also manage Actions settings, our recent coverage of the pull_request_target default block and workflow lockfiles reaching general availability is worth a look.
Conclusion
GitHub Desktop 3.6.10 brings expiring, self-renewing tokens to github.com and Enterprise Cloud accounts as part of a staged rollout. The change is quiet for users but meaningful for security. Upgrade, sign in again to pick up the new credential type, and check the other tokens on your machine while you are at it.
Sources
- GitHub Changelog: GitHub Desktop adds short-lived authentication tokens
- GitHub Docs: Authenticating to GitHub in GitHub Desktop
See my articles more often when you search Google.
