Save an AI Studio project to GitHub as real source, one commit. Bring a GitHub repo — a Lovable export, say — into AI Studio. Every project is checked before anything is written, so it never half-imports.
HighLevel AI Studio
client-site
React + Vite + Tailwind
Checked first
GitHub
you/client-site
One commit — the whole project, real source.
Yours to keep, diff, deploy
Save to GitHub — the project’s real source lands in your repository as one commit.
How it works
Your own HighLevel session, your own GitHub. Nothing to install on either side beyond the extension.
AI Studio → GitHub
The extension lists your AI Studio projects using the HighLevel session you already have open. No second login, no OAuth.
Before anything is written you see the exact file list — including any files a save would remove from the repository.
The whole project — real Vite + React + TypeScript + Tailwind source — arrives in your repository as a single commit. Yours to keep, diff, and deploy anywhere.
GitHub → AI Studio
Connect GitHub and pick from the repositories you allow. Badges show which ones look compatible before you commit to anything — Lovable projects are flagged as such.
Every repository is checked before anything is written: project shape, dependencies, assets, settings. Three verdicts — Supported, Needs review, Unsupported.
Super Vibe creates the project, applies the fixups a Lovable export needs, writes the files, and waits for the build. If anything fails, it rolls back.
Compatibility
AI Studio runs one kind of project — a React app built with Vite — so that’s what Super Vibe moves. Lovable projects fit. Next.js, Nuxt, Remix and Astro don’t, because they need a server AI Studio doesn’t have.
React single-page apps built with Vite
The one kind of project AI Studio runs — TypeScript, Tailwind, shadcn/ui. This is the template AI Studio itself generates.
Lovable projects
Same stack. Super Vibe strips the dev-only lovable-tagger plugin, inlines env values, and rewrites outside dependencies so the build passes.
AI Studio exports
Anything Super Vibe saved to GitHub comes straight back in — the round trip is the point.
Next.js, Nuxt, Remix, Astro
They run code on a server. AI Studio only runs projects in the browser, so there’s nowhere for that code to go.
SvelteKit, Gatsby
Server rendering and a different build system — same wall.
Vue, Svelte, Angular SPAs
Client-side isn’t enough: AI Studio’s build expects React and Vite, and the two aren’t interchangeable.
Plain static HTML sites
Also client-side, also fails — there’s no React app for AI Studio to build.
Create React App
React, but built with a different tool than AI Studio uses, so the build won’t run.
Monorepos
Super Vibe brings in one project at a time, at the top level of a repository — for now. Put the app in its own repo and it comes in.
AI Studio’s build doesn’t run npm install — it installs one fixed set of add-ons and nothing else. Anything your project uses outside that set would normally break the build. Super Vibe rewrites those to load from the internet instead, which works reliably for plain-JavaScript packages. The ones tied closely to React sometimes break when loaded this way — so the gate names them and asks you to confirm before anything is written.
The gate catches all of this before anything is written. Not sure about a project? Connect GitHub and run a check — it takes a few seconds and changes nothing.
The safety gate
Every project is evaluated across four axes — integrity, shape, dependencies, reachability — before a single byte moves.
Everything checks out. Proceed.
It will come in, but some things won’t work the way they do now — each one is named, and you confirm each one before proceeding. Example: “I understand some add-ons might not work and I’ll test it.”
A hard block. The proceed button isn’t greyed out — it’s gone. Nothing gets half-imported, and the screen tells you what would work instead.
The benefit of the doubt is yours. Only signals we’re certain about can block a project outright. When the check isn’t sure, you get a named warning and the choice — because a wrongly-blocked project helps nobody.
Any failure after a project is created rolls it back. If the rollback itself fails, the error names the leftover project so you know exactly what to remove.
Every failure states what happened, whether anything changed, and what to do next. Raw error details go behind “Copy details” — never in your face.
Both directions show a preview before writing — including the exact list of files a save would delete from your repository.
After you migrate
The files come across and the build runs — then the project is yours to tune in AI Studio. Plan for this pass before you publish.
Environment values get inlined during import so the app starts. Add your own addresses and keys in AI Studio — your Supabase URL, your API keys.
Packages outside AI Studio’s fixed set are loaded from the internet at run time. Where a built-in equivalent exists, swap to it for a sturdier build.
Content images are served from the source repository, which has to stay public for them to load. Move them to your own hosting and point the app there.
Every Needs-review item named something specific — a React-coupled add-on, a missing setting. Click through those parts of the app first.
Once it looks right and the flagged items check out, publish from AI Studio the way you would any project.
FAQ
Yes. Enter your email and your license key arrives in your inbox — no card, no trial clock. Paste the key into the extension and you’re set.
Your GitHub token is stored locally in your browser and never sent to us. Your HighLevel session is never stored at all — the extension reads it from AI Studio’s own requests, in memory, only while an operation runs.
React single-page apps built with Vite — the kind AI Studio and Lovable make. Next.js, Nuxt, Remix and Astro don’t fit because they need a server AI Studio doesn’t have, and a Vue app or plain HTML site doesn’t fit because AI Studio’s build expects React and Vite.
Super Vibe checks every project before anything is written and gives one of three verdicts: Supported, Needs review, or Unsupported. Unsupported is a hard block — nothing gets half-imported. The check takes a few seconds and changes nothing.
Treat a migrated project as a starting point, not a finished site. Plan to re-add environment settings, swap CDN-loaded add-ons for AI Studio’s built-in ones, re-host images, and test anything the check flagged — then publish.
No. GitHub asks you to pick which repositories Super Vibe can use, and it can’t see the rest. You can change the selection any time in your GitHub settings, or skip the app entirely and paste a fine-grained token.
Any failure after a project is created rolls it back, so nothing half-finished is left behind. If the rollback itself fails, Super Vibe names the leftover project so you know exactly what to remove. Every failure states what happened, whether anything changed, and what to do next.
Get your free key, install the extension, and move your first project — checked first, previewed before writing, rolled back if anything fails.