Cursor expands Cloud Agents with event triggers, goals, and browser previews

Cursor’s late-August changelog expands Cloud Agents from one-off runs toward longer-lived, event-driven development workflows. The update says agents can respond to events, hold a goal until it is met, and keep working through long-running sessions with less manual intervention.

Event subscriptions and persistent goals

Cloud Agents can now subscribe to event sources such as pull requests, Slack threads, and scheduled tasks. When something changes, Cursor says the agent can wake up and continue the work. Subscriptions are currently available for cloud agents, so teams should treat them as an automation surface rather than a general editor trigger.

The same release adds goals that persist across a session. This is designed for work that needs multiple turns instead of a single prompt, while still leaving the developer responsible for defining the goal and reviewing the resulting changes.

Isolated subagents and better steering

Subagents can run on their own virtual machines, with an isolated copy of the project and a clean context for each environment. That separation can make parallel exploration safer, but it also means teams should understand what files, credentials, and integrations are available to each run.

Cursor also added a way to send a message while an agent is working without interrupting its current tool call. Follow-ups wait for a safe boundary, so developers can steer a run without discarding the action already in progress.

Start without GitHub, then preview in a browser

Cloud Agents no longer require a connected GitHub or other third-party source-control provider to get started. A user can choose Start from scratch, prompt the agent, and later create a private or internal Cursor Origin repository when the project is ready to keep building or share.

Cursor also says it can port-forward a cloud agent’s live environment into the browser. That makes it possible to preview a running project and use browser-based tools such as design mode. Publishing the result through the built-in flow requires connecting a Vercel account.

How to evaluate the update

The new pieces are most useful when a team has repeatable work arriving from external events, long-running goals that need continuity, or parallel tasks that benefit from isolated environments. They do not remove the need for repository permissions, environment review, or human checks before merging and publishing.

Sources

• Cursor — “What’s New in Cursor” changelog (late-August 2026): https://cursor.com/changelog
• Cursor — official updates account: https://x.com/cursor_ai