October 2, 2026
From post-deploy failure to a one-click fix: Cursor Rollouts launches an agent from an issue
Rollouts links a failure after deployment to a suspected PR, and the Fix issue button lets you assign the fix to an AI agent.
Cursor
@cursor_ai
When Rollouts detects a regression, it finds the PR that caused it and opens an issue. One click launches a cloud agent to fix it. Rollouts usage credits are included through Oct 3.
Introducing Rollouts. Rollouts write a monitoring plan, then watch changes as they deploy. Deployments are verified, so regressions are caught before users see them.
· 15.1K views
Rollouts detects performance degradation after deployment, opens an issue and notifies the author of the change. The Fix issue button launches a cloud agent to fix it.
On Sep 23, Cursor launched Rollouts to check deployments. Now a detected issue can lead directly to agent work. Rollouts creates its own monitoring plan and compares metrics after deployment with their pre-deployment baseline.
How to enable it. In Cursor, open Automations → From Cursor → the Rollouts card → Enable. Then select repositories and configure deployment events, telemetry and notifications. You need at least 1 telemetry tool, such as Datadog: without it, changes remain Pending and Rollouts cannot detect regressions.
To connect CI, create an API key and save it as the CURSOR_API_KEY secret. The setup agent can open a PR with calls marking the start and end of a deployment. Merge this PR to finish the setup.
Rollouts supports up to 200 repositories. You can connect:
- Origin. - GitHub. - GitLab.com. - Bitbucket Cloud.
What Rollouts checks. The service monitors staging and production separately. Checks run immediately after deployment, then after 20 minutes, 1 hour, 1 day and 3 days. According to Cursor, Rollouts detects performance degradation at a single endpoint in one region before a global alert fires.
You can adjust the monitoring plan in a PR. Mention the handle from the Rollouts comment and specify what to track or ignore. You need write access to the repository.
Availability and pricing as of Oct 2, 2026:
- Teams: $40 per user per month. - Enterprise: custom pricing. - At launch on Sep 23, Cursor provided Rollouts credits for 10 days, covering roughly 50 changes for Teams and 500 for Enterprise.
Primary sources: Cursor documentation and pricing dated Oct 2, 2026, and Cursor's changelog and blog dated Sep 23, 2026.
Rollouts usage credits are included through Oct 3, 2026.
Source
