Willo's browser
How Willo opens, reads and clicks through your live site and draft preview in its own browser, signed out or signed in, and what it never does there.
On this page
Willo has its own browser. It uses it to look at your site the way a visitor does, check that a change landed, and click through a flow to find what's broken. Willo shows you a screenshot of what it saw in the chat.
What it can do
- Look. Open a page on your live site or your draft preview, take a screenshot of what's on screen, further down the page or one section, and look again after a change. Desktop, tablet and phone widths.
- Read. Get a page's text and outline, and the style of one element (its color, size, spacing, and whether something covers it).
- Click. Click, type into fields, pick options, tick boxes, hover, and press keys such as Enter, Tab and the arrows. Up to eight steps at a time, followed by a screenshot.
- Sign in. Open the pages behind your app's login, as Willo's test user or as you. See Test your app signed in.
Ask in plain words: "check the pricing page on a phone", or "fill in the contact form and show me what happens".
Willo's browser opens your own site only: the live site and the draft preview. It stays on your site's addresses, so a click that leads to another website stops there and is reported.
Signed out, nothing is sent
When Willo clicks through your site while signed out, nothing it does reaches anyone:
- Your site's lead and newsletter forms show their normal success message, but nothing is saved and no one is emailed.
- Any other form, or anything that would save to your database, is held back. Willo lists what the page tried to send.
- A click that would open your Willo checkout is stopped. Willo checks that the product can be sold and tells you the answer, with no payment started.
Signed in
Signed in, Willo sees what that account sees, and it can save records for real when the testing session you approved allows it. Willo's reply says who it was signed in as.
| Signed in as | Sees | Approval |
|---|---|---|
| Willo's test user | What anyone who signs up to your app sees | One card per testing session on the live site; none on a draft, or to look and click once the test user exists |
| You | Everything your own account sees, including your admin pages | One card, for up to an hour; only you can approve it |
Willo's test user is an ordinary account in your app that Willo owns, with no special role. Willo signs in to your app as you only with an account you made yourself.
What it never does
- Type a password, even one you paste into the chat. Willo signs in without one.
- Create an account to sign in as you, or give its test user a role.
- Fill in a card or payment field, or make a payment.
- Download files, open pop-up windows, or leave your site.
- Call your backend functions or change your sign-in settings when it clicks.
- Upload a file on your live site. File uploads run only on a draft, signed in as the test user, on their own card.
Where it runs
Willo's browser works in chat on the dashboard, for an owner, admin or editor. A viewer's chat is read-only, so it never uses the browser. Willo doesn't use its browser for your own AI agent's requests through MCP, from email, in Agent Programs, or in other work it does on its own.
Signed in as you, a save after Willo read outside content in the same request, such as another website, an email or rows from your database, asks first. On a business with connectors, clicks and sign-ins after outside content ask too.
How long screenshots are kept
Screenshots are kept for 30 days. Screenshots taken while signed in as you are kept for 7 days, because your admin pages can show your customers' data. What Willo read from a page stays in the chat's history like any message.
Limits
- Willo's browser signs in only to apps that use the member login Willo builds. It can't sign in through a custom or PIN login, Google or another sign-in provider alone, or a session kept in a server-side cookie. Willo says which page it couldn't see.
- Signed in as you, Willo's browser doesn't load content from other websites, such as a map, payment or chat widget, doesn't call your backend or database functions, and stops at a second-factor (MFA) challenge.
- A screenshot shows what the page looked like. It doesn't prove which publish is live.
- Each business has one Willo browser. A session signed in as you ends when anyone else uses it, or you use it from another chat.
Related: What stops for your approval, Drafts and publishing.
Questions
Can Willo see the pages behind my app's login?
Yes. Willo signs its browser in as its own test user, or as you after you approve a card, then opens the page. See Test your app signed in.
Will Willo's clicks send real emails or create real leads?
Not while it's signed out. Your site's forms show their success message and nothing is saved or sent. Signed in, Willo saves for real only when you allow it, on your live site after you approve a card and on a draft without one.
Can Willo use its browser from my own AI agent?
No. Willo's browser works only in chat on the dashboard.