Repository navigation
Support multiple fine-grained tokens for gh auth switch #12888
Description
Activity
Thank you for your issue! We have categorized it as an enhancement (feature or improvement) request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.
Unless you see the help wanted
Contributions welcome label, we are not currently looking for external contributions for this feature.If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.
I was able to work around this by using https://direnv.net/. However, it works best when you have project directories or git checkouts for the
.envrcor.envfile to exist in, which wouldn't help cases where a user is callingghdirectly with nothing locally other than theghargs to identify what token to use.Having issues on
gh auth switchdoesn't pick up second account, it was stuck in the first authentificated account, any suggestions to fix that on mac- added a commit that references this issue
on Jul 23, 2026 I know it will not be merged but in case it helps i have implemented this branch: rastaman#1 (with Opus and Cursor) to implement what is described here. I have done it, and added a possibility to sync a fork with upstream from 2 auths, because my day-to-day employer disabled PAT and only allowed FAT and it brokes some of my workflows with gh. I really don't say it perfect but it does the job for me.
HtH, my 2 cents
Reacted by Andrew Berry
Describe the feature or problem you’d like to solve
Fine-grained tokens are a great way to limit access to automated tools and AIs by repository and permission. However, each fine-grained token can only be associated with a single GitHub organization. That means that if you want to use a single GitHub CLI instance to interact with multiple organizations, you can't. Since the CLI is limited to a single token, it also means that concurrent processes can't be using the CLI to communicate to different organizations in parallel.
Proposed solution
Add
--add-tokenas an option when using--with-token. When specified, this will add the new token instead of replacing it. As well, add the organization name or ID to thehosts.yamlfile for the token so the gh CLI tool can automatically use the right token.