Cursor ships /goal command and VM-isolated subagents for cloud agents
Cursor’s August 19 changelog advances always-on cloud agents with two structural upgrades. A new /goal command lets operators assign long-lived objectives that persist until fully complete, shifting sessions from reactive prompts toward sustained work. Subagents can now execute on dedicated virtual machines, each carrying an isolated project copy, which reduces cross-task interference when parallel work runs in the background. The release also signals broader harness improvements so cloud agents can operate as a coordinated system rather than isolated chat turns, alongside Slack integration and PR monitoring capabilities referenced in the announcement. Teams evaluating autonomous coding workflows should note that details on rollout, pricing, and limits appear only in the full changelog, and some listed features were truncated in public snippets.
Cursor ships /goal command and VM-isolated subagents for cloud agents
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 and VM-isolated subagents move Cursor cloud agents toward sustained, parallel objectives instead of one-off chat tasks.
What happened
In an August 19, 2026 changelog entry titled Cloud Agents and Cursor Harness Improvements, Cursor announced a new /goal command that lets users give an agent a long-lived objective to work toward until it is fully complete.
Cursor also said subagents can now run on their own virtual machines, each with an isolated copy of the project, and referenced additional cloud agent updates including Slack integration and PR monitoring, though public snippets cut off before full feature details.
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 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.
Cursor is improving cloud agents and the harness for always-on system 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
Isolated VMs per subagent raise the ceiling for background automation but also increase infrastructure complexity for teams orchestrating many agents.
Limits and uncertainties
Public snippets truncate the changelog mid-sentence, so full scope of Slack, PR monitoring, and other listed updates is not fully visible in the packet.
The packet does not specify availability, pricing, quotas, or operational limits for VM-isolated subagents.
Practical implications
Operators can assign durable /goal objectives instead of repeatedly restating the same end state across sessions.
Builders running parallel subagents should plan for per-VM project isolation when coordinating background work.
What to watch
Whether Cursor publishes full changelog details on Slack integration, PR monitoring, and VM subagent limits beyond truncated public snippets.
How teams operationalize long-lived /goal workflows alongside multiple VM-isolated subagents in production pipelines.
