Release notes··2 updates

Vercel auth handling and PR re-run commands

2 updates shipped on April 17, 2026.

  1. Update 01 of 02

    Re-run from the PR comment

    Tell the bot to re-test, or test something specific, by commenting on the PR.

    Bot comments on PRs now include a footer explaining how to re-trigger testing: comment @qa.tech to re-run, or @qa.tech test the checkout flow to focus on a specific area. Works on GitHub and GitLab. No need to leave the PR or open the QA.tech app.

    # Direct link

  2. Update 02 of 02

    Vercel-protected sites no longer fail on the first 401

    The agent waits to see if your bypass headers actually work before giving up.

    When testing a Vercel deployment with password protection, the initial request returns a 401 even when bypass headers are configured correctly – the page loads anyway. The agent used to bail on the first 401 and report a Vercel auth error. It now waits to see whether the loaded page is the actual app or the "Authentication Required" wall, and only fails when the wall is still showing.

    # Direct link

Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

Get a demo