What it can and can't do

What it can doCopy Anchor Link

Sites

• See every site in the workspace it was given access to
• Create a new site from any of the site templates, with the template's pages, sample content and colours
• Change the colours, corner rounding and light/dark setting for a whole site

Pages

• List the pages of a site and read any one of them
• Search every page for a phrase and tell you where it appears
• Add a page, either blank or from a starter — starters that need a collection bring the collection and its detail page along with them
• Rename a page, move it to a new address (with a redirect from the old one), fill in its search-result title and description, make it members-only, or make it the home page
• Rewrite copy, several places at once

Page layout

• Add a section from the ready-made ones — a hero, a feature row, a pricing table, a testimonial block — and then replace the sample words with real ones
• Add a single block into an existing section or card
• Move a section up or down, duplicate it, or remove it
• Change settings that aren't words: where a button goes, how many columns a grid has, which image is used, how things are aligned

Content collections

• List your collections and their fields
• List and search entries
• Add or update entries in bulk, and publish or unpublish them

Images

• Generate one with AI from a sentence — a Nordic living room, oak and oatmeal textiles, morning light — and put it straight onto the page
• Fetch an image from a public web address into the media library and use it on a page

Seeing your work

• Hand you a no-login preview link for any page's draft
• Take a screenshot of a page — desktop, tablet or phone width, top of the page or all of it

Before and after going live

• Run the pre-publish checks and tell you what's broken
• Publish
• Roll back to an earlier published version

Deleting — pages and whole sites, but only if you ticked that permission, and only after it repeats the page address or site name back exactly. See below.

Letting it make the picturesCopy Anchor Link

Ask for a banner with a photo of a bright living room and the assistant writes the description, generates the image and puts it on the page in one go. It can see what came out, so if the picture isn't what you meant it can reword the description and try again without you having to look at each attempt.

Three things worth knowing before you ask for a dozen of them:

• Every image it generates is kept. They all land in your media library under a folder called AI. This is different from generating images yourself in the editor, where you see four and only the one you pick is saved — the assistant doesn't need to be shown four, so it makes one at a time unless you ask for several (one per slide of a carousel, say). If it took a few tries, the earlier attempts are still in that folder for you to delete.
• It comes out of the same monthly allowance as generating images in the editor — 10 a month on Free, 100 on Starter, 500 on Pro, 2000 on Business. One request counts as one, however many pictures it made. (Assistant access itself needs Starter or above.)
• Don't ask for words in the picture. Text and logos come out as gibberish — that's the image model, not us. Put real text in a heading on top of the image instead.

If the allowance runs out, or you'd rather use a specific photo, the assistant can still pull an image in from any public web address.

How you see what it didCopy Anchor Link

Tessolo is a visual builder, so "I rewrote the hero" is only half an answer. Two things come back to you without asking:

• A preview link. Every change the assistant makes ends with a link to that page's draft. It opens in any browser, needs no login, and always shows the current draft — not the live site. Click it and you're looking at exactly what the assistant just did.
• A screenshot. Ask show me how it looks now and the assistant takes a picture of the page and shows it to you in the chat. It can do desktop, tablet or phone width, and the whole page rather than just the top.

On top of that it tells you, line by line, which words changed from what to what — and before its first change to a page it saves a backup you can restore from Site → Versions.

What it deliberately can't touchCopy Anchor Link

Some of these are dangerous, some are just none of an assistant's business:

• Form submissions. They're your visitors' personal details, and they're text written by strangers — exactly the kind of thing that shouldn't be fed into an assistant's context.
• Custom code and tracking tags. Anything that can run scripts on your published site stays with a human.
• Members, roles and billing. An assistant shouldn't be able to widen its own access.
• Domains and payment settings. Getting these wrong is expensive and slow to undo.
• Deleting media. It can add and generate images, but not remove them. The media library is shared across the workspace — one deletion can break a site the assistant was never asked to touch. That's also why generated images it decided against are left for you to clear out.
• Embedded code that runs scripts. It can drop in a map, a form or a video through the ready-made embeds, but anything that would run a script on your published site stays with a human — same rule as custom code above.

There's also one thing it can't do by design rather than by policy: it can only change words in places that are meant to be words. Button targets, form identifiers and embed code look like text but aren't, so "rewrite the copy" can never quietly repoint a button or break the form that feeds your submissions list.

Why publishing and deleting are off by defaultCopy Anchor Link

When you approve an assistant, reading and editing drafts are ticked and publishing and deleting are not. That's deliberate:

• Editing is safe to undo. Everything the assistant changes is a draft. Your live site doesn't move until something publishes.
• Publishing is visible to the world immediately. It's recoverable — you can roll back to any earlier version — but people may have seen it.

If you do give it publishing rights, it still has to run the checks first: when something is actually broken, it has to tell you and get a clear yes before it can publish anyway.

Deleting works differently again — there is no "get it back". So on top of the permission, the assistant has to repeat the page address or the site name back exactly before anything is removed. That means it has to have looked at the thing it's about to delete, and it gives you one more chance to say no.

Editing collection entries is ticked by default, because entries are drafts too. Putting an entry live still needs the publishing permission, even though editing it doesn't — otherwise ticking "can edit content" would quietly hand over the right to publish.

If it gets something wrongCopy Anchor Link

It changed a draft you didn't want. Before an assistant's first change to a page it saves a backup of that page, labelled with the assistant's name — so Site → Versions always has the version from just before it started. Restore that, or open the page in the editor and fix it by hand. Note that the editor's undo button won't reach an assistant's changes: undo only covers what you did in that browser tab.

It published something you didn't want. Site → Versions → roll back to the version before it. That takes effect right away.

You want it to stop entirely. Revoke its access under Workspace settings → Agent access. The next thing it tries fails immediately.