Cursor adds /goal command and isolated subagent VMs in cloud agent update
Cursor's August 19, 2026 changelog advances its cloud agent stack with a /goal command for long-lived objectives, dedicated virtual machines for subagents each carrying an isolated project copy, and event subscriptions that let cloud agents monitor pull requests, Slack threads, and scheduled tasks. The release positions these updates within broader Cursor harness work aimed at always-on agents operating as a system for building and shipping software. Teams evaluating cloud automation should note that subagents now run on separate VMs rather than sharing one runtime context, while /goal gives agents a persistent objective until completion. Available reporting here is changelog-level: social snippets and page extracts in this packet are partially truncated, so full feature scope, availability, and integration limits remain to be confirmed in Cursor's complete release notes.
Cursor adds /goal command and isolated subagent VMs in cloud agent update
Cursor's Aug 19 changelog introduces /goal for long-lived agent objectives and moves subagents onto dedicated virtual machines with isolated project copies. Cloud agents can also monitor PRs, Slack threads, and scheduled tasks through event subscriptions.
Key takeaway
The /goal command and VM-isolated subagents mark Cursor's push toward persistent, system-level cloud agents rather than session-bound automation.
What happened
In its August 19, 2026 changelog, Cursor introduced the /goal command so agents can pursue a long-lived objective until it is fully complete, alongside harness improvements for cloud agents.
The same update moves subagents onto dedicated virtual machines with isolated project copies and adds event subscriptions so cloud agents can monitor pull requests, Slack threads, and scheduled tasks.
Evidence
Cursor added 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 now run on dedicated virtual machines with isolated project copies.
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
Cloud agents can monitor PRs, Slack threads, and scheduled tasks via event subscriptions.
Cursor · attributed
Cloud agents can also monitor PRs, Slack threads, and scheduled tasks through event subscriptions.
The changelog frames the work as improving always-on cloud agents as a coordinated system.
Cursor · attributed
We're continuing to improve cloud agents and the Cursor harness so always-on agents can operate as a system, building and shipping softwa
Why it matters
Event subscriptions for PRs, Slack, and scheduled tasks widen where cloud agents can act without manual triggers.
Limits and uncertainties
Several source snippets in the packet are truncated, including the social post ending at 'run ht' and the changelog page extract ending at 'building and shipping softwa'.
Slack integration is referenced in social copy, but this packet does not include full integration details or limits.
Practical implications
Operators can assign persistent work with /goal instead of restating objectives each session.
Builders running subagents should expect separate VMs and isolated project copies, which may change how parallel agent work is coordinated.
Teams can wire cloud agents to PR, Slack, and scheduled-task events rather than relying solely on manual invocation.
What to watch
Whether Cursor publishes full docs on event subscription setup, scopes, and Slack monitoring behavior beyond the truncated snippets.
How /goal completion criteria and subagent VM lifecycle are documented in the full changelog.
