Cursor launches Rollouts, an agent that writes a monitoring plan on every PR and reports change health per environment

A team that uses a coding agent has, over the past year, cut the time it takes to write a change from days to minutes, while the time to know whether the change broke something in production has stayed the same. Cursor's Rollouts changelog on 2026-09-23 is the company's first product answer to that gap: an agent that watches every change as it deploys and reports change health per environment. Paul Sawers at The New Stack wrote up the launch on 2026-09-24 and covered the acquisition history behind it.

What Rollouts does on a pull request

Cursor's own changelog describes the flow. When a pull request opens, Rollouts reads the diff and the systems it touches, then writes a monitoring plan as a PR comment. The plan names the risks it identified, the effect the change is meant to have, the signals it will check, and any gaps in instrumentation that would make the change hard to verify. A developer can edit the plan in the PR and Rollouts uses that version.

After the change is deployed, Rollouts runs the plan against the team's logs, metrics and traces, and tracks each environment on its own. Cursor says a change "can be verified in staging and still flagged in production". Every deploy gets one of three verdicts: verified healthy, regression detected, or inconclusive.

What happens when it flags a regression

When Rollouts detects a regression, it names the change it suspects and notifies the author. Depending on how it is configured, it can also open a revert pull request for review, or hand the finding to a Cursor cloud agent to attempt a fix. Cursor's changelog is explicit that Rollouts "does not merge or roll back on its own today", so a person still owns the merge decision.

The Firetiger co-founder Rustam Lalkaka, now at Cursor after the acquisition The New Stack reports Cursor announced last month, gave the reasoning in the launch post Sawers quotes: "Writing code is no longer the slow part. What hasn't sped up is everything after the PR goes up: making sure code is secure, watching the deploy, deciding whether a latency bump is real, figuring out which of eleven changes broke checkout."

Integrations, and what the launch says about Cursor's direction

Rollouts connects to Cursor's own Origin repository host or GitHub for source control, to a team's continuous delivery system for deploy events, and to Datadog and other telemetry providers for signals. Feature flag integration is listed as coming soon. Both Rollouts and an upgraded Security Review bot ship today on Cursor Teams and Enterprise plans, and are built on a @cursor/bdk package the launch describes as the Bot Development Kit for defining agents in Markdown and TypeScript.

Sawers frames Rollouts as an early glimpse of Origin's product argument: the coding agent, the repository, the security check and the production feedback can sit closer together than they can when spread across GitHub, a separate deployment platform and a separate telemetry vendor. That is also the pitch Datadog's Bits Release, Harness and LaunchDarkly Guarded Rollouts each make from their own side, and this launch is the coding tool joining the argument.

Source

• Rollouts and Security Review, Cursor changelog, 2026-09-23
• Cursor acquired Firetiger. A month later, it launched a bot that tracks code changes from PR to production., Paul Sawers, The New Stack, 2026-09-24