Site Discovery

What Discovery Does

A discovery works in multiple phases. In the first phase, agents start at your URL and explore broadly — clicking through navigation, opening menus, following links. As they go, they record every page, form, button, and interaction they find.

After each phase, the system analyzes what was found and identifies gaps — pages that were linked to but not visited, forms that were seen but not filled in. It then sends more agents to explore those areas in subsequent phases. This continues until the app is thoroughly mapped.

The end result is an app map — a structured inventory of everything the agents found — and a set of journey suggestions that you can review, edit, and save as real journeys.

When to Use Discovery

• Getting started with a new app. If you just set up a project and have no journeys yet, run a discovery first. It will give you a set of suggested journeys to start from, so you do not have to write everything from scratch.
• After a major refactor. When your app has changed significantly — new pages, restructured navigation, redesigned features — run a fresh discovery to see what the app looks like now and identify any new areas that need test coverage.
• Periodic coverage checks. Run a discovery every few weeks to find pages or features that exist in the app but have no test journeys. This helps you close the gap between what your team thinks the product does and what it actually does.

Discovery is broad — it explores everything it can reach. Journeys are deep — they test one specific flow thoroughly. Use discovery to figure out what to test, then use journeys to test it.

How to Run a Discovery

Go to Setup > Site Discovery in the sidebar and click Run Discovery.

You will see a few fields:

• Project. Select which project this discovery belongs to. Journey suggestions will be created under this project.
• Starting URL. The URL where agents will begin exploring. Use the login page if your app requires authentication, or the home page if it does not.

Click Run and the discovery starts. You can watch progress in real time — each phase shows the agents that are currently running, and the app map updates as new pages are found.

Want to run discoveries programmatically? See the Discoveries API reference.

What You Get Back

When a discovery completes, you get three things:

• App map. A structured inventory of every page the agents found. Each entry shows the page URL, a description of what is on the page, and the forms and interactive elements available. This gives you a bird's-eye view of your application.
• Journey suggestions. Based on what agents found, the system generates test journey prompts for the key flows in your app. These are ready-to-use — you can review them, edit them if needed, and save them as real journeys with one click.
• Agent conversations. The full log of what each discovery agent did — every page it visited, every action it took, with screenshots. Useful for understanding how the agents navigated your app and spotting issues they encountered.

Acting on Results

The most valuable output of a discovery is the journey suggestions. Here is the typical workflow:

• Review suggestions. Go through the suggested journeys. Each one has a name, description, and prompt. Some will be exactly what you need, others might need tweaking.
• Save the ones you want. Click to create a journey from a suggestion. You can edit the prompt before saving. Dismiss suggestions you do not need.
• Add to a schedule. Once you have a set of journeys, add them to a schedule so they run automatically on a recurring basis.

You do not have to accept every suggestion. Start with the ones that cover your most critical flows, then add more over time. See the Writing Effective Journeys guide for tips on refining journey prompts.

Discovering authenticated pages

If your application requires login, discovery agents need a way to get past the authentication gate. Without one, they only explore publicly accessible pages.

The simplest setup is a dedicated test account whose credentials you reference directly in the discovery prompt. Start the discovery on your login page so the agent has somewhere obvious to authenticate first, then keep exploring once it lands in the logged-in part of the app.

If the login flow involves a magic link or verification email, create a mailbox for the test account and attach it to any journeys spawned from the discovery. The mailbox gives the agent read access to the inbox so it can complete the email step.