# Automations, on-demand PR reviews, and compactable conversations

> 5 updates: Automations: schedule test runs and chat workflows, Chat agent can research sibling repositories, Chat conversations report status and linked…

Source: https://qa.tech/changelog/2026-09-09

---
5 updates shipped on September 9, 2026.

In this release

1.  01[Automations: schedule test runs and chat workflows](#2026-09-09-automations-scheduled-runs-and-workflows)Highlight
2.  02[Chat agent can research sibling repositories](#2026-09-09-chat-agent-researches-sibling-repositories)
3.  03[Chat conversations report status and linked runs](#2026-09-09-chat-conversations-report-status-and-runs)
4.  04[Compact long conversations with /compact](#2026-09-09-compact-long-conversations)
5.  05[Test editor remembers your Environment and Device](#2026-09-09-test-editor-remembers-environment-and-device)

1.  Highlight
    
    Featured this release
    
    ## Automations: schedule test runs and chat workflows
    
    Project Settings now runs your chat workflows or test plans on a schedule, via the API, or on demand.
    
    Create an automation under Project Settings → Automations for an AI Assistant (chat) action or a Run Test Plan action, then set it to fire hourly, daily, weekly, monthly or once, in your project's timezone.
    
    Run Now fires immediately, even while an automation is paused, and any automation can be triggered from the public [API](https://docs.qa.tech/api-reference/introduction). A nested History view links each run back to its conversation or test result.
    
    More on this: [smoke testing](https://qa.tech/use-cases/smoke-testing) and [automated regression testing](https://qa.tech/use-cases/automated-regression-testing).
    
    [\# Direct link](#2026-09-09-automations-scheduled-runs-and-workflows)
    
2.  Update 02 of 05
    
    ## Chat agent can research sibling repositories
    
    The codebase tool can look at any repository your GitHub connection can reach.
    
    Mention a sibling repository by name or paste its GitHub URL and the chat agent's codebase tool explores that repository instead of only the one mapped to your project. The agent run card shows which repository it looked at.
    
    Code access still needs to be enabled on a [GitHub](https://docs.qa.tech/integrations/github) mapping, and that mapping's installation determines which repositories are reachable.
    
    More on this: the [GitHub integration](https://qa.tech/product/integrations/github) and [AI test generation](https://qa.tech/use-cases/ai-test-generation).
    
    [\# Direct link](#2026-09-09-chat-agent-researches-sibling-repositories)
    
3.  Update 03 of 05
    
    ## Chat conversations report status and linked runs
    
    Conversations started over the API or MCP expose a status field and their linked runs.
    
    Conversations started through the public [API](https://docs.qa.tech/api-reference/introduction) or [MCP](https://docs.qa.tech/integrations/mcp) now return a status – in progress, completed, failed or cancelled – along with a list of runs carrying each run's short ID, status and result.
    
    Poll the conversation until its status is terminal, then fetch the run to see the outcome, instead of guessing when a result is ready.
    
    More on this: [the QA.tech MCP server](https://qa.tech/product/mcp) and the [CI/CD API integration](https://qa.tech/product/integrations/cicd-api).
    
    [\# Direct link](#2026-09-09-chat-conversations-report-status-and-runs)
    
4.  Update 04 of 05
    
    ## Compact long conversations with /compact
    
    A /compact command condenses a long conversation, with a context-usage indicator in the composer.
    
    Type `/compact` in the chat composer to condense a long conversation into a fresh, smaller context, optionally with a short note describing what to keep.
    
    A context-usage indicator in the composer shows how much of the conversation window you have used, and compacted conversations persist so the summary survives a refresh.
    
    More on this: [what QA.tech does](https://qa.tech/product).
    
    [\# Direct link](#2026-09-09-compact-long-conversations)
    
5.  Update 05 of 05
    
    ## Test editor remembers your Environment and Device
    
    Manual Environment and Device selections in the test editor stick between visits.
    
    Pick an Environment or Device while editing a test and QA.tech remembers it next time you open that project's editor. Opening a test from a specific run or test plan applies that run's options for the visit without overwriting your saved defaults, and override chips now show the environment name rather than a raw ID.
    
    More on this: [multi-environment testing](https://qa.tech/use-cases/multi-environment-testing) and [mobile testing](https://qa.tech/product/mobile-testing).
    
    [\# Direct link](#2026-09-09-test-editor-remembers-environment-and-device)
    

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

-   [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)
-   [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
