The sites I build in AI Studio lived only in there. To change a button I went back to the builder's chat, explained again what I wanted and crossed my fingers it wouldn't move something else. Meanwhile the rest of my work lives on GitHub and I edit it with Claude Code or Codex.
On October 15 GoHighLevel connected the two. The request on its ideas board had 147 votes, had been planned since May 4, and the board still marks it as in progress.
Source: "Add GitHub integration", HighLevel ideas board
What it does
Git Sync is a two-way link between an AI Studio project and a GitHub repository: what you change on one side shows up on the other. Inside the project, under More → Git, you connect your GitHub account. AI Studio creates a private repository named after the project and pushes the first version. From there, sync runs both ways:
Every version you save in AI Studio (a prompt, a code edit, a visual edit, a restore) goes up to GitHub. And every new commit on the connected branch comes back on its own. When it comes back, AI Studio builds the preview in the background and lets you hit Update preview when it is ready, without reloading the page on you.
If both sides changed at once, it asks you: Force push (AI Studio wins) or New branch (keep both). And the sync history shows every commit that moved, with its link.
Automatic sync can be turned off in either direction, and the Push now and Pull now buttons stay available.
Sources: official HighLevel changelog; The Stack Insiders, Oct 15, 2026
Limits and rules
| Project type | Works with React (Vite) and TanStack Start projects. |
|---|---|
| Branches | Only the connected branch syncs. It starts on main. |
| Commit author | Commits made by AI Studio show up as "GHL AI Studio", not your GitHub user. |
| Secrets | Blocks the push if it finds AWS, GitHub, Stripe or OpenAI keys, or private keys. |
| Files | Images, fonts and other binary files are kept on every sync. |
The secret scan is good, but it looks at the code, not your database. If your app stores customer data, checking who can read those tables is still your job. I cover it in the AI Studio and Supabase security guide.
The permission I'd switch off first
There is a new permission, Manage Git & download code, and it comes on for every role. Whoever has it can connect GitHub and download the project's full code.
In an agency with client users inside the sub-account, that is the code of your work walking out the door.
You turn it off per user under Settings → Team → Permissions → AI Studio. Someone without it can still build, edit and preview; they just stop seeing the Git tab and the downloads. It is the first thing I am going to check.
Source: official HighLevel changelog (Permissions section)
What I'm going to do
- Connect one site, not all of them, and switch to a test branch before the first change. main stays still.
- Clone the repo and open it in Claude Code.
- Ask for a small change with the prompt below and see if it comes back to AI Studio on its own.
- If the branches split, choose New branch. Force push wipes out what I did outside.
Try it yourself: paste this into Claude Code, inside the repo, on your test branch.
This repo is a GoHighLevel AI Studio project and I am on the prueba-claude branch. Change the text of the main button on the home page to "Book your appointment". Show me the change before saving it. Then commit and push to this same branch. Don't touch main.
Also this week
Since October 14 you can turn features on or off in many sub-accounts at once, from the sub-accounts list. Changes take 2 to 5 minutes and show up in the bulk actions history. If you manage ten sub-accounts, that is ten fewer visits every time something new ships.
The rest of GoHighLevel's changes are in GHL Updates.
Sources: official HighLevel changelog; The Stack Insiders, Oct 14, 2026
