Insites AI · Build with AI in your editor
Tutorial: Deploy a Page with ChatGPT
Last updated 18 November 2026
Connect ChatGPT to CloudShell and deploy your first page, step by step.
What you will do
This tutorial takes you from nothing to a live page on your Insites site, using ChatGPT on the web. You connect ChatGPT to CloudShell, choose a site, ask for a page, and check that it is live. It takes about 15 minutes.
For the background, see Use ChatGPT with Insites and CloudShell MCP.
Before you start
- An Insites account. The same one you use to sign in to the Console.
- A site, with the Developer role or above on it. A lower role can read logs but cannot deploy. Use a staging site for your first try.
- A ChatGPT plan that allows custom connectors. Connecting your own MCP server uses ChatGPT's developer mode, which needs a paid plan. On a Business or Enterprise workspace, an admin may need to turn it on for you.
- ChatGPT in a web browser at chatgpt.com. Set the connector up on the web; the desktop and mobile apps may not show the setting.
Step 1: Turn on developer mode in ChatGPT
- Open chatgpt.com and sign in.
- Click your name in the bottom left, then Settings.
- Open Apps and Connectors (it may show as Apps or Connectors).
- Open Advanced settings and switch on Developer mode.
ChatGPT changes its menu names from time to time. If a name here does not match, look for the place where you add a custom connector or an MCP server.
Step 2: Add CloudShell as a connector
- Back in Apps and Connectors, click Create.
- Fill in the form:
- Name:
Insites CloudShell - Description:
Deploy pages, read logs and manage settings on my Insites instances. - MCP server URL:
https://cloudshell.insites.io/mcp - Authentication: OAuth
- Name:
- Tick the box to confirm you trust the connector, then click Create.
Do not paste a password, API key or site ID anywhere. CloudShell does not need one.
Step 3: Sign in with your Insites account
- ChatGPT opens an Insites sign-in window. If it does not, click Connect on the new connector.
- Sign in with your Insites account, the same way you sign in to the Console.
- Approve the access request. The window closes and the connector shows as connected.
CloudShell now acts as you, with the same access you have in the Console.
Step 4: Start a chat with CloudShell turned on
- Start a new chat.
- Click the + beside the message box, then More, then Developer mode.
- Choose Insites CloudShell so it is switched on for this chat.
You need to do this in each new chat.
Step 5: Give ChatGPT the Logic Engine
The Insites Logic Engine is the public set of rules for building on Insites. Paste this as your first message:
Before you write any code for this project, read the Insites Logic Engine at
https://github.com/insites-io/insites-logic-engine
Start with skills/insites/SKILL.md and follow its decision trees, then use the
reference docs in skills/insites/references/ and the rules in logic-engine/rules/.
Whenever you are unsure how something works on Insites, check the Logic Engine
first instead of guessing, and follow its conventions over your own assumptions.Step 6: Choose your site
Send this, with your own site name:
List my Insites instances, then select the one called my-staging-site.ChatGPT asks you to approve each CloudShell action. Read what it is about to do, then click Confirm. Check that the reply names the site you meant. Every later result names the site too.
Step 7: Ask for a page and deploy it
Send this:
Create a page at /hello with a heading that says Hello from ChatGPT and one short
welcome paragraph. Save it as app/views/pages/hello.liquid and deploy it to the
selected instance with insites_deploy. Then check the deploy status and the logs.ChatGPT writes the file and sends it to CloudShell, which deploys it. Approve the deploy when ChatGPT asks.
How the file gets there. ChatGPT on the web cannot read files on your computer, so it writes the page content straight into the deploy. That works well for pages and partials of normal size. For a large file, such as an image or a long script, host it at a public https address and ask ChatGPT to deploy it with insites_deploy_from_url. Only use a public address for content anyone may read, and never put a secret in it.
Step 8: Check it is live
- Read ChatGPT's reply. It should show the deploy status as success and no errors in the logs.
- Open your site address with
/helloon the end, for examplehttps://my-staging-site.example.com/hello. - You should see your heading and paragraph.
If the page does not appear, ask ChatGPT: Check the logs on the selected site for errors and fix them.
Step 9: Undo a change
When a deploy replaces a file that was already there, CloudShell keeps a copy of the old file for 30 days. To roll back, ask ChatGPT:
Show my recent deployments on the selected instance and restore the previous
version of app/views/pages/hello.liquid.To remove the test page, ask ChatGPT to delete app/views/pages/hello.liquid. Every change also shows in the Console change log, with who made it.
If something goes wrong
- A tool is refused. Your role on that site is too low. Ask the account owner to give you the Developer role in the Console.
- The wrong site changed. Ask ChatGPT which site is selected before you deploy. See Working on Several Sites.
- ChatGPT does not use CloudShell. Check that developer mode and the Insites CloudShell connector are switched on for this chat (Step 4).
- The sign-in has expired. Open the connector in Settings and connect again.
- ChatGPT keeps making the same mistake. See When your AI gets stuck.