alt Hacker NewsTried the GitHub app, made sure everything was properly connected, and asked a question about one of my repositories. It repeatedly claimed (5 times) that it wasn't connected and couldn't do anything, telling me to check the checkboxes that were already checked. Only after I showed it a screenshot of the settings did it suddenly comply and answer the question. I guess it still needs more polish.
Replies
hi kgeist - i work on the team that manages the github app. are you able to share a conversation where the github connector did not work? feel to message me at https://x.com/kevins8 (dm's open)
I never had a pleasant GitHub connection experience in any platform.
Permission to allow the specific repo only access never works, so I'll have to allow access to all repo and then manually change it back to specific repo inside GitHub after connecting.
There have been instances of endless loop after Oauth sign-in, more recent experience was in Claude Code Web[1].
Poor GitHub folks, only if someone can donate time/money to this struggling small company these critical issues could be addressed /S
Screenshots use a different router, so if you get stuck in one modality then pasting a screenshot can sometimes divert whatever "expert" you were stuck on that was refusing to comply. I don't work at OpenAI but I know enough about how these systems are architected to know that once you are stuck in a refusal basin the only way is to start a new session or figure out how to get routed to another node in their MoE configuration. Ironically, they promised their fancy MoE routing would fix issues like these but it seems like they are getting worse.