Release Notes - 9 November 2026

This release adds baselines for MCP monitor steps, more fields in the panel for creating a monitor, and enhancements to the API, along with bug fixes and security updates.

Added: MCP step baselines

• Mark as Expected: on an MCP monitor result, mark a step's result as expected. Later results of that step are checked against it, and differences show as Data issues on the Conformance page. You choose which parts of the result are allowed to change, such as tool descriptions.
• Accept as Expected: when a server changes on purpose, accept the new result as the baseline from the Data issue.

Updated: Creating monitors

• The Create New API Call panel now takes query parameters, headers, an auth setting and token, and a body for POST, PUT, and PATCH. If you leave the name empty, the monitor is named after the method and URL. See Add an API monitor.
• The Create MCP Monitor panel now takes an auth setting and token. See MCP monitors.

Updated: Monitor pages

On a project's performance page, the API tables list API monitors only, and the browser table shows DNS lookup, TCP connect, and SSL handshake times.

Updated: CLI sign-in

A browser or device-code login now renews itself in the background while you use the CLI. Sign in again after 3 days without using it, or 7 days after you signed in. See CLI authentication.

Updated: API

This release includes enhancements and improvements to the API. See the API reference.

Bug fixes, enhancements, and improvements

This release includes various bug fixes, enhancements, and improvements across the platform.

Security updates

This release includes security updates.