Cursor adds /goal command and VM-isolated subagents in cloud agent update
Cursor's August 19, 2026 changelog expands always-on cloud agents with three structural capabilities aimed at sustained, system-level automation. A new /goal command lets operators assign long-lived objectives that agents pursue until completion rather than treating each prompt as a one-off task. Subagents can now execute on dedicated virtual machines, each carrying an isolated copy of the project, which reduces cross-task interference when parallel workstreams run concurrently. Cloud agents can also subscribe to external events, monitoring pull requests, Slack threads, or scheduled triggers to react without manual nudging. These changes position Cursor's harness closer to a persistent build-and-ship loop rather than chat-only assistance. The release notes emphasize that event subscriptions currently apply to cloud agents only, leaving unclear when comparable triggers might reach local or desktop workflows.
Cursor adds /goal command and VM-isolated subagents in cloud agent update
Cursor's Aug 19 changelog introduces /goal for long-lived agent objectives, subagents on isolated virtual machines, and event subscriptions for PRs, Slack threads, and scheduled tasks. Subscriptions remain available for cloud agents only for now.
Key takeaway
The /goal command, VM-isolated subagents, and event subscriptions move Cursor cloud agents toward persistent, event-driven automation rather than single-turn chat.
What happened
According to Cursor's August 19, 2026 changelog, the product now supports a /goal command that gives agents a long-lived objective to work toward until it is fully complete.
The same release adds subagents that run on their own virtual machines with an isolated project copy, plus event subscriptions for pull requests, Slack threads, and scheduled tasks that remain available for cloud agents only for now.
Evidence
Cursor introduced a /goal command for long-lived agent objectives.
Cursor · attributed
Use /goal to give the agent a long-lived objective to work towards until it's fully complete.
Subagents can run on isolated virtual machines with their own project copy.
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
Cloud agents can subscribe to PR, Slack thread, and scheduled task events.
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run ht
Event subscriptions are limited to cloud agents for now.
Cursor · attributed
Subscriptions remain available for cloud agents only for now.
Why it matters
Teams running unattended pipelines gain isolation for parallel subagent work and external triggers, but must stay on cloud agents until subscriptions broaden.
Limits and uncertainties
Event subscriptions remain available for cloud agents only for now.
Several source snippets in the packet are truncated, so full scope of Slack integration and harness changes may extend beyond what is quoted here.
Practical implications
Operators on cloud agents can assign durable /goal objectives and wire PR, Slack, or schedule triggers instead of manually restarting sessions.
Teams relying on local or desktop agents cannot use event subscriptions yet and may need cloud workflows for event-driven automation.
What to watch
Whether event subscriptions expand beyond cloud agents to local or desktop agent runtimes.
Follow-on changelog detail on Slack integration and broader Cursor harness improvements referenced in the release title.
