# Google AI Studio GitHub sign-in loop blocks pushes > Source: > Published: 2026-10-01 17:05:55+00:00 # Google AI Studio GitHub sign-in loop blocks pushes The GitHub authorization finishes, but Google AI Studio does not recognize the session it receives afterward, so workspace changes cannot be pushed to `jaikishan123/reflectai-journal` on `main`. Because the GitHub App already has read/write code access and permission for all repositories, changing those permissions is not the useful next move. The apparent failure is the handoff from GitHub back to AI Studio. ## Where does the sign-in flow break? The repository is already visible and connected in AI Studio, which means the project selection itself is intact. Pressing the sync or push control produces the same message: > “Sign in to GitHub to continue” After selecting that option, GitHub authentication completes and the flow returns to AI Studio. Instead of exposing the push controls, AI Studio displays the identical sign-in prompt again. That sequence points away from missing repository access. Authentication finishes at GitHub, but AI Studio apparently fails to retain or recognize the authenticated session. Repeating the same authorization attempt may simply recreate the same broken state. ## How to document the failing attempt A useful bug report should contain one uninterrupted reproduction rather than another general description of the permissions screen. The sequence to capture clarifies the point of failure. First, open the push or sync control for the connected project. Next, select **Sign in to GitHub** and complete authentication on GitHub. After returning to AI Studio, record whether the same sign-in prompt appears. The report must then include the repository and branch, along with the exact error text. Finally, attach the existing screenshots of the App permissions and the AI Studio GitHub panel. The relevant details are: - **Repository:**`jaikishan123/reflectai-journal` - **Branch:**`main` - **GitHub App status:** Installed - **Code access:** Read/write - **Repository access:** All repositories - **Failure point:** Authentication succeeds, then AI Studio asks the user to sign in again - **Persistence:** The loop has continued for several hours across multiple days This makes the report specific to session handling after GitHub authentication. Describing it only as a permissions problem would miss the step that is actually failing. ## What should AI Studio reset? The next support action should be an AI Studio-side reset or repair of the stored GitHub connection and authenticated session, followed by reconnecting the repository through the complete authorization flow. Removing the GitHub App is unlikely to help unless support specifically requests it, because the App is already installed and its required access is present. If resetting the connection produces the same return-to-AI-Studio loop, the focus should remain on the OAuth callback or session handoff. That is the condition under which another repository-access change will not explain the behavior. ## How to keep the push moving Until the built-in connection is repaired, the current changes can be delivered through a local checkout and a regular Git client instead of AI Studio’s sync control. That does not fix the authentication loop, but it separates code delivery from the broken integration. The integration issue itself should still be reported with the exact repository, branch, error message, and evidence that GitHub authentication completes before AI Studio displays the prompt again. [Next Explore GPTs missing from ChatGPT iOS 1.2026.265 sidebar →](https://promptcube3.com/en/threads/9696/) ## All Replies （1） Want a live back-and-forth? [Join the global AI chat room](https://promptcube3.com/en/chat/) — login to talk. I had the same issue with my own project. That handoff to AI Studio is broken for the main branch.