# List runs via MCP, typed tool schemas, mobile test cases, and API key labels

> 11 updates: PR review bot keeps one comment per pull request, Test Cases page works on mobile, Agents can list runs via MCP and API, Chat assistant…

Source: https://qa.tech/changelog/2026-06-02

---
11 updates shipped on June 2, 2026.

In this release

1.  01[PR review bot keeps one comment per pull request](#2026-06-02-pr-review-bot-sticky-comment)Highlight
2.  02[Test Cases page works on mobile](#2026-06-02-test-cases-page-works-on-mobile)Highlight
3.  03[Agents can list runs via MCP and API](#2026-06-02-agents-list-runs-via-mcp-and-api)
4.  04[Chat assistant explains when file downloads aren't possible](#2026-06-02-chat-assistant-file-downloads-clarity)
5.  05[MCP tools now expose typed schemas for all parameters](#2026-06-02-mcp-tools-typed-parameter-schemas)
6.  06[Name your API keys](#2026-06-02-name-your-api-keys)
7.  07[Network settings shows the correct outbound IPs URL](#2026-06-02-network-settings-outbound-ips-url)
8.  08[Personal API keys](#2026-06-02-personal-api-keys)
9.  09[Tighter PR review status comment handling](#2026-06-02-pr-review-status-comment-dedupe)
10.  10[Sign-up page is faster](#2026-06-02-signup-page-faster)
11.  11[Simpler sign-up when arriving from a shared link](#2026-06-02-simpler-signup-from-shared-links)

1.  Highlight
    
    Featured this release
    
    ## PR review bot keeps one comment per pull request
    
    The review bot now edits a single sticky comment in place rather than posting a new comment on every round.
    
    Previously, each review round – queued, running, result – added a fresh comment to your pull request. The bot now maintains one comment per PR and updates it as the run progresses, with a collapsible history of earlier rounds at the bottom. The GitHub review verdict (approve, request changes, or comment) is still posted as a separate review object and links back to the sticky comment.
    
    [\# Direct link](#2026-06-02-pr-review-bot-sticky-comment)
    
2.  Highlight
    
    Featured this release
    
    ## Test Cases page works on mobile
    
    The scenario tree and test list are now usable on phones – no horizontal scrolling and menus are always reachable on touch.
    
    On narrow screens, the scenario tree slides in as a sheet triggered by a selector button instead of squeezing into a thin sidebar. The table fills the full width, drops columns that don't fit, and moves last-run history directly under the test name so it stays visible. The row options menu is always visible on mobile – previously it was hidden behind hover and never appeared on touch devices.
    
    [\# Direct link](#2026-06-02-test-cases-page-works-on-mobile)
    
3.  Update 03 of 11
    
    ## Agents can list runs via MCP and API
    
    A new list\_runs MCP tool and GET /v1/run endpoint let agents query runs by app, plan, status, branch, or date range – no human lookup required.
    
    `list_runs` is now available in the QA.tech MCP, letting agents query runs by application, test plan, status, trigger, branch, commit hash, and time window. It returns shortIds that feed directly into `get_run` and `rerun_run`, which previously required a human to paste a run ID. A matching `GET /v1/run` endpoint is also available in the public API.
    
    [\# Direct link](#2026-06-02-agents-list-runs-via-mcp-and-api)
    
4.  Update 04 of 11
    
    ## Chat assistant explains when file downloads aren't possible
    
    The assistant tells you clearly when a request isn't supported, instead of attempting it and running into limits.
    
    When asked to produce a CSV export or other file download, the chat assistant previously tried to work around the limitation – sometimes producing chunked output or stopping mid-way through a large result. It now tells you upfront that file downloads and attachments aren't supported in the chat surface, and offers inline tables or short summaries as an alternative where they fit.
    
    [\# Direct link](#2026-06-02-chat-assistant-file-downloads-clarity)
    
5.  Update 05 of 11
    
    ## MCP tools now expose typed schemas for all parameters
    
    start\_run, append\_chat\_message, and the mobile build upload flow are now self-describing – agents can build correct payloads from the schemas alone.
    
    `start_run` and `append_chat_message` previously exposed `applications`, `notifications`, and `applicationOverrides` as opaque arrays. They now carry full typed schemas matching the tool contract. The two-step mobile build upload (`application_build_upload_url` → HTTP PUT → `create_application_build`) is documented in both tool descriptions with cross-references, and the upload-URL response includes a `nextStep` hint pointing to the next call.
    
    [\# Direct link](#2026-06-02-mcp-tools-typed-parameter-schemas)
    
6.  Update 06 of 11
    
    ## Name your API keys
    
    You can now give each API key a label so it's easy to tell them apart.
    
    API keys in Settings now have an optional name field. Set a name when you create a key, or edit any existing key to label it – handy when you're managing separate keys for different environments or integrations.
    
    [\# Direct link](#2026-06-02-name-your-api-keys)
    
7.  Update 07 of 11
    
    ## Network settings shows the correct outbound IPs URL
    
    Settings → Network now links to https://api.qa.tech/v1/outbound-ips instead of the old path.
    
    Settings → Network now links to `https://api.qa.tech/v1/outbound-ips` instead of the old path.
    
    [\# Direct link](#2026-06-02-network-settings-outbound-ips-url)
    
8.  Update 08 of 11
    
    ## Personal API keys
    
    You can now create and manage your own personal API keys from the dashboard.
    
    The Settings → API keys page now lets individual team members generate personal API keys in addition to any project-level keys. Personal keys are scoped to your account, shown once at creation time, and can be revoked from the same page.
    
    [\# Direct link](#2026-06-02-personal-api-keys)
    
9.  Update 09 of 11
    
    ## Tighter PR review status comment handling
    
    Each pull request now gets exactly one status comment, updated in place as runs complete.
    
    The status comment writer has been tightened so each PR gets exactly one status comment, updated in place as runs complete.
    
    [\# Direct link](#2026-06-02-pr-review-status-comment-dedupe)
    
10.  Update 10 of 11
     
     ## Sign-up page is faster
     
     An analytics timing issue that slowed the sign-up page has been resolved.
     
     Analytics tracking on the sign-up page was running synchronously and adding noticeable latency on load. Tracking now runs asynchronously, so the page renders without delay.
     
     [\# Direct link](#2026-06-02-signup-page-faster)
     
11.  Update 11 of 11
     
     ## Simpler sign-up when arriving from a shared link
     
     Visitors following a shared run or project link now see a focused sign-up form instead of the full marketing layout.
     
     When an unauthenticated visitor opens a shared link (a `/p/…` URL) and reaches the sign-up page, the page now shows a streamlined layout with just the form. Testimonials and marketing content are omitted. The full layout is unchanged for direct visits.
     
     [\# Direct link](#2026-06-02-simpler-signup-from-shared-links)
     

## 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