Page HTML
To write tests and find a moved element again.
Learn more
Page HTML and the lists of elements the crawl found, to write tests and to find a moved element again.
It runs on a machine you control. Here’s exactly what leaves it, and what stays.
Nothing goes to the TestPilot team.
Through Claude Code on your machine. No TestPilot server in between.
To write tests and find a moved element again.
Page HTML and the lists of elements the crawl found, to write tests and to find a moved element again.
Only for checks that need vision.
Screenshots, for checks that need vision (a produced result, a visual check, an assistant’s reply).
To explain why a test failed.
Test titles, descriptions and steps, and the details of a failure, to explain why it failed.
Uploads you add for extra context.
Documents you upload for extra context, and the words around an upload field when a sample file has to be written for it.
AI runs through the Claude Code command-line tool on the machine running TestPilot, signed in with that machine's Claude account. There is no TestPilot server in between: what Claude needs goes from your machine to Anthropic, and Anthropic's terms for that account apply.
Screenshots and page HTML contain whatever the page shows. Point TestPilot at a test account with test data wherever you can.
All in its data folder (DATA_DIR, ./data by default).
Projects, tests, runs, results, saved logins.
data/testpilot.db: projects, tests and their step history, runs and results, what the crawl learned, cached AI answers, saved logins and the email log.
Screenshots, videos, reports, your data files.
data/projects/<project id>/: screenshots, videos, reports and the data files you upload.
Reused instead of asking twice; expire in 30 days.
Claude’s answers are reused when the same question comes up again (the same page crawled again, the same failure, the same document), so it isn’t asked twice. They expire after 30 days; AI_CACHE=off turns this off.
In the local database, not encrypted at rest yet.
Settings only show which ones are set.
Tokens and Basic Auth go to your site’s host only.
Signed session, checked on every request.
All that TestPilot’s own code connects to.
| To | When and what |
|---|---|
| Your website | Every crawl and every test, from a Chromium browser that never hides that it’s automated. |
| Anthropic, through Claude Code | What the AI needs (the list above), under the Claude account signed in on that machine. |
| Your SMTP server | Only when you set up email: the PDF report after a scheduled run, or a short “Site down” alert. |
| Google and Cloudflare (by default) | Only when your site doesn’t answer: a request to a well-known address to tell an outage from TestPilot’s own connection. The addresses can be changed (CONNECTIVITY_CHECK_URLS). |
| The TestPilot team | Nothing. TestPilot doesn’t report back to us. |
Tests, runs, files, crawl data and cached answers go.
Deleting a project removes its tests, runs and results, data files, crawl knowledge, cached AI answers, and its folder of screenshots, videos and reports.
Its results, screenshots, videos and report go.
Deleting a run removes its results, screenshots, videos and report.
Handled under your Claude account’s terms.
What was already sent to Anthropic is handled under your Claude account’s terms, not by TestPilot.
Bring them to a demo. We'll show where each of these lives in the running product.