1. Update 01 of 05

    Filter and identify pull requests by repo and author

    Multi-repo projects can tell PRs apart at a glance and narrow the list down.

    The Pull Requests view adds a Repo column – hover for the full owner and name – plus a Filters dropdown to narrow by repository or author. Both are multi-select, with "All" and "None" shortcuts per section and a one-click Reset.

    Selections live in the URL, so a filtered view of your PR reviews is shareable and survives a refresh.

    # Direct link

  2. Update 02 of 05

    Stopping a chat response stops it instantly

    Stop freezes the response immediately and won't let a pending analysis or test run resume the conversation later.

    The stop button used to wait on a network round trip before the interface caught up, while the current step's remaining tool calls kept running.

    It now stops the moment you click it. If a site analysis, test run or crawl was in flight, it won't quietly resume the conversation afterwards – a short "complete" notice waits in the queue until your next message.

    # Direct link

  3. Update 03 of 05

    Site analyses dig deeper when you point at something specific

    Ask about a setting or integration a few clicks deep and the agent goes and finds it instead of reporting it doesn't exist.

    Chat-initiated site analyses used to default to a shallow crawl that only reached pages linked from the homepage, so anything nested – settings, billing, admin screens – was out of reach and the agent could wrongly conclude a feature didn't exist.

    Analyses that name a target now crawl deeper automatically, which means test discovery reaches those pages before the agent answers.

    # Direct link

  4. Update 05 of 05

    See what an Xray connection can actually reach

    Testing an Xray connection shows the tests it found, not just a pass-or-fail toast.

    An Xray Cloud API key is tied to a Jira account, so it can authenticate perfectly and still see none of your tests. Settings → Integrations → Xray now reads back a sample after "Test connection": instance URL, response time, and up to five tests with their Jira keys, summaries and folders.

    That makes it obvious whether the connection reaches the right project before you start pulling cases into chat.

    # 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