I am experiencing what appears to be a repository-binding issue between Google AI Studio Build Mode and GitHub.
My existing AI Studio application was previously synchronized normally with a private GitHub repository:
Repository: GelisonClementino/TecVitta-Medical
Branch: main
The integration had been working correctly for a long time. I disconnected and reconnected the GitHub integration after experiencing a sync problem. Since then, the original AI Studio workspace no longer recognizes the repository as its connected repository.
In Settings → GitHub, the original workspace now only displays:
“A new GitHub repository will be created”
and the only available action is:
“Create new repository”
There is no option to reconnect or select the existing TecVitta-Medical repository.
What I have already verified
- The GitHub repository still exists and is healthy.
- The repository is private and not archived.
- My GitHub account has administrator and push permissions.
- The Google AI Studio GitHub App is installed on my GitHub account.
- The GitHub App has explicit access to
GelisonClementino/TecVitta-Medical. - GitHub OAuth/authentication appears to be working.
- In Chrome DevTools,
MakerSuiteService/GetGitHubAuthStatusreturns HTTP 200 OK. - After clearing Network and Console and reopening the GitHub panel, no 401 or 403 GitHub authentication errors are produced.
- The AI Studio GitHub import dialog can successfully see
GelisonClementino/TecVitta-Medicaland themainbranch. - I successfully tested Import from GitHub in a temporary new AI Studio app. It imported approximately 691 files successfully.
- However, the import dialog explicitly states that “Imported code won’t stay synced with GitHub.”
- The newly imported test workspace also did not provide a way to establish normal synchronization with the existing repository, so I deleted that temporary app and returned to the original project.
- I also tested the “Create new repository” flow far enough to confirm that AI Studio correctly detects that a repository with the same name already exists.
This demonstrates that AI Studio can:
- authenticate with GitHub;
- access the repository;
- list the existing repository and its
mainbranch; - import its contents;
- detect that its repository name already exists.
However, it cannot associate the existing AI Studio workspace with that existing GitHub repository anymore.
Expected behavior
The existing AI Studio application should remain associated with:
GelisonClementino/TecVitta-Medical → main
or there should be an option in Settings to re-select/reconnect an existing GitHub repository after the GitHub integration is reauthorized.
Actual behavior
The workspace behaves as if it has never been connected to GitHub and only offers to create a new repository.
There is no visible option to rebind the workspace to the repository it was previously using.
Why this is critical
The original AI Studio workspace currently contains validated code changes that have not yet been published to GitHub.
I have preserved:
- the original AI Studio workspace;
- AI Studio Versions/checkpoints;
- a downloaded ZIP backup of the current workspace;
- the last official GitHub
mainstate.
I cannot safely recreate the project from GitHub because that would start from the older main version and would not automatically include the unpublished changes currently present in the original AI Studio workspace.
I also do not want to create a second GitHub repository because that would create a parallel development history.
Request
Could the Google AI Studio team please verify whether the repository-binding metadata for this workspace was lost or invalidated when the GitHub integration was disconnected/reconnected?
Ideally, I need either:
- the original GitHub repository association restored on the backend; or
- a supported UI option to rebind an existing AI Studio workspace to an existing GitHub repository and branch, without creating a new repository or replacing the workspace.
I can provide additional screenshots, Network logs, workspace identifiers, and timestamps privately if required.
I have screenshots demonstrating:
- the GitHub App permissions;
- the existing repository being explicitly authorized;
GetGitHubAuthStatusreturning 200 OK;- the original workspace showing only “Create new repository”;
- the GitHub import dialog correctly detecting the existing repository and
main; - successful import of the repository into a temporary workspace.
Important: I have intentionally not included Authorization headers, cookies, OAuth tokens, or other sensitive session data in this report.