Back to rankings

Cursor Cloud Agent Subscriptions: Event-Driven PR and Slack Automation

CursorView original changelog

Cursor introduced Subscriptions, letting cloud agents subscribe to an event source — a pull request thread, a Slack thread, or a schedule — and wake automatically when something happens, rather than waiting for a person to re-prompt them. Cloud agents now automatically subscribe to the PRs they open and drive them to completion, fixing CI failures and responding to bot review comments on their own. In Slack, users can ask @cursor to check back periodically and keep working until feedback lands. The feature is available for cloud agents only, for now.

Key Takeaways

  • Cloud agents can now stay attached to a task after the initial run, subscribing to a PR or Slack thread and waking automatically when new activity appears.
  • PRs opened by an agent are now self-driving, with the agent automatically fixing CI failures and responding to bot review comments until the PR is ready.
  • Slack becomes a control surface for long-running work, letting users tell an agent to "check back" on a delay and keep iterating until feedback is resolved.
  • Subscriptions are currently cloud-agent-only, so IDE/local agents don't yet get this always-on behavior.
  • This shifts Cursor's cloud agents from single-shot task runners toward persistent, event-reactive collaborators, reducing the need to manually re-prompt after every CI failure or review comment.
  • The feature builds on Cursor's existing cloud agent infrastructure (introduced with cloud environments and cloud subagents in June 2026), extending it with autonomous re-engagement rather than just remote execution.

Agents that wake themselves up

Cursor introduced Subscriptions, a new way for cloud agents to stay attached to a piece of work without a person needing to keep re-triggering them. Instead of running once and stopping, a cloud agent can now subscribe to an event source — a specific thread or conversation — and wake up automatically the moment something relevant happens there.

This is part of a broader push described in the release: Cursor's cloud agents and harness are being built so that "always-on agents can operate as a system," picking up work in response to events and staying on course through long-running sessions without intervention at every step.

PR-driven automation

The most immediate application is pull requests. Cloud agents that open a PR now automatically subscribe to it. From there, the agent keeps working the PR through to completion — fixing failing CI runs and addressing comments left by review bots — without a developer needing to paste the failure back into a fresh chat. This closes a common gap in AI-assisted PR workflows, where an agent produces a first draft but a human still has to babysit CI and review threads afterward.

Slack integration

Subscriptions also extend into Slack. A user can ask the agent directly in a thread, for example: @cursor check back in an hour and keep going until that feedback is in. Cursor will hold that subscription open and re-engage with the thread on the schedule or trigger described, rather than requiring the user to manually re-invoke it.

Cursor notes that subscriptions are currently limited to cloud agents; local/IDE agents don't yet support this event-driven wake-up behavior.