# A chat agent that reads your test inbox, PR triage for API reviews, and cache-free runs

> 3 updates: The chat agent can read your test inbox, PR triage applies to API and GitHub Action reviews, Run without the agent cache from the API and MCP

Source: https://qa.tech/changelog/2026-10-12

---
3 updates shipped on October 12, 2026.

In this release

1.  01[The chat agent can read your test inbox](#2026-10-12-chat-agent-reads-your-test-inbox)Highlight
2.  02[PR triage applies to API and GitHub Action reviews](#2026-10-12-pr-triage-for-api-and-github-action-reviews)
3.  03[Run without the agent cache from the API and MCP](#2026-10-12-run-without-agent-cache-from-api-and-mcp)

1.  Highlight
    
    Featured this release
    
    ## The chat agent can read your test inbox
    
    Chat and PR reviews can look at the emails and SMS a test received, so email failures get a real answer.
    
    Three new chat tools let the agent search the project inbox, open a specific email – readable body, every link with its anchor text, and attachment info – and list SMS messages. Scoped to a test, they show which messages went to that test's addresses and whether one arrived after the test had already moved on.
    
    For [AI QA testing](https://qa.tech/) of sign-up and login flows, the PR review bot uses the same tools to tell a slow delivery or a test-side misread apart from a real app bug when an email test fails.
    
    More on this: [authentication testing](https://qa.tech/use-cases/authentication-testing), [notifications testing](https://qa.tech/use-cases/notifications-testing) and [PR testing](https://qa.tech/product/pr-testing).
    
    [\# Direct link](#2026-10-12-chat-agent-reads-your-test-inbox)
    
2.  Update 02 of 03
    
    ## PR triage applies to API and GitHub Action reviews
    
    Reviews started through the API or the GitHub Action follow your PR Triage setting, with an optional per-review override.
    
    Change reviews started with `POST /v1/chat/change-review` or the GitHub Action now follow your repository's PR Triage toggle and prompt, the same as mentions and "Start review". A skipped review shows up as a skipped `QA.tech / PR Review` check with a short summary.
    
    To override a single review, send an optional `triage` object: `triage.enabled` (`false` to never skip, `true` to allow a skip even when the toggle is off) and `triage.prompt` (up to 4,000 characters) to replace the triage prompt for that review only.
    
    More on this: [PR testing](https://qa.tech/product/pr-testing) and [PR and CI/CD testing](https://qa.tech/use-cases/pr-cicd-testing).
    
    [\# Direct link](#2026-10-12-pr-triage-for-api-and-github-action-reviews)
    
3.  Update 03 of 03
    
    ## Run without the agent cache from the API and MCP
    
    Runs and reruns started from the API or MCP accept a flag that skips Agent Cache for every test in the run.
    
    Pass `"skipAgentCache": true` to `POST /v1/run` or `POST /v1/run/{shortId}` (rerun), or to the `start_run_with_test_cases`, `start_run_with_test_plan` and `rerun_run` MCP tools, to run every test in that run without Agent Cache. It's a quick way to check whether a flaky test is a cache problem, without unticking the setting test by test. Omitting it or sending `false` keeps each test's own setting.
    
    More on this: [MCP](https://qa.tech/product/mcp), [API testing](https://qa.tech/product/api-testing) and [PR and CI/CD testing](https://qa.tech/use-cases/pr-cicd-testing).
    
    [\# Direct link](#2026-10-12-run-without-agent-cache-from-api-and-mcp)
    

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

[Book a technical session](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)](https://trust.qa.tech/)

### Product

-   [API Testing](https://qa.tech/product/api-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [Voice Testing](https://qa.tech/product/voice-testing)
-   [Web Testing](https://qa.tech/product/web-testing)

-   [AI QA testing guide](https://qa.tech/ai-qa-testing)
-   [Changelog](https://qa.tech/changelog)
-   [Integrations](https://qa.tech/product/integrations)
-   [Platform overview](https://qa.tech/product)
-   [Use cases](https://qa.tech/use-cases)

### Compare

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

-   [B2B SaaS testing](https://qa.tech/saas)
-   [Ecommerce testing](https://qa.tech/industries/ecommerce)
-   [For CTOs](https://qa.tech/solutions/ctos)
-   [For QA teams](https://qa.tech/solutions/qa-testers)

### 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)
-   [Trust Center: Security & Compliance](https://trust.qa.tech/)

### Social

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

© 2026 QA.tech. All rights reserved
