Insites AI · Build with AI in your editor
Tutorial: Deploy a Page with VS Code
Last updated 20 November 2026
Connect VS Code 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 VS Code. You connect VS Code 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 VS Code 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.
- VS Code with GitHub Copilot or the Claude Code extension, and the Insites CLI.
- An empty project folder. Make a new folder for this tutorial and open it in VS Code.
Step 1: Connect VS Code to CloudShell
- In your project folder, run this in the VS Code terminal:
insites-cli ai init --tool vscode --yes - Reload VS Code so it loads the new server.
- When VS Code asks, start the CloudShell server.
Do not paste a password, API key or site ID anywhere. CloudShell does not need one.
Step 2: Sign in with your Insites account
- The first time your assistant uses CloudShell, your browser opens an Insites sign-in page.
- Sign in with your Insites account, the same way you sign in to the Console.
- Approve the access request, then go back to VS Code.
CloudShell now acts as you, with the same access you have in the Console.
Step 3: Give your assistant the Logic Engine
Open the Chat view and choose agent mode. 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 4: Choose your site
Send this, with your own site name:
List my Insites sites, then select the one called my-staging-site.Your assistant asks before it uses each CloudShell tool. Read what it is about to do, then allow it. Check that the reply names the site you meant.
Step 5: Ask for a page and deploy it
Send this:
Create a page at /hello with a heading that says Hello from VS Code and one short
welcome paragraph. Save it in this project as app/views/pages/hello.liquid and
deploy it to the selected site. Then check the deploy status and the logs.Your assistant writes the file in your project folder, then sends it to CloudShell, which deploys it. Approve the deploy when asked. Because the file is in your folder, you can open it, change it and ask for another deploy at any time.
Step 6: Check it is live
- Read the 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: Check the logs on the selected site for errors and fix them.
Step 7: 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:
Show my recent deployments on the selected site and restore the previous
version of app/views/pages/hello.liquid.To remove the test page, ask your assistant to delete app/views/pages/hello.liquid from the site. 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 which site is selected before you deploy. See Working on Several Sites.
- VS Code does not use CloudShell. Reload VS Code and check that the CloudShell server is started. Use the Chat view in agent mode, which can call tools.
- The sign-in has expired. Connect again as in Step 1, and sign in when the browser opens.
- Your assistant keeps making the same mistake. See When your AI gets stuck.