AI Studio checkouts just got more flexible. Pick exactly which fields buyers fill in, capture leads before they pay with a two-step checkout, and show a full order summary once payment goes through.

Show, hide or require the phone number and each billing address field (street, city, state, ZIP, country). Name and email are always required.

Capture the lead first and take the payment second, just like the Two Step Order form in Funnels.

new leads fire the trigger, not Order Form Submission. Check that your workflows listen for the right one.

The confirmation screen now shows the order ID, items, taxes and total paid, plus the next charge for subscriptions. Prefer your own page? Send buyers to a custom thank-you page that displays their real order.

Projects already using Payments get all of this on their next prompt. No need to reconnect.

Connect a GitHub account to any AI Studio project and keep your code in sync both ways. AI Studio creates a private repository for the project, pushes every version you save, and pulls back every commit made outside it. Work in any editor or coding agent (Claude Code, Codex, Cursor, Copilot, Gemini CLI) and your changes land back in the project with a fresh preview.

A new AI Studio permission controls Git access and code downloads. It's , so nobody loses access. Agency admins can turn it off per user in . Users without it won't see the Git tab or Download options, but can still build, edit and preview as usual.

You can now add native chat widgets to your AI Studio apps — built and styled by AI Studio to match your site, instead of a generic chat bubble. Just ask AI Studio to "add a live chat", and it builds a real HighLevel chat widget into your app.

Chat widgets in AI Studio run on HighLevel's chat widget, so the conversations, contacts and widget settings are the ones you already use in your HighLevel account. There's nothing extra to set up.

Go to to see the leads your project's chat widgets bring in.

Go to to see your project's widgets. Open one to manage it without leaving AI Studio:

You've built a great app in AI Studio, and now it needs to remember things. It needs to know who's signed in and store the photos people upload. Until now, that meant wiring up a backend yourself.

Open and turn it on from . In about a minute, HighLevel creates a private backend just for that project, with a , , and . There's nothing extra to connect.

🌟

lets you shape sign-in:

⚠️ sign-in supports email and password only. We'll expand to more sign-in methods in future releases.

If the security advisor spots a problem, a card appears on . lists them, and asks AI Studio to repair them.

You can now take payments in apps built with AI Studio. Connect the products in your catalog, ask the agent to “add payments”, and your app gets a secure, hosted checkout.

Payments in AI Studio uses HighLevel’s native payments. Your products, orders, payment providers and subscriptions are the ones already set up in your HighLevel account. There’s nothing extra to set up.

Every published AI Studio site now measures itself. See page views, opt-ins and opt-in rate right inside your project, compare all your sites in Sites Analytics, and follow every lead from first visit to CRM contact. No setup or tracking code needed.

See page views, unique visitors, opt-ins and opt-in rate, with trends and the change from the previous period. Dig into top pages, time on page, traffic sources, devices, browsers, and countries, regions and cities.

Every lead your site's forms collected, with a link to the contact. Filter by form and date, or create a workflow right from there.

See every AI Studio site next to your Funnels and Websites, or pick one project to focus on it.

Contacts created from your site keep their visit history: the pages they viewed, where they came from, and the form they submitted.

Opt-ins from forms you connected before today keep counting. To link a submission to the pages that visitor viewed first, ask AI Studio to reconnect form tracking, then publish again.

AI Studio is now live from Labs for all locations.

A React project that needs server-rendered pages, server functions, or secrets can now be upgraded from Project Settings. AI Studio makes a second project in the same sub-account and runs the upgrade there. The published project stays as it is, domains included. React projects that don't need the new stack stay on React.

🔍 Problem

SSR, server functions, and secrets shipped for new projects. An existing React site that needs those capabilities had no way to get them. Rebuilding inside the live project would have put the published site and its domains at risk.

📦 What shipped

Migrate to SSR is in Project Settings, marked Advanced. It shows on React/Vite projects when you can edit the project. Projects that are already on TanStack do not get the action, and a React project stays on React until someone runs this.

Confirming creates a new project next to the original, in the same account:

You land in that project and the upgrade starts in chat. On the dashboard the card shows Migrating to SSR until the new project is ready as a TanStack app.

Until then, publish, code save, version restore, domain changes, slug changes, and remix are blocked on the copy. Preview, chat, and delete stay open.

⬇️ How to run it

Watch the chat. It reads the app, rewrites it onto TanStack Start, and the card clears once the new project is a normal SSR project.

If the run stops short, the badge stays. In that project’s chat, “continue the migration” picks up the same copy. Starting Migrate again from the original creates another copy.

⚠️ Before you publish the copy

✅ Why this matters

A React project that needs server rendering, a real backend, or secrets can move onto that stack without a rebuild and without a cutover. Projects that don't need it stay on React.

AI Studio just leveled up from “generate a pretty frontend” to build a real full-stack web app. New projects run on TanStack Start: server-rendered pages, real backend (server functions and REST APIs), and a proper secrets vault. Prompt it. Ship it. Watch search engines, social cards, and users all see the same live site.

New AI Studio projects are born full-stack. Not a static SPA pretending to be a website: a React app with a server, routes, APIs, and a published runtime.

Every page is rendered on the server, on every request. Google, LinkedIn, Slack unfurls: they get real HTML (titles, descriptions, headings, the actual copy). No empty #root. No “enable prerender and hope.” Disable JavaScript and the page is still there. That’s not a tweak. That’s how the web is supposed to work.

Need to load data, talk to an API, or keep logic off the client? AI Studio can write server functions that run on the server and stay there. The browser calls them. It never sees the implementation. Your secret sauce stays secret.

Need a public API? You can ship REST endpoints too (/api/...): JSON in, JSON out, GET/POST, webhooks, curl. Server functions power the app from the inside. Server routes are the HTTP API the rest of the world can call.

Drop API keys and tokens into Secrets. They never land in the client bundle, never get pasted into chat, never show up in View Source. Preview and production both get them. Your app can finally call real services without you shipping credentials to every visitor.

SSR + server functions + REST APIs + secrets is the combo: multi-page sites with unique URLs, server-backed data, public APIs, private integrations, and a publish path that’s a live app, not a static zip. Describe the product. AI Studio builds the stack.

They keep running the same way. Nothing changes for existing Vite/React apps. A migration guide to move them onto the new framework is coming soon.

📝

The new AI Studio Form Submitted trigger lets you start workflows when visitors submit connected forms on AI Studio websites. This provides a dedicated way to automate follow-up actions for AI Studio leads, such as sending notifications, emails, SMS messages, tags, or creating opportunities.

AI Studio form submissions will continue to work with the existing External Tracking functionality as well.

⚙️

Add theAI Studio Form Submitted trigger to a workflow.

When a visitor submits a connected AI Studio form, the workflow can start automatically.

Add the actions needed to follow up with the contact. The existingExternal Tracking script and trigger will continue to work alongside this new trigger.

📑 : How existing forms can use this trigger

Forms connected before this trigger was released need to refresh their tracking setup:

😎 Learn More : AI Studio Form Submitted Workflow Trigger