Building with AI

Build on Insites with your own AI tool

This section is for developers who build and deploy with their own AI assistant. Your assistant connects to an instance through Insites CloudShell, learns the platform's rules from the Insites Logic Engine, and keeps a history in GitHub.

It is different from the assistant inside the admin, which the people who run the site use to ask questions and make previewed changes. For how the two fit together, see the Insites AI hub: What Is Insites AI and How the Pieces Fit Together. For the admin assistant itself, see Insites AI in the Instance.

Start here

• Building with AI Overview
• Getting Set Up with Insites and AI: an instance and an AI assistant that deploys through CloudShell.
• Start Here: Build Your First Page with AI: one prompt to paste, step by step.

Tools

• About CloudShell: how any AI assistant deploys to your instance.
• CloudShell Tools: every tool, with example prompts.
• Insites Logic Engine: the public rules that teach AI assistants how to build on Insites.
• Insites GitHub App: deploy on every push to a watched branch.

Working well

• What to Ask Your AI: copy-ready prompts for common jobs.
• What Insites Can Do: a capability list.
• Insites in Plain Words: a glossary.
• Safety Rails for AI Builds: staging, GitHub history, undo and secrets.
• Undoing a Change
• When Your AI Gets Stuck
• Pre-Launch Checklist

Changes made in the admin

Changes the admin assistant applies are written straight to the instance, like any admin edit, and do not reach your repository. Pull them before you deploy, or the deploy overwrites them. See History, Previews and Revert.