Cursor ships /goal command and isolated VM subagents in Aug 19 cloud agent update
Cursor's August 19, 2026 changelog expands how cloud agents operate within the Cursor harness as always-on systems. The central addition is a /goal command that assigns a long-lived objective the agent pursues until fully complete, moving beyond one-shot prompts. Subagents can now run on dedicated virtual machines, each with an isolated copy of the project, enabling parallel sandboxed work without shared filesystem contention. The post frames broader harness improvements for continuously building and shipping software, and distribution snippets mention Slack integration and PR monitoring without full detail in the excerpted corpus. Treat the official changelog as the scope boundary; truncated social copy may omit limits on VM subagents, billing, or enterprise behavior before production adoption.
Cursor ships /goal command and isolated VM subagents in Aug 19 cloud agent update
Use /goal to give the agent a long-lived objective to work towards until it's fully complete. Subagents can now run on their own virtual machines.
Key takeaway
The /goal command plus VM-isolated subagents shift Cursor cloud agents toward persistent, parallel execution rather than single-threaded chat sessions.
What happened
On August 19, 2026, Cursor published a changelog entry titled Cloud Agents and Cursor Harness Improvements, announcing updates to cloud agents and the Cursor harness so always-on agents can operate as a system for building and shipping software.
Cursor states users can use /goal to give the agent a long-lived objective to work towards until it is fully complete, and that subagents can now run on their own virtual machines, each with an isolated copy of the project; distribution snippets also reference Slack integration and PR monitoring.
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 can run on isolated virtual machines with separate project copies.
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
The release is framed as ongoing cloud agent and Cursor harness improvements.
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
Distribution copy mentions PR monitoring and Slack thread watching.
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run ht
Why it matters
Isolated VM subagents reduce cross-task interference and make multi-agent cloud workflows more viable for teams shipping code continuously.
Limits and uncertainties
The excerpted changelog text is truncated mid-sentence, so the full list of harness and integration changes is not visible in the packet.
Social distribution snippets cut off details on PR monitoring, Slack behavior, and any limits on VM subagent usage.
Practical implications
Teams can define durable /goal objectives for cloud agents instead of restating scope on every turn.
Builders can delegate parallel subagent work in isolated VMs without a single shared workspace copy.
What to watch
Whether Cursor publishes full documentation on VM subagent quotas, billing, and lifecycle management.
How PR monitoring and Slack thread watching behave in production workflows once details beyond truncated snippets are released.
