Cursor launches Rollouts and Security Review bots on September 23 for post-deploy monitoring and PR security review
Cursor launched Rollouts and Security Review bots on Teams and Enterprise plans on September 23, with launch credits covering roughly 50 changes for Teams and 500 for Enterprise for ten days.
On September 23, Cursor launched Rollouts and Security Review bots on Teams and Enterprise plans. Rollouts attaches a monitor to every PR, watches changes as they deploy, and reports one of three verdicts per environment: verified healthy, regression detected, or inconclusive. When a PR opens, Rollouts reads the diff and the systems it touches, then publishes a monitoring plan as a PR comment that engineers can edit in-place, with edits becoming the working baseline. Rollouts does not merge or roll back on its own today, but on a regression it can notify the author, open a revert PR for review, or hand the finding to a cloud agent.
Security Review reads every PR in codebase context and posts a single review comment focused on exploitable bugs, covering SQL/command/template injection, authn and authz bypasses, secrets committed to source, SSRF and unvalidated redirects, unsafe deserialization, and dependency changes that introduce known vulnerabilities. Draft PRs are skipped to avoid noise. Style and quality stay with Bugbot.
Both bots are enabled via the Automations dashboard. Rollouts needs source control (GitHub or Origin), a continuous-delivery system, and a telemetry source such as Datadog. For ten days from launch, Cursor includes usage credits covering roughly 50 changes for Teams and 500 for Enterprise.