Cursor's Rollouts bot watches your PRs from merge to production
Built on newly-acquired Firetiger tech, it flags regressions and can open reverts; a Security Review bot hunts exploitable bugs on every PR. Teams/Enterprise.
Copy markdown
Rollouts: your deploys get a verdict, not a prayer
Cursor's new Rollouts bot reads a PR's diff, writes a monitoring plan, then watches the change ship across staging and production and returns one of three verdicts: verified healthy, regression detected, or inconclusive. On a regression it can ping you, open a revert PR, or hand the fix to a Cursor cloud agent — humans still own the actual deploy. It wires into GitHub, Cursor's Origin, and telemetry providers like Datadog.
Security Review reads every PR for exploitable bugs
A companion bot reviews each pull request in full-codebase context and posts one comment flagging real vulnerabilities — SQL and command injection, auth bypasses, credential leaks, SSRF, unsafe deserialization, and risky dependencies — each with a severity rating and a proposed fix. Teams can layer on custom security rules for their own repo.
Why now: Cursor bought Firetiger a month ago
Rollouts is Firetiger's 'Change Monitors' rebuilt inside Cursor on a new Bot Development Kit, following the acquisition that brought co-founder Rustam Lalkaka aboard. His framing: 'Writing code is no longer the slow part. What hasn't sped up is everything after the PR goes up.' Both bots are Teams and Enterprise only, with free trial credits (~50 changes for Teams, ~500 for Enterprise) for the first 10 days.
Elsewhere: Gemini CLI now asks before touching your build files
Gemini CLI v0.61.0 (Sept 24) hardens against indirect prompt injection — untrusted repo content can no longer silently rewrite build files or slip in untrusted flags — and tightens filesystem isolation in the sandbox. If you point the CLI at repos you don't fully trust, update now.