Both tools are read-only. They scroll and they draw. They cannot click, type, submit or navigate. If you want the assistant to act on your site, that is a Custom Function, where you write the handler.
You do not have to do anything
Page Tools ship with the standard embed snippet and are on by default:How it finds things
The assistant never writes a CSS selector. It sends the words a person would use — “Pro plan”, “Enterprise”, “How it works” — and the loader matches them against the visible text of headings, links, buttons, labels and cells on the page. An exact match wins over a passing mention, so on a pricing page where the Enterprise card says “everything in Pro, plus SSO”, asking to highlight “Pro plan” lights the Pro card, not Enterprise. A matched heading is then widened to the card or section it belongs to, because glowing two words inside a plan looks like a bug. If nothing matches, the assistant is told so and goes back to describing it in words. It never points at something that only shares a word with what it meant.Name things precisely
For anything you want matched exactly — a plan, a tier, a feature card — label it:Keep things out of reach
Mark anything that should never be matched:display:none tab panel full of the right words is never a scroll target, because scrolling to it scrolls to nothing.
What it looks like
The glow is drawn in the widget’s own layer, over your page. Nothing of yours is restyled, no classes are added and no attributes change, so a re-render cannot leave the page in a strange state. It never takes a click, so the visitor can keep using the button it is pointing at. It clears itself after a few seconds, on the visitor’s next click or keypress, or when the assistant points at something else. Only one highlight exists at a time. The page scrolls smoothly unless the visitor’s system is set to reduced motion, in which case it jumps.Turning it off
Per site, on the script tag:Replacing them with your own
Register a handler under the same name and yours runs instead:{ found: false, reason: "…" } when you cannot find the target, so the assistant knows to describe it instead.
Where it works
Page Tools need a page to act on, so they work on the sidebar widget:Related
- Live Website Events — tell the assistant what the visitor is doing.
- Custom Functions — let the assistant act on your site, not just point at it.