Bolt / StackBlitz Workspace Not syncing to Github & now GitHub Repo Import Failing

[istaydirect]

Summary of Issue: Bolt / StackBlitz Workspace Not Persisting Changes & GitHub Repo Sync Failing

Account: StackBlitz Pro
Repo: istaydirect/staycanadian-app (GitHub organization repo)
Framework: Next.js (App Router), Supabase, Vercel

Issue Description
I connected my project to GitHub last night and it was perfect - then today after several hours of work in Bolt
I experienced a series of issues where Bolt/StackBlitz appeared to be “synced” with GitHub, but no changes were actually written to the project filesystem or pushed to GitHub.

Specifically:

After disconnecting from Github and reconnecting - Bolt pulled in the git repo and I lost all of this mornings work.

GitHub Integration / Sync Issues

I revoked and re-authorized StackBlitz under GitHub → Authorized OAuth Apps.

Despite successful OAuth authorization, Bolt still could not push commits or persist changes.

The repo is under a GitHub organization, which may involve OAuth/SSO restrictions.

The project would silently revert to GitHub state on refresh.

Now my Bolt project appears to be in a tmp/ mode and is not saving files or making any changes to my project.

There was no clear indication in the UI that the workspace was read-only or operating in sandbox mode.

Recovery Attempts & Additional Errors

Attempted to recover work using Bolt backups and fork-from-backup:

Backups did not contain recent changes.

Forked projects also did not contain the claimed file modifications.

Attempted to create a new repo-backed workspace using:

“Open GitHub repository (BETA)”
This resulted in a 500 Internal Server Error.

I then opened this support ticket to report the issue.

Expected Behavior

When Bolt reports files as “CREATED” or “MODIFIED,” those changes should:

appear in the actual project filesystem

persist across refresh

be commit-able to GitHub

The UI should clearly indicate when a project is:

repo-backed vs sandbox/agent-only

read-only or unable to persist changes

GitHub repo import should not fail with a 500 error without user-facing guidance.

Impact

Multiple hours of development time lost due to misleading “success” indicators.

Inability to safely continue development in Bolt despite having a Pro account.

Forced to manually reconstruct changes directly in GitHub to proceed.

Final State When Ticket Was Opened

At the time of opening this ticket, I was attempting to create a new StackBlitz project by importing my GitHub repo. I was hoping to get Bolt back to a happy place - but this process failed with a 500 error.