Your QA agent

Every site you add gets its own AI QA agent: a tester that uses your site the way a customer would, in a real browser, and tells you in plain English when something breaks. You talk to it instead of configuring it.

Open it from your site's page (Talk to your QA agent) or from the dashboard. The chat is on the left; on the right you watch the agent's browser live while it works: the page, its cursor, and what it's doing step by step.

What you can ask it

• Walk my main flow. It finds what visitors come to do (book, buy, sign up, get in touch) and goes through it, stopping before anything is booked, paid or sent.
• Test something specific. "Check the Pro plan costs $50 at checkout." It turns that into a test plan of short steps, runs it now, and keeps it as a weekly test. Ask it to change, re-run or delete a plan the same way.
• Check a page now. "Is the pricing page OK?" In about 30 seconds: broken links and images, errors, phone layout and how fast it loads.
• Re-check a problem you fixed. It checks the page again and marks the problem fixed if it's gone.
• Try a preview deploy or staging site. Give it the address (https://my-app-git-branch.vercel.app) and, if you like, steps to follow. It tests it once without saving anything. Previews behind Vercel's deployment protection need the deploy check instead.
• How fast is my site? Load time, when the main content appears, layout shift, page weight, requests, other companies' scripts, the largest file and memory, with the trend over recent checks.
• Test after every deploy. It writes the GitHub Action for you, with one of your test plans as the steps if you want.
• Test pages behind your login. "Check my dashboard shows my projects." It asks for a test account in a secure form under its message (never type a password into the chat; if you do, it's removed before it's saved). The account is stored encrypted and only used to sign in on your own site, and the agent never sees the password: signing in is done by code, then the agent carries out the steps as that user. Use an account made for testing, not your own. You can remove it beside the chat any time.
• A full pass of the site (Pro): every page it can find, up to 100. See full site scan.

It remembers what you tell it matters, and what it learns about your site, for next time. You'll see those notes beside the chat.

What it won't do

It never pays, books, creates accounts, sends your details or leaves your site, whatever it's asked. The one thing it types into a sign-in form is the test account you saved, and only on your site's own sign-in page. Ask for one of those and it offers what it can do instead, like walking to the payment page and stopping there.

How we recommend using it

1. Let it walk your main flow every week (it does this on its own).
2. Give it one or two test plans for what makes you money: a price, a booking step, a signup.
3. Have it test after every deploy with the deploy check.
4. On Pro, a full pass of the site once a month.