# Vercel auth handling and PR re-run commands

> 2 updates: Re-run from the PR comment, Vercel-protected sites no longer fail on the first 401

Source: https://qa.tech/changelog/2026-04-17

---
2 updates shipped on April 17, 2026.

In this release

1.  01[Re-run from the PR comment](#2026-04-17-rerun-from-pr-comment)
2.  02[Vercel-protected sites no longer fail on the first 401](#2026-04-17-vercel-protected-sites-no-longer-fail)

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](#2026-04-17-rerun-from-pr-comment)
    
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](#2026-04-17-vercel-protected-sites-no-longer-fail)
    

## 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](https://qa.tech/demo)

[QA.tech](https://qa.tech/)

SOC 2 Type 2 compliant

![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)

### Product

-   [Platform overview](https://qa.tech/product)
-   [AI QA Testing](https://qa.tech/ai-qa-testing)
-   [Web Testing](https://qa.tech/product/web-testing)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Use cases](https://qa.tech/use-cases)
-   [Changelog](https://qa.tech/changelog)

### Compare

-   [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress)
-   [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright)
-   [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl)
-   [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf)
-   [AI vs Human QA](https://qa.tech/saas)

### Resources

-   [Docs](https://docs.qa.tech/)
-   [Blog](https://qa.tech/blog)
-   [Events](https://qa.tech/events)
-   [Pricing](https://qa.tech/pricing)
-   [Case Studies](https://qa.tech/case-studies)

### Company

-   [About](https://qa.tech/about-us)
-   [Partnerships](https://qa.tech/partnerships)
-   [Press](https://qa.tech/press)
-   [Contact Us](https://qa.tech/contact)
-   [Privacy Policy](https://qa.tech/privacy-policy)
-   [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf)
-   [Security & Compliance](https://trust.qa.tech/)

### Social

-   [](https://www.linkedin.com/company/qa-tech-ai/)
-   [](https://x.com/getqatech)
-   [](https://www.instagram.com/getqatech/)

© 2025 QA.tech. All rights reserved