CursorEngineering PostOfficial Source

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 · Sep 23, 2026

Open Source Open Markdown Open JSON

Source Summary

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.

Practical Implication

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.

Agent-Ready Context

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.

Connected Context · Feed7 Judgment

This turns Cursor’s proposed production loop into two concrete, review-oriented controls spanning pre-merge security and post-merge behavior. It confirms telemetry-backed monitoring as part of coding-agent reliability, but keeps authority bounded through reviewable plans and conservative responses; missing accuracy data and forthcoming release controls prevent treating either bot as an autonomous gate.

Firetiger joins CursorRollouts is a concrete realization of the previously announced Firetiger direction, moving from an upcoming monitoring concept to a product with baseline creation, monitoring plans, and configurable regression responses.PostHog/posthogPostHog’s telemetry-to-diagnosis path provides the broader observability pattern that Rollouts operationalizes around individual changes from PR through production.Distributed Attacks in Persistent-State AI ControlDistributed attacks across multiple PRs expose a limit of per-PR security review; whole-codebase context may broaden each inspection, but the supplied material does not show that Security Reviewer detects persistent multi-PR attacks.LLM Agents Can Easily Tamper With Their Own TracesBecause Rollouts depends on deployment and telemetry evidence, trace-tampering results make independently captured, agent-inaccessible monitoring data an important prerequisite for trustworthy automated responses.

Context Map

toolscodingsecurity#coding-agents#agent-reliability#observability

Uncertainty

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.