# Automations from MCP and the API, domain-scoped basic auth, and knowledge file uploads > 5 updates: Set up automations from MCP, the API and chat, Domain-scoped basic auth for environments, New docs: the regression review agent, PR reviews… Source: https://qa.tech/changelog/2026-10-14 --- 5 updates shipped on October 14, 2026. In this release 1. 01[Set up automations from MCP, the API and chat](#2026-10-14-automations-from-mcp-api-and-chat)Highlight 2. 02[Domain-scoped basic auth for environments](#2026-10-14-domain-scoped-basic-auth-for-environments)Highlight 3. 03[New docs: the regression review agent](#2026-10-14-docs-regression-review-agent) 4. 04[PR reviews list follow-up todos](#2026-10-14-pr-reviews-list-follow-up-todos) 5. 05[Upload files to your knowledge library](#2026-10-14-upload-files-to-knowledge-library) 1. Highlight Featured this release ## Set up automations from MCP, the API and chat Agents can list, create, update, delete and trigger automations through MCP, the public API and the in-app chat. MCP clients get five new tools: `list_automations`, `create_automation`, `update_automation`, `delete_automation` and `trigger_automation`. The same actions are available over the public API at `/v1/automations`. The in-app chat assistant can create, edit, pause, run and delete automations, and shows each schedule in plain language with its last few runs. Pausing an automation clears its next run, and resuming schedules the next run from that moment. One-time schedules use a pinned cron expression like `30 9 14 10 *`. More on this: [MCP](https://qa.tech/product/mcp), [API testing](https://qa.tech/product/api-testing) and [smoke testing](https://qa.tech/use-cases/smoke-testing). [\# Direct link](#2026-10-14-automations-from-mcp-api-and-chat) 2. Highlight Featured this release ## Domain-scoped basic auth for environments Protect staging and preview sites with HTTP Basic Auth rules that QA.tech applies only to the domains you choose. Add one or more rules – domains, username, password – to an environment, and QA.tech sends basic auth only to matching hosts, with `*.example.com` wildcards supported. Set rules in the environment form or as a default for Preview Environments; saved passwords are write-only and show as "Stored password". Rules apply to [AI testing](https://qa.tech/) in the browser, API tests and the crawler, and carry through preview creation and promotion. CI integrations and the public API accept a `basicAuth` field on environment overrides, and the chat agent can create and update environments with basic auth. The existing "Use for Basic Auth" checkbox and `user:pass@` URLs keep working. More on this: [multi-environment testing](https://qa.tech/use-cases/multi-environment-testing), [authentication testing](https://qa.tech/use-cases/authentication-testing) and [integrations](https://qa.tech/product/integrations). [\# Direct link](#2026-10-14-domain-scoped-basic-auth-for-environments) 3. Update 03 of 05 ## New docs: the regression review agent A new docs page explains how QA.tech reviews test plan results and what each verdict means. The "Regression review agent" page under Regression Testing in the docs covers what gets a review (test plans started from Run Tests, schedules, CI or the API), how the agent investigates failures and reruns tests to check its hypotheses, and how verdicts are grouped: Issues, Setup – not a code bug, Flaky – passed on retry, and Tests to update. It also shows where the review appears and how to start one yourself with `/regression` in chat. More on this: [docs](https://docs.qa.tech) and [regression testing](https://qa.tech/use-cases/automated-regression-testing). [\# Direct link](#2026-10-14-docs-regression-review-agent) 4. Update 04 of 05 ## PR reviews list follow-up todos Review comments show each open todo for the pull request as a tip under the verdict. The review agent now files follow-ups it finds during a pull request review and shows them as a tip under the verdict, marked "after merge". In the todo detail they carry an "Awaiting merge" badge. When the PR merges, the post-merge review keeps or drops each one; if the PR closes without merging, pending todos are dropped. More on this: [PR testing](https://qa.tech/product/pr-testing) and [shift-left testing](https://qa.tech/use-cases/shift-left-testing). [\# Direct link](#2026-10-14-pr-reviews-list-follow-up-todos) 5. Update 05 of 05 ## Upload files to your knowledge library Add Markdown, text, CSV, JSON, YAML and PDF files to the knowledge library, or ask the chat agent to add one. Under Add Knowledge there's a new "Upload Files" option next to Web Link and Text Content. Drop in several files at once, and each becomes its own library item with an editable title. Supported types are `.md`, `.txt`, `.csv`, `.json`, `.yaml`/`.yml` and `.pdf` – text files up to 5 MB, PDFs up to 100 MB. You can also attach a file in chat and ask the agent to add it to the library. It starts indexing right away, and the agent can then read added PDFs when it answers questions. More on this: [product overview](https://qa.tech/product), [file upload testing](https://qa.tech/use-cases/file-upload-export-testing) and [AI test generation](https://qa.tech/use-cases/ai-test-generation). [\# Direct link](#2026-10-14-upload-files-to-knowledge-library) ## 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