Cursor added Rollouts and Security Review pull request bots for Teams and Enterprise

Archive entry: this covers an event from September 23, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On September 23, 2026, Cursor added two bots for pull requests, Rollouts and Security Review, as described in Cursor's blog post on the two bots. Both bots were limited to the Teams and Enterprise plans.

What the bots did

• Rollouts: watched each pull request as it deployed and labeled each environment 'verified healthy', 'regression detected' or 'inconclusive'.
• Rollouts connections: it connected to Origin or GitHub, to the deploy system and to telemetry tools such as Datadog, and at launch it did not merge or revert on its own.
• Security Review: posted one comment per pull request flagging exploitable bugs such as injection, auth bypasses, committed secrets, SSRF and risky dependency updates.
• Scope: style issues were left to Bugbot.
• Setup: both bots were turned on in the automations section.

What it meant for builders

Teams that shipped agent-written code in Cursor got automated deploy verification and security checks on every pull request. Rollouts covered the stage after a change deployed, while Security Review commented on the pull request itself.

Availability and sources

For a limited 10-day period at launch, usage credits covered roughly 50 changes on Teams and 500 on Enterprise. The Cursor changelog entry carries the same date as the blog post.

Sources

• Bots for the last mile: Rollouts, Security Review (Cursor, September 23, 2026, official)
• Rollouts and Security Review (Cursor, September 23, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.