Cursor adds /goal command and subagents on isolated virtual machines
Cursor's August 19, 2026 changelog introduces a /goal command and VM-isolated subagents as part of broader cloud-agent harness improvements. The /goal command assigns a long-lived objective the agent pursues until completion, shifting work from one-off prompts toward durable missions. Subagents now run on dedicated virtual machines, each with an isolated project copy and clean context in its own cloud environment, which reduces cross-task contamination when parallel work runs. Cursor positions the update so always-on agents can operate as a system for building and shipping software. Available excerpts also mention PR monitoring and Slack thread watching, but those claims arrive truncated in the packet rather than as fully documented changelog bullets. Teams evaluating autonomous workflows should note the combination of persistent goals and hardware-isolated delegation, while treating incomplete excerpts as a coverage limit until the full changelog is reviewed.
Cursor adds /goal command and subagents on isolated virtual machines
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. Each gets an isolated copy of the project with clean context in its own cloud environment.
Key takeaway
Cursor's /goal command plus VM-hosted subagents move cloud agents from session-scoped prompts toward durable objectives and isolated parallel execution.
What happened
On August 19, 2026, Cursor published a changelog entry titled Cloud Agents and Cursor Harness Improvements announcing the /goal command and subagent virtual-machine isolation.
According to Cursor's reporting, /goal lets users set a long-lived objective the agent works toward until completion, while subagents run on separate virtual machines with isolated project copies and clean cloud contexts.
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 gets an isolated copy of the project with clean context in its own cloud environment.
The release is framed as cloud-agent and harness improvements for always-on agents.
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 and isolated subagent VMs change how teams can safely delegate parallel autonomous work without shared context bleed.
Limits and uncertainties
The available changelog excerpt in the packet is truncated and does not include the full list of harness changes.
References to PR monitoring and Slack thread watching appear only in partially cut social snippets, not as complete changelog documentation in the packet.
Practical implications
Operators may need to structure work around /goal as a durable mission rather than a single-turn prompt.
Parallel subagents on separate VMs imply separate isolated project copies, which may affect how teams coordinate reviews and merges across delegated tasks.
What to watch
The full Cursor changelog for complete details on PR monitoring, Slack integration, and other harness updates only hinted at in truncated excerpts.
How VM-isolated subagents behave in real multi-step build and ship workflows once teams adopt /goal-driven missions.
