Site navigation and actions.
Walk the flows your PR touches like a real user, try the things that go wrong, and catch errors in the console, the network and your links.
Checkout can't be completed
Selecting Place order did nothing and the page stayed on checkout. The confirmation page was never reached.
No error or timeout state when the API is slow
With the order request delayed, the button spins indefinitely and the user is never told anything went wrong.
Completes the main flows your PR touches, like a real user would.
Every step of the session as a thumbnail, with the failing step circled.
Step 4 · Select Place order.The button did not respond and the page stayed on checkout.
From the diff and criteria, Hydrofoil picks the flows the PR affects. A browser agent walks them step by step, reading the page and acting as a user would.
From the diff and criteria, choose what the PR affects.
The browser agent acts as a user would.
Check each step did what it should.
Findings point to the failing step.
Findings appear in the Hydrofoil dashboard and in your GitHub check, with a severity (blocker, major, minor or nit) and a confidence level. Low-confidence findings are marked Needs reviewand don't fail the check.
What each finding includes.
Turn this review on or off for each repository in repository settings.[TBD: add any check-specific options.]
Tries the things users do wrong, and the things networks do wrong.
A form stuck on a spinner because the API was slowed down, next to the finding it produced.
No error or timeout state when the API is slow
With the order request delayed, the button spins indefinitely and the user is never told anything went wrong.
The agent tries the inputs and actions above. For failures and delays it uses Playwright network interception to force API errors and slow responses, then checks what the user sees.
Empty, invalid, long, boundary and Unicode values.
Double submits, back, refresh and expired sessions.
Playwright forces API errors and slow responses.
Look for loading, error and empty states.
Findings appear in the Hydrofoil dashboard and in your GitHub check, with a severity (blocker, major, minor or nit) and a confidence level. Low-confidence findings are marked Needs reviewand don't fail the check.
What each finding includes.
Turn this review on or off for each repository in repository settings.[TBD: add any check-specific options.]
Runs your most important journeys on every PR, to catch breakage outside the diff.
Your journeys with a pass or fail each. Expand one to see the steps.
The payment button stayed disabled after the card was chosen.
You describe journeys per repository in plain English ("Sign up", "Check out with a saved card"). Hydrofoil runs them on every PR alongside the PR-specific review.
In plain English, per repository.
Alongside the PR-specific review.
Pass or fail per journey.
Findings appear in the Hydrofoil dashboard and in your GitHub check, with a severity (blocker, major, minor or nit) and a confidence level. Low-confidence findings are marked Needs reviewand don't fail the check.
What each finding includes.
Turn this review on or off for each repository in repository settings.Define journeys in repository settings. Journeys are written in plain English, not code.
Watches the browser console and network for errors while every flow runs.
The page at the moment an error was logged, beside the console entry itself.
The browser records console output and network activity throughout the run. Hydrofoil flags the entries that matter and the AI helps rank them.
Console output and network activity throughout the run.
Keep the entries that matter.
AI helps order them by importance.
Findings appear in the Hydrofoil dashboard and in your GitHub check, with a severity (blocker, major, minor or nit) and a confidence level. Low-confidence findings are marked Needs reviewand don't fail the check.
What each finding includes.
Turn this review on or off for each repository in repository settings.[TBD: add any check-specific options.]
Crawls the pages your PR touches for dead links and missing images.
A page with a broken image boxed, plus the URLs that failed.
/assets/team/photo.png404/docs/getting-start404/pricing/old500Hydrofoil crawls the impacted pages and checks every link and image.
The pages your PR touches.
Look for errors and wrong destinations.
Look for assets that fail to load.
Findings appear in the Hydrofoil dashboard and in your GitHub check, with a severity (blocker, major, minor or nit) and a confidence level. Low-confidence findings are marked Needs reviewand don't fail the check.
What each finding includes.
Turn this review on or off for each repository in repository settings.[TBD: add any check-specific options.]
Hydrofoil opens each preview in a real browser and posts what it finds to GitHub.