Todos for everyone, custom environment headers, and Slack in chat

Highlight
Featured this release
Chat can read and post to Slack
Opt in and the agent can browse channels, read threads and post updates, screenshots included.
Turn on "Enable Slack Tools in Chat" under the project's Slack integration and chat gains tools to list public channels, read messages and threads, and post rich updates with images and files attached.

Off by default – existing Slack integrations are unaffected until you opt in. You may need to reconnect Slack to grant the additional permissions.

More on this: the Slack integration.
# Direct link
Highlight
Featured this release
Custom HTTP headers for environments
Set per-environment header rules, like a preview protection-bypass token, and every run sends them.
In environment settings, add name and value header rules scoped to a domain pattern, for example *.preview.example.com. Matching requests from the browser, crawler and API sandbox include them automatically – handy for bypassing preview-deployment protection or attaching auth tokens.

Rules can also be set from the Start Run API or a GitHub Action configuration, and they persist across runs until explicitly cleared.

More on this: preview protection bypass and multi-environment testing.
# Direct link
Highlight
Featured this release
Todos is now on for every organization
Todos leaves early access, splits into Focus and More, and each item leads with a way to solve it.
Every organization now sees Todos in the project nav, chat and command palette – no invite needed.

The list splits into two views with the same filter pills as Pull Requests: Focus holds todos that recurred four or more times in the last 30 days, More holds everything else recent, and hovering either pill explains the rule.

Each todo's detail page now opens with a Recommended Next Step – Solve in Chat, or Complete With Cursor or Claude – instead of a generic settings link.

More on this: testing AI-generated code and how to audit your QA process.
# Direct link
Update 04 of 06
Store API keys as a dedicated config type
Configs now have an API Key type, masked everywhere in the UI and passed to tests as a variable.
Under Settings → Configs → Add config, choose API Key to store a secret without folding it into Custom Fields. The value stays masked in the dashboard and in chat, and API tests can reference it as an environment variable.

More on this: API testing and API contract testing.
# Direct link
Update 05 of 06
Copy assistant replies in chat
A copy icon appears under finished assistant messages so you can grab the text in one click.
Once an assistant message finishes, a copy icon appears next to the feedback buttons. Click it to copy the reply's text – tool calls and reasoning are excluded – and the icon turns into a checkmark to confirm.

More on this: what QA.tech does.
# Direct link
Update 06 of 06
Re-run the PR review agent on demand
A menu action starts the post-merge review agent manually from any pull request.
From a project's Pull Requests list, a pull request's detail page, its kebab menu or Cmd+K, choose "Run post-merge agent" to trigger a review on demand. Running it on a pull request that has not merged yet asks for confirmation first, and a toast with a "View conversation" link opens the chat thread the agent posts to.

More on this: pull request testing and the GitHub integration.
# Direct link

Chat can read and post to Slack

Custom HTTP headers for environments

Todos is now on for every organization

Store API keys as a dedicated config type

Copy assistant replies in chat

Re-run the PR review agent on demand

Your team moves fast. Can your testing keep up?