Hello Team,
I’m experiencing an issue with GitHub synchronization in Google AI Studio.
For several months, everything worked perfectly. I was able to:
- develop my application in AI Studio,
- synchronize changes to GitHub,
- and deploy them through Netlify.
On July 23, 2026, something unexpectedly changed.
Earlier that same day—and even just a few minutes before the issue occurred—I had successfully synchronized my project with GitHub multiple times without any problem.
Then, without changing my configuration, AI Studio suddenly stopped synchronizing.
Here is the issue:
- My AI Studio project still exists and all my source code is intact.
- When I click GitHub → Sync, AI Studio asks me to reconnect to GitHub.
- After authentication, nothing happens and synchronization fails.
The strange part is that the synchronization dialog now displays a repository owner that does not exist in my GitHub account.
Example:
AI Studio tries to sync to:
wrong-owner/MyProject
while the actual GitHub repository is:
correct-owner/MyProject
The repository itself exists and is accessible.
What I have already tried:
- Revoked the AI Studio GitHub authorization.
- Uninstalled and reinstalled the GitHub App.
- Reinstalled permissions.
- Created a new repository.
- Cleared browser cache.
- Tested different browsers.
- Logged out and back in.
None of these solved the issue.
Another important observation:
The AI Studio project is associated with one Google account, while clicking the AI Studio link stored inside the GitHub repository opens AI Studio under another Google account (which contains no projects).
This makes me think AI Studio may have cached an incorrect project-to-account or project-to-repository mapping after July 23.
My questions are:
- Has anyone experienced AI Studio keeping an outdated GitHub owner or account association?
- Is there a way to reset the GitHub binding of an existing AI Studio project?
- Can the repository owner associated with a project be edited manually?
- Is this a known AI Studio issue?
Since the project itself is fully intact and the problem appeared immediately after several successful synchronizations, I suspect this may be related to an internal GitHub binding or account mapping issue rather than a GitHub permission problem.
Any help would be greatly appreciated.
Thank you.
Oms