Cursor ships /goal command and VM-isolated subagents for cloud agents
Cursor's August 19 changelog introduces harness upgrades for always-on cloud agents working as a coordinated system. The new /goal command lets agents pursue a long-lived objective until it is fully complete, shifting sessions from single-turn tasks toward sustained execution. Subagents can now run on their own virtual machines, each with an isolated copy of the project in a separate cloud environment, expanding parallel work without shared filesystem collisions. The release frames these changes as part of broader cloud agent and Cursor harness improvements. Teams evaluating autonomous coding workflows should weigh isolation benefits against VM provisioning and monitoring overhead. The packet highlights /goal and VM isolation most clearly; Slack integration and PR monitoring appear only in truncated promotional copy, so full rollout details may require the complete changelog.
Cursor ships /goal command and VM-isolated subagents for cloud agents
Cursor's Aug 19 changelog adds /goal so agents can pursue a long-lived objective until it is fully complete. Subagents can now run on their own virtual machines, each with an isolated project copy in its own cloud environment.
Key takeaway
Cursor is pushing cloud agents toward persistent, multi-step execution with /goal and VM-isolated subagents that can work in parallel on separate project copies.
What happened
In its August 19, 2026 changelog, Cursor added the /goal command so agents can pursue a long-lived objective until it is fully complete, according to Cursor's published release notes.
The same changelog states that subagents can now run on their own virtual machines, each with an isolated project copy in its own cloud environment, as part of cloud agent and Cursor harness improvements.
Evidence
Cursor added a /goal command for long-lived 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 dedicated VMs with isolated project copies
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
The release is dated August 19, 2026 and targets cloud agent harness improvements
Cursor · attributed
Aug 19, 2026 · Changelog 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
Isolated VM subagents plus durable /goal objectives move Cursor cloud agents closer to always-on, system-level automation rather than one-off chat sessions.
Limits and uncertainties
Promotional copy in the packet is truncated and only partially describes Slack integration, PR monitoring, and other changelog items beyond /goal and VM isolation.
The packet does not specify VM sizing, concurrency limits, pricing, or enterprise availability for isolated subagents.
Practical implications
Operators can assign a persistent /goal when work should continue until completion instead of re-prompting each session.
Builders can delegate parallel subagent work with filesystem isolation, reducing collision risk from multiple agents editing the same project copy.
What to watch
Whether Cursor publishes full details on Slack thread monitoring, PR watching, and other harness features mentioned only in truncated social copy.
How teams operationalize VM-isolated subagents for cost, latency, and coordination across long-running /goal runs.
