AI
/ ai-studio

AI Studio

A conversational workspace that builds websites, pages, and apps from a prompt.

Overview

A dedicated conversational project workspace for generating websites, landing pages, forms, booking experiences, and small interactive web projects from a prompt, template, or reference. It produces layouts, copy, images, and code-level edits, then publishes to a preview or custom domain. New projects run full-stack on TanStack Start with server-side rendering, server functions, REST APIs, and Secrets (Sep 8, 2026), and can add a Cloud backend — database, auth, storage (Oct 9, 2026), native payments (Oct 8, 2026), and built-in Analytics & Submissions (Oct 8, 2026). Existing projects can migrate to SSR as a separate copy (Sep 22, 2026), and the builder can now run shell commands to inspect, test, and verify the live app before it finishes (Sep 3, 2026). Distinct from the agent builders: AI Studio ships web experiences, not conversational agents.

What it's for

Go from a description to a published web experience — with backend, payments, and measurement — without hand-building every page in the funnel/site builder.

Capabilities

Prompt-to-site

Describe the site/page in plain English and get a generated layout, copy, and structure.

Conversational editing

Refine by chatting — request section, styling, copy, and code-level changes in dialogue.

Templates & references

Start from a template or point at a reference site to match its structure and tone.

Landing pages & forms

Generate lead-capture pages, forms, and booking experiences wired to the CRM.

Copy & image generation

AI writes on-brand copy and can source/generate imagery for sections.

Code-level edits

Make targeted code changes (HTML/CSS/JS) through the same conversation.

Publish

Publish to a preview URL or a custom domain from inside the workspace.

Full-stack apps

New projects run on TanStack Start, not a static single-page app: a React app with a server, routes, APIs, and a published runtime. Server-side rendering renders every page on the server on every request, so Google, LinkedIn, and Slack unfurls get real HTML — titles, descriptions, headings, and the actual copy, with no empty #root — and the page is still there with JavaScript disabled. Server functions run backend logic on the server only; the browser calls them and never sees the implementation, so scoring, API calls, and private logic stay secret. REST API routes (/api/...) are a real HTTP backend — JSON in, JSON out, GET/POST, webhooks, curl — for public endpoints and integrations. Secrets hold API keys and tokens; they never land in the client bundle, never get pasted into chat, and never show up in View Source, and preview and production both get them. Existing Vite/React projects keep working unchanged; only new projects are born full-stack.

AI Studio Cloud

Oct 9, 2026 — a built-in backend in one click, at Your project › More › Cloud › Overview: choose Enable Cloud and confirm, or ask in chat and accept the prompt. AI Studio only builds against Cloud after you confirm, and your published site stays as it is until you publish again. Database (More › Cloud › Database): your app can save records and look them up — tell AI Studio what to remember in plain language and it designs the tables and access rules (row-level security); browse tables, rows, and policies here. Users (More › Cloud › Users): sign-up, sign-in, and password reset built into your app; signup, invite, and password-reset emails go out through your account's email, and their links open your app. Version 1 is email/password only — no social login. Storage (More › Cloud › Storage): files your app can upload and serve — create buckets, browse files, and set upload limits. Usage and size (More › Cloud › Overview › Advanced settings): see how full your backend is and give it a bigger size as your app grows. Cloud is billed for the time it runs, and a paused backend can still be charged for the space it holds; a bigger disk costs more and cannot be made smaller later. Removing Cloud (same Advanced settings) deletes that project's database, users, and files — there is no database file to download first, so it asks you to confirm, and other projects are not affected. Cloud works only on projects on the newer TanStack Start stack; move an older React project first from Project settings, and migrating alone does not turn Cloud on.

Payments & checkout

Oct 8, 2026 — native payments at More › Payments: turn on Payments, pick products from your Products catalog, and ask AI Studio for a store or a checkout page. Ask for an online store with product pages and a cart, or one standalone checkout page; checkout can sit on its own page or open in a pop-up. Checkout is a ready-made, platform-managed hosted checkout component that AI Studio places in your app — it never writes payment code, card data never touches app code, and totals are checked on the server so buyers are charged exactly what they see. Buyers pay with cards, PayPal, and the other methods your connected payment gateway supports. Sell recurring plans with free trials and setup fees, show buyers one extra offer right after checkout (one-click post-purchase upsell, one per order), and let buyers apply coupon codes, with gift cards on one-time purchases. Every sale lands in your CRM: each purchase creates the contact and the order in your sub-account, like any other sale, and checkout follows the buyer's browser language in 13 languages. Payments start in Test mode, where only test cards work — switch to Live in More › Payments when you are ready to take real money. Products must first exist in the sub-account Payments catalog AND be included in the online store, or the build cannot see them.

Analytics & Submissions

Oct 8, 2026 — built-in measurement with no setup or tracking code, on by default for every published site. Analytics inside your project (Your project › More › Analytics › Overview): 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 form submission in one place (More › Analytics › Form Submissions): 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. All your sites in Sites Analytics (Sites › Analytics › AI Studio): see every AI Studio site next to your Funnels and Websites, or pick one project to focus on it. Know where every lead came from (Contacts › Contact details › Activity): contacts created from your site keep their visit history — the pages they viewed, where they came from, and the form they submitted. Visits are measured on your site's own domain, so fewer are lost to ad blockers. Page views are counted from October 8, 2026; older opt-ins still show, but the opt-in rate for days before that is not meaningful. 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.

SSR migration

Sep 22, 2026 — upgrade an existing project to server-side rendering (SSR) from Project settings › Migrate to SSR. AI Studio creates a separate copy and migrates it in the background, so your original project stays live while you review the upgrade and your original is never changed. Review and test the new copy before publishing it: the migration is automated and may need a few fixes. If your project uses form tracking or workflow triggers, reconnect or update them in the migrated copy before publishing.

Shell execution

Sep 3, 2026 — AI Studio can now run commands inside your project to inspect the live app, investigate errors, recover from environment issues, and verify fixes, like a developer working on your behalf. The problem it solves: generating code is not enough — the agent could change your app but had fewer ways to see what was actually running, which led to guess-based fixes, stale previews mistaken for broken code, and extra back-and-forth for you to explain what went wrong. The improved shell harness lets the agent inspect the running app, dig into errors and logs, test real behavior, recover a stuck preview, and verify the result before it finishes. Commands stay focused and unsafe or unnecessary actions are blocked. Ask as usual; when deeper investigation is needed, the harness keeps commands controlled, captures useful failure output, and avoids repeating work AI Studio already does — fewer assumptions, fewer retries, and a better chance of a working result in one request.

Use cases

Campaign microsite

Describe the offer and audience; AI Studio drafts a landing page with copy and a lead form, then publish to a custom domain.

Booking-first site

Generate a services page that embeds a calendar and lets visitors book directly, then refine the wording conversationally.

Form + follow-up

Build a qualification form page; on submit it creates a contact and fires a nurture workflow.

Challenge portal with login

Enable Cloud, then prompt for a member portal: users sign up with email/password, daily homework is saved to the database, and worksheets go to Storage.

Sell a course or VIP upgrade

Add Payments, pick the product from the Payments catalog, build a checkout page, test with test cards, then go live — with a one-click upsell right after checkout.

Measure a launch funnel

After publishing, check More › Analytics › Overview for opt-in rate by page and source, then open Form Submissions to follow each lead to its CRM contact and visit history.

Assessment scored server-side

Build a quiz on the TanStack Start stack: the questions render server-side for SEO, a server function scores the answers without exposing the scoring logic to the browser, and the result page is a unique URL that can be shared.

Onboarding wizard that saves progress

Enable Cloud first, then build a multi-step onboarding app: progress is saved to the Database as the user goes, files go to Storage, and the user can log back in with email/password to finish later.

Challenge ticket page with VIP upsell

Create the ticket and VIP products in the Payments catalog first, add Payments in Test mode, build the ticket checkout page, test the purchase and the one-click VIP upsell with test cards, then switch to Live.

Sales-call prep from visit history

Before a call, open the contact in the CRM and read Contacts › Contact details › Activity: which AI Studio pages they viewed, where they came from, and which form they submitted, so the call starts from what they already saw.

Fix a broken preview without guessing

Describe the symptom in chat as usual and let Shell execution inspect the running app, read the error and logs, test the real behavior, and verify the fix before it finishes — instead of re-prompting with guesses about what went wrong.

Move an old React site to SSR for SEO

Use Project settings › Migrate to SSR to create a separate copy, review and test the copy, reconnect its forms and workflow triggers, and only then publish the copy — the original stays live the whole time.

AI prompt patterns

Copyable templates for prompting an AI agent about this feature.

Brief a site generation
Build a [type] site for [business/audience] with these pages: [pages]. Tone: [tone]. Goal: [primary conversion]. Include a [form/calendar/booking] on [page].
Refine by chat
On the current page: [add/change section], rewrite the hero to emphasize [benefit], match the [brand] palette, and shorten the about section to [length].
Wire it to the CRM
Make the [form] on [page] create a contact, set tag [tag], and trigger [workflow] on submit.
Build with a Cloud backend
Enable Cloud, then build a [type] app with email/password login, a [table] table for [records], and a Storage bucket for [files]. Keep it on the Tiny tier to start.
Sell and measure it
Add Payments for [product] with a [one-time/subscription] checkout and a one-click upsell for [upsell], test in Test mode, then check Analytics for opt-in rate by page and source after launch.
Build a full-stack app
Build this as a new TanStack Start project with SSR, a server function to [backend task, e.g. score the quiz / call the API], a REST endpoint at /api/[name] for [webhook/public use], and a Secret named [name] for the [service] key. Never put the key in the prompt or the client code.
Design the Cloud schema first
Enable Cloud, then create a table for [records] with fields [field: type, ...], row-level security so users only see their own [records], email/password login, and a Storage bucket for [files] with a [size] upload limit.
Migrate to SSR safely
Migrate this project to SSR as a separate copy, keep the original live, review and test the copy, reconnect the [form/workflow] in the copy, and do not publish the copy until I confirm it works.
Verify a fix, do not guess
The [page/preview] shows [symptom]. Inspect the running app, read the error and logs, test the real behavior, fix the cause, and verify the fix before you finish. Do not re-prompt with a guess.
Name pages and forms for Analytics
Give every page a distinct name and path ([page names]) and name each form descriptively ([form names]) so More › Analytics › Overview and Form Submissions stay readable after launch.

Integrations & connections

  • Publishes to custom domains like the Funnel & Website Builder
  • Generated forms write to contacts and trigger workflows
  • Embeds calendars and booking experiences
  • Copy/images produced by the Content AI engine
  • Payments create the CRM contact and order in the sub-account, like any other sale
  • Analytics links form submissions to the CRM contact and its visit history
  • Cloud database, auth, and storage live inside the project — no external backend needed

Gotchas & limits

Things an AI should not assume about this feature.

It generates web experiences, not AI agents — use Agent Studio or Managed Agents for conversational agents.
Hosting above the base tier may incur extra cost; verify your plan before publishing.
AI-generated copy and prices must be fact-checked before going live.
Complex custom logic may still need manual code edits the conversation can't fully express.
Cloud works only on TanStack Start projects; move an older React project first, and migrating alone does not turn Cloud on. Cloud is billed for the time it runs, a paused backend can still be charged for storage, a bigger disk costs more and cannot be made smaller, and removing Cloud deletes that project's database, users, and files with no download first.
Payments start in Test mode — only test cards work until you switch to Live in More › Payments. Products must first exist in the Payments catalog and be included in the online store, and the one-click upsell is one per order.
Analytics page views are counted from October 8, 2026; older opt-ins still show, but the opt-in rate for days before that is not meaningful. Forms connected before that date keep counting opt-ins, but to link a submission to the pages that visitor viewed first, ask AI Studio to reconnect form tracking, then publish again.
Shell execution verifies the live app — it does not replace publishing. The harness keeps commands controlled and blocks unsafe or unnecessary actions.
SSR migration creates a separate copy — review and test it, and reconnect forms and workflows in the migrated copy, before publishing it.

Related features