You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Github login popup keep opening multiple times repeatedly in desktop app, UX is getting very bad due to this #2874
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
I am not sure how to reproduce this, But in my case whenever I open the t3code it start happing directly I am not sure why, I have not done any setting change related to GitHub in t3 code
Expected behavior
Should only ask for login when we try to push code and should only do one time not repeatedly
Actual behavior
Github login popup keep getting open every time I am opening the t3 code
Same. Luckily I do not currently need the git functionality in t3 at the moment so I set this interval to a really long time in the settings for now. The Git credentials doesn't stay open very long either. It pops up for about 3 seconds then closes. Clicking on an option has different outcomes. I have had T3 successfully authenticate every now and then using the browser but it will usually open a coded url at localhost with no way to use that for authentication.
Had the same bug. In my case it was triggered by expired credentials for some repos. Problem is that I had git credential manager window prompting to log in every few seconds but it was timing out and closing the process before I could log in. Information for this could be found in logs but not visible otherwise. I solved it by manually doing git fetch in one of the repos (with same account to same organisation as a few others).
Also some kind of information would be needed instead of suddenly prompting for credentials in the first place.
Desired behavior: something like prompt from T3 "git fetch for project failed because insufficient permissions, click here to log in". Which of course has the issue that people use different authentication methods to different git hostings. But definitely better behavior than current can and should be done.
Thanks for the report and the credential details. We believe this is fixed by PR #3133.
Background Git fetches now disable Git Credential Manager interaction, terminal prompts, and askpass. Passive status polling should no longer open repeated GitHub login windows, while explicit Git actions can still request authentication.
I'm closing this as fixed as part of an automated pass on all open issues. If passive polling still opens a login window in a build that includes PR #3133, please reply with the Git command and environment shown in the trace, and we can reopen it.
Activity
gizix commentedon May 30, 2026
Same. Luckily I do not currently need the git functionality in t3 at the moment so I set this interval to a really long time in the settings for now. The Git credentials doesn't stay open very long either. It pops up for about 3 seconds then closes. Clicking on an option has different outcomes. I have had T3 successfully authenticate every now and then using the browser but it will usually open a coded url at localhost with no way to use that for authentication.
bczaplicki-gd commentedon Jun 19, 2026
Had the same bug. In my case it was triggered by expired credentials for some repos. Problem is that I had git credential manager window prompting to log in every few seconds but it was timing out and closing the process before I could log in. Information for this could be found in logs but not visible otherwise. I solved it by manually doing git fetch in one of the repos (with same account to same organisation as a few others).
Also some kind of information would be needed instead of suddenly prompting for credentials in the first place.
Desired behavior: something like prompt from T3 "git fetch for project failed because insufficient permissions, click here to log in". Which of course has the issue that people use different authentication methods to different git hostings. But definitely better behavior than current can and should be done.
t3dotgg commentedon Aug 27, 2026
Thanks for the report and the credential details. We believe this is fixed by PR #3133.
Background Git fetches now disable Git Credential Manager interaction, terminal prompts, and askpass. Passive status polling should no longer open repeated GitHub login windows, while explicit Git actions can still request authentication.
I'm closing this as fixed as part of an automated pass on all open issues. If passive polling still opens a login window in a build that includes PR #3133, please reply with the Git command and environment shown in the trace, and we can reopen it.