Cursor adds /goal command and isolated VM subagents for cloud agents
Cursor's August 19 changelog expands how cloud agents pursue work over time and where subagents execute. The new /goal command lets operators assign a durable objective that the agent keeps working toward until completion, rather than treating each prompt as a disconnected task. Subagents can now run on dedicated virtual machines, each holding an isolated copy of the project inside its own cloud environment. Cursor frames the release as part of broader harness improvements so always-on agents can operate more like a coordinated system for building and shipping software. The same update cycle also references Slack integration and PR monitoring, though those details are only partially described in the available material. Teams evaluating cloud agents should weigh isolation benefits against the operational overhead of provisioning and monitoring per-subagent VMs.
Cursor adds /goal command and isolated VM subagents for cloud agents
Cursor's Aug 19 changelog adds /goal so agents can hold 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 cloud agents can now pursue a persistent /goal until finished while subagents run on isolated VMs with separate project copies.
What happened
In its August 19, 2026 changelog, Cursor introduced the /goal command so agents can hold a long-lived objective and keep working toward it until it is fully complete.
The same release lets subagents run on their own virtual machines, each with an isolated copy of the project in its own cloud environment, as part of broader cloud agent and Cursor harness improvements.
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.
Cursor is improving cloud agents and the harness for always-on system-style operation.
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
Persistent goals plus VM-isolated subagents move cloud agents toward longer-running, parallel workflows with stronger separation between concurrent tasks.
Limits and uncertainties
The available changelog excerpt is truncated, so Slack integration, PR monitoring, and other mentioned features are not fully documented in the packet.
Practical implications
Operators can define durable /goal objectives instead of re-stating scope across sessions, and assign subagents to isolated VMs when parallel work needs project separation.
What to watch
Whether Cursor publishes full documentation on VM subagent provisioning, limits, and how /goal completion is determined in production cloud agents.
