Skip to content
NewsProduct launch

Cursor Cloud Agents can now monitor GitHub PRs and Slack threads and resume work without manual re-invocation

· by Pondero Newsdesk

The short version

Cursor's August 19 changelog adds event-driven subscriptions, isolated subagent virtual machines, a /goal command for multi-session tasks, and custom always-on skill modes to cloud agents. Local agents are not included at launch.

Cursor Cloud Agents can now monitor GitHub PRs and Slack threads and resume work without manual re-invocation

Six weeks after SpaceX closed its $60 billion Cursor acquisition, Cursor published a changelog on August 19 adding five capabilities to cloud agents: event-driven subscriptions that wake agents when something changes in a PR or Slack thread, isolated subagent virtual machines, a /goal command for long-lived objectives, custom always-on skill modes, and steering messages that redirect a running agent without cutting it off mid-action. None of the five features extend to local agents yet.

What

The headline feature is Subscriptions, per the Cursor changelog. A cloud agent can now monitor a GitHub pull request thread, a Slack channel, or a scheduled timer and resume work automatically when something happens. An agent that opens a PR subscribes to it automatically and drives it to completion: the agent fixes failing CI checks and addresses bot-review comments without waiting for a user to re-invoke it. In Slack, a user can tell @cursor to "check back in an hour and keep going until that feedback is in" and the agent will do so.

Custom Modes let users pin any saved skill as a persistent instruction set for every interaction in a session. Activating a mode requires selecting a skill from the / menu and pressing Alt+Enter. Skills pinned this way act as always-active playbooks rather than one-off invocations.

Subagents can now run on their own isolated virtual machines. Each subagent gets a clean copy of the project repository with its own cloud environment, eliminating file-system and build-artifact collisions when multiple subagents run against the same codebase in parallel. The changelog gives a sample prompt: "run a swarm of subagents to test my app for bugs, each in its own environment."

/goal accepts a long-lived objective and keeps the agent working toward it until the task is fully complete. Pairing /goal with a custom mode runs every step of a multi-stage task against the same skill playbook. Pairing it with /loop triggers recurring check-ins.

Steering improvements let users send a follow-up message to a running agent without stopping it. Follow-ups queue behind the agent's current tool call and arrive at the next natural pause rather than cutting it off mid-action.

Why it matters

The subscription model addresses a friction point that teams running AI agents on live codebases hit regularly: an agent finishes its current context, stops, and requires a human to check on results and manually re-invoke it for the next step. For PR-heavy workflows, that cycle repeats with every round of review or CI failure. Subscriptions remove the re-invocation loop for those specific event types, shifting cloud agents from task-mode tools into longer-running autonomous workers.

Isolated subagent VMs matter most to teams experimenting with parallel agent patterns. Without environment isolation, subagents running concurrently on the same repository can clobber each other's changes or produce non-deterministic build results. Clean-slate VMs per subagent make those parallel runs reproducible.

All five capabilities are cloud-agent-only. Teams on local-agent plans see no change. Cursor has not published separate pricing for subscriptions; the existing cloud-agent plan pricing applies.

What to watch next

The most immediate open question is whether subscriptions and subagent VMs extend to local agents. The changelog notes "Subscriptions are available for cloud agents only, for now," leaving the door open but giving no timeline. SpaceX officially closed its $60 billion Cursor acquisition on August 14, per TechCrunch, and this changelog is the first major product release since the close. The next changelog entry will clarify whether SpaceX's GPU infrastructure is already shaping the roadmap or whether the current features were already in flight before the acquisition finalized.

Sources