# Bots for the last mile: Rollouts, Security Review

Source: [Cursor](https://cursor.com/blog/rollouts-and-security-reviewer)  
Feed7 permalink: https://feed7.dev/p/rollouts-and-security-reviewer-015uvdo  
Published: 2026-09-23T12:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

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.

## 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 across 875 accumulated Signals:

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 Cursor](https://feed7.dev/p/firetiger-06hv2bc) — Rollouts 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/posthog](https://feed7.dev/p/posthog-1dwbj56) — PostHog’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 Control](https://feed7.dev/p/2607-02514v1-02bqscm) — Distributed 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 Traces](https://feed7.dev/p/2609-30266v1-1kct4j7) — Because 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

- Layer: tools
- Domains: coding, security
- Topics: 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.