Release notes··4 updates
4 updates shipped on June 30, 2026.
Update 01 of 04
Press Cmd+K (or Ctrl+K) to quickly copy your organization or project UUID to the clipboard.
Two new command palette actions make it faster to grab the identifiers you need when working with the API or filing a support request: "Copy Current Organization UUID" is available on any authenticated page, and "Copy Current Project UUID" appears when you're inside a project.
Update 02 of 04
docs.qa.tech now has a dedicated guide to the Maximum Concurrent Tests setting and how it affects your test runs.
The new Core Concepts → Parallel Test Execution and Concurrency Limits page explains how to tune the concurrency cap for your environment – useful when you want to avoid overloading a staging server or maximize throughput on a resilient one. It includes a decision table, setup steps, and an FAQ.
Update 03 of 04
A new checklist page covers everything to prepare before starting a proof of concept with QA.tech.
The checklist walks through choosing and configuring a staging environment, test data requirements (including PII handling), network access options (IP allowlisting, SSH tunnels, WAF configurations), email delivery setup, authentication configuration, and a pre-kickoff smoke test. Find it under Get Started in the docs sidebar.
Update 04 of 04
The PR review agent now analyzes every changed file in a pull request, up to GitHub's 3,000-file limit.
GitHub's API returns changed files in pages of 100. The review agent now fetches all pages up to GitHub's 3,000-file limit, so large refactors, dependency upgrades, and migration PRs get a full-file-list review instead of a partial one.
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.