What did HighLevel add to AI Studio on October 14 and 15, 2026?
Three things in two days: a two-way Git sync with GitHub for AI Studio projects, new checkout controls for AI Studio Payments, and native chat widgets built into AI Studio apps. Git sync is the one that changes who can work on an AI Studio app, because it puts the code in a repository a developer can edit.
The HighLevel entries are AI Studio: Git Sync with GitHub, Checkout upgrades for AI Studio Payments and AI Studio Chat Widgets. The pages themselves show no date; HighLevel's changelog feed lists them on October 14 and 15, 2026. They follow the AI Studio Cloud and payments launch we covered in HighLevel AI Studio Cloud and payments.
How does AI Studio's Git sync with GitHub work?
You connect a GitHub account or organization from More, then Git, inside a project. AI Studio creates a private repository named after the project, pushes every saved version to it, and pulls back any commit made outside AI Studio on the connected branch. Both directions can be switched off.
How a change travels between AI Studio and GitHub
The details that matter, all from HighLevel's entry:
- What gets pushed. Every saved version, including AI prompts, code edits, visual edits and restores. Images, fonts and other binary files are kept on each sync.
- What gets pulled. New commits on the connected branch. After a pull, a new preview builds in the background and you choose when to apply it with Update preview, so the page does not reload under you. If the build fails you can retry it or ask AI Studio to try to fix it.
- Branches. The sync starts on main. You can switch branches at any time, and a new branch is created on the next push.
- Frameworks. React (Vite) and TanStack Start projects.
- Secrets. Pushes are scanned for keys such as AWS, GitHub, Stripe and OpenAI keys and private keys, and a push that contains one is blocked.
- Who did it. Commits made by AI Studio appear as "GHL AI Studio", not as your own GitHub identity.
Access needs a new permission, Manage Git & download code. It is on by default for every role. An agency admin can turn it off per user under Settings → Team → Permissions → AI Studio. People without it do not see the Git tab or the download options, but they can still build, edit and preview.
What happens when GitHub and AI Studio both have new commits?
HighLevel calls this a diverged branch and asks you to pick one of two options: force push, where AI Studio's version wins, or new branch, where both versions are kept. Force push can overwrite a developer's work, so a team sharing a project should choose the new-branch option.
| Situation | What HighLevel does | What we would do |
|---|---|---|
| Only AI Studio changed | Pushes each saved version | Nothing; this is the normal case |
| Only GitHub changed | Pulls the commits, builds a preview, waits for Update preview | Review the preview before applying |
| Both changed | Asks: force push or new branch | New branch, then merge in GitHub by hand |
| A secret is in the code | Blocks the push | Move the key to an environment setting and push again |
The last column is our recommendation, not HighLevel's. The reasoning: a person who wrote code in GitHub expects it to stay there, and force push does not give it back. The history in GitHub still holds the old commits, but recovering them is a developer task.
What did the AI Studio checkout upgrade change?
You can now show, hide or require the phone number and each billing address field, capture the buyer as a contact before they pay with a two-step checkout, and show a full order summary after payment. Name and email are always required.
Step one of the two-step checkout saves the buyer as a CRM contact, so a person who does not pay stays a lead. Step two takes the payment. HighLevel says this works like the Two Step Order form in Funnels. One thing to check in an existing account: the new lead fires the Contact Created trigger, not Order Form Submission. A workflow that waits for Order Form Submission will not start for these buyers.
After payment, the confirmation shows the order ID, the items, taxes, the total paid and, for subscriptions, the next charge. You can send buyers to your own thank-you page that shows their order instead. Projects already using Payments get these options on their next prompt, with no reconnecting.
What can an AI Studio chat widget do?
Ask AI Studio for a "live chat" and it builds a HighLevel chat widget into the app's code, styled to match the site. There are two types, Live Chat and Email Chat. Every message lands in HighLevel Conversations like a normal widget message.
Settings sit under More → Chat Widgets: widget name, welcome and acknowledgement lines, contact form fields, a compliance notice with consent options (privacy, marketing, SMS, HIPAA), spam protection and business hours for Live Chat. Spam protection keeps suspicious leads for review and tags them, with optional Do Not Disturb on SMS, email or both. One project can have more than one widget, such as live chat on every page plus an after-hours one.
Limits from HighLevel's entry: Voice, WhatsApp, Facebook Messenger and Instagram widgets are not supported yet, and attachments must fit the widget's file type and size limits. If you want a chat agent that answers questions and books appointments on its own, that is a separate build; see our AI chat agent service.
When is an AI Studio app enough, and when do you need engineers?
AI Studio is enough for a landing page, a simple booking or payment app, or a prototype you will throw away. You need engineers when the app holds customer accounts, connects to systems HighLevel does not cover, has to pass a security review, or must survive years of change.
Git sync makes a middle path realistic: build the first version in AI Studio, connect GitHub, and hand the repository to a developer who hardens it. It does not remove the need for that developer. The list below is how we would size the decision.
| Question | If yes |
|---|---|
| Will customers log in and see their own data? | Plan an engineered build; see customer portal development |
| Does it connect to a billing, booking or ERP system outside HighLevel? | Plan API work; see API integrations |
| Will you sell it as a product to other businesses? | Plan a product build; see SaaS product development |
| Is it a one-off page or a short campaign? | AI Studio alone is likely enough |
| Is it a prototype to show a client or investor? | AI Studio first, then decide on a rebuild |
For the custom builds we have shipped and what they cost, see custom web applications and our custom software page.
What is still unknown?
HighLevel's entries do not say which plans include Git sync, whether there are repository size or rate limits, or when each feature reached all accounts. None of the three pages shows a publish date.
- Plans and pricing. Not stated in any of the three entries. AI Studio Cloud has its own pricing, covered in our earlier note.
- Code ownership. The repository is private and created under the GitHub account you connect, which points to you owning the code. HighLevel's entry does not discuss licensing of AI-generated code, so ask HighLevel if that matters to you.
- Other frameworks. Only React (Vite) and TanStack Start are named.
Frequently asked questions
Can I edit my HighLevel AI Studio app in my own code editor?
Yes, after you connect GitHub. HighLevel says you can work in any editor or coding agent, commit to the connected branch, and AI Studio pulls the commits back and builds a new preview. The sync supports React (Vite) and TanStack Start projects.
Who owns the repository that AI Studio creates?
It is a private repository created in the GitHub account or organization you connect, named after the project. Commits show as "GHL AI Studio". HighLevel's entry does not say anything about licensing, so confirm that point with HighLevel if you need it in writing.
Can I stop my team from downloading or syncing AI Studio code?
Yes. The Manage Git & download code permission is on by default for every role, and an agency admin can switch it off per user under Settings, Team, Permissions, AI Studio. People without it can still build, edit and preview.
Why did my workflow not start for AI Studio checkout buyers?
With the two-step checkout, the buyer is saved as a contact in step one and the Contact Created trigger fires, not Order Form Submission. Change the workflow trigger, or add a second workflow that starts on the payment event you care about.
Sources
- HighLevel changelog, AI Studio: Git Sync with GitHub, feed date October 15, 2026, read October 21, 2026.
- HighLevel changelog, Checkout upgrades for AI Studio Payments, feed date October 15, 2026, read October 21, 2026.
- HighLevel changelog, AI Studio Chat Widgets, feed date October 14, 2026, read October 21, 2026.
