Bots for the last mile: Rollouts, Security Review
Cursor added PR-to-production monitoring and codebase-aware security review, giving agent-driven teams automated checks after code generation but before and after deployment.
Cursor released **Rollouts** to monitor changes from PR through production and **Security Reviewer** to inspect every PR in whole-codebase context. Rollouts establishes a pre-deploy baseline; Security Reviewer reports severity, attack path, and a proposed fix.
Connect deployment and telemetry systems, then review Rollouts’ monitoring plan before merge. Configure regression responses conservatively—notification, rollout pause, or approval-gated revert—and treat security fixes as reviewable patches rather than automatic truth.
Cursor released **Rollouts** to monitor changes from PR through production and **Security Reviewer** to inspect every PR in whole-codebase context. Rollouts establishes a pre-deploy baseline; Security Reviewer reports severity, attack path, and a proposed fix. Connect deployment and telemetry systems, then review Rollouts’ monitoring plan before merge. Configure regression responses conservatively—notification, rollout pause, or approval-gated revert—and treat security fixes as reviewable patches rather than automatic truth. Both bots are limited to **Teams and Enterprise** plans. Feature-flag traffic control, release-train awareness, and deploy-freeze awareness are still forthcoming, and the post provides no measured accuracy or false-positive rates.
This turns Cursor’s proposed code-to-production loop into two shipping controls: pre-merge whole-codebase security review and post-merge regression monitoring with bounded response options. It strengthens the case for continuous verification, but absent accuracy data, independent trace guarantees, and cross-PR attack handling, neither bot should become an unquestioned merge or rollback authority.