Automated QA forAI-written code.
Your agents open pull requests faster than anyone can review them.
On every pull request, Paidwen opens your app and uses it like a real user. It creates an account, logs in and fills in your forms. If something breaks, it blocks the pull request and shows you a video of what broke.
Paidwen replays your user journeys in a real browser.
A journey is a few lines of YAML. Paidwen clicks, types and reads the page like a user, and compares a broken journey with the base branch.
paidwen.yml
journeys: - id: sort name: Sort the invoices by amount account: true steps: - goto: /login - fill: { field: Email, value: "{{account.email}}" } - fill: { field: Password, value: "{{account.password}}" } - click: Log in - goto: /invoices - click: Largest first - expect: { text: "$5,936.40" }
- Your real app
- Paidwen starts it from your compose file or Dockerfile, with a fresh database and your seed script.
- No real payment or email
- Stripe, email, storage and AI APIs answer from local mocks by default.
- Journeys written for you
- npx paidwen initwrites a first journey for each public page.- npx paidwen recordrecords a journey while you click.
- Only the pull request is blamed
- A journey that also breaks on the base branch does not count against the pull request.
Your agent reads the verdict and fixes the pull request.
The verdict names the broken journey, the failed step and what the browser saw. Paidwen replays the journeys on every new commit.
- Claude Code, Codex, Cursor and Copilot
- Paidwen verifies the pull requests of every agent and of your developers with the same journeys.
- Agent pull requests detected
- Paidwen recognizes them by their branch prefix, their author and their Co-Authored-By lines.
- One command for the agent
- npx paidwen verdictprints the last verdict, ready to paste.- npx paidwen mcpserves it to your agent.
The dashboard keeps every verification of every repository.
Each row is a pull request with its verdict, its journeys, its duration and the agent that wrote it.
- The month in four numbers
- Pull requests verified, broken, stopped before the merge, and the share written by agents.
- One page per verification
- The verdict, the video, the commit and the workflow run.
- Copy for your agent
- The verdict leaves the dashboard in one click, ready to paste.
- A monthly report
- Verified pull requests per week and per repository, and the review hours saved.
Your code never leaves your GitHub Actions runner.
The servers of Paidwen receive the verdict lines and the link to the video. They never read or store your code.
Your GitHub Actions runner
GitHub destroys the machine after the job.
Verdict lines and video link
Paidwen
- No Contents permission
- The GitHub App cannot read the code of your repository.
- A signed engine
- The runner refuses any engine whose signature does not match the pinned public key.
- Forks without secrets
- A maintainer starts the first verification of a new contributor.
- No AI model in the replay
- The replay is a deterministic Playwright script.