Brain, body, hands and tools: how your AI works on your site
The four parts that let Claude or ChatGPT change your site, and why nothing goes live until someone says publish.
Last checked .
What are the four parts?
Think of it as one helper, put together from four parts.
- The brain is your own Claude or ChatGPT. It understands what you ask and works out what to do.
- The body is your website: its pages, its pictures and the way it sounds.
- The hands are the site manager, the part of our service that works on your site and makes each change as a preview first.
- The tools are the jobs the hands know how to do. The main ones are below.
Before it starts on a site, your AI reads the site's notes: how it sounds, its rules, and what was changed and decided before.
Which tools can my AI use today?
- Change the words on a page, or add a new block of text.
- Add a new page of a kind your site already has, like a recipe on S'mores, or change one that's there.
- Swap a picture, or make a new one from a description.
- On a site with a posting schedule, see what's coming up and move a post to another date.
- See your changes that are waiting, publish one, or undo one.
- Add something you noticed to your site's to-do list.
If you ask for something your site doesn't have yet, like a new kind of page, your AI doesn't build it. It writes it up as a proposal for us to decide on.
What does a request look like, from chat to live?
Say you run S'mores and you open Claude. You ask: "Add a new recipe for campfire banana boats."
Claude reads S'mores' notes first, so the recipe sounds like the rest of the site. Then it adds the recipe as a change and gives you a preview link.
You open the link and see the new recipe on a copy of your site. The live site hasn't changed. If you don't like it, say undo and it's gone.
When it looks right, say "publish". Your AI never publishes on its own.
What may the hands do, and what may they never do?
Changes your AI makes with the tools can touch only the parts of your site that hold its words and pictures, never the code that runs it.
Every change, whoever makes it, goes on a copy of your site first, with its own preview. The hands never publish on their own. Only a "publish" from you or our team does that.
On S'mores, the site manager also works through the site's to-do list on its own, one job at a time, turning each into a preview for you. It never picks up an idea, and it stops when two of its previews are waiting for you.
On other sites, nothing picks a task up on its own.
What if I have more than one site?
One sign-in covers every site you have access to. Every change is for one site, so your AI needs to know which. If it isn't clear, it can list your sites and ask you.
A site can also have its own address for your AI to connect to. S'mores has one. Signed in there, your AI sees S'mores and nothing else, even if you have other sites. A sign-in at one address doesn't carry over to another.
