App Gets Confused Which GitHub Account It Should Use for Tokens

When being logged in in multiple GitHub Accounts (e.g. one with tokens and another with read/write to our repositories) the app regularly gets confused and switched to the account without tokens. This leads to hiccups and warnings about token limits.

If I log out with the account, which has read/write to our repositories, I can't push anymore.

Every time I have to intentionally select the account with the tokens to continue, which is kind of cumbersome.

Maybe you could add that you can have one account only for repo access and one account for token usage or clearly define in the settings which account can do what.

Start by reproducing the behavior with two GitHub accounts: one with tokens and one with repository access. Inspect how the app selects accounts for token usage and repository operations. Done should mean the roles can be selected or kept distinct so token-limit warnings and repository pushes no longer require repeated manual account switching.

Written by the indexing model from the issue text.