Cursor adds /goal command and isolated subagent VMs in Aug 19 cloud agents release
In its August 19, 2026 changelog, Cursor rolled out harness upgrades for cloud agents aimed at sustained autonomous work rather than one-off prompts. The headline additions are a /goal command that keeps an agent focused on a long-lived objective until it is fully complete, and VM-backed subagents that each run in a separate cloud environment with an isolated project copy and clean context. Cursor positions these changes within broader cloud-agent and harness improvements so always-on agents can operate as a system for building and shipping software. The published summary also alludes to Slack integration and PR monitoring, but those details are truncated in the available excerpts, so operators should treat them as announced directions rather than fully documented behavior until Cursor publishes fuller guidance.
Cursor adds /goal command and isolated subagent VMs in Aug 19 cloud agents release
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 cloud agents now support persistent /goal objectives and per-subagent virtual machines with isolated project copies, enabling longer autonomous runs with cleaner parallel context.
What happened
According to Cursor's August 19, 2026 changelog, cloud agents gained a /goal command that lets users give the agent a long-lived objective to work toward until it is fully complete, rather than resetting scope on every interaction.
Cursor also reports that subagents can now run on their own virtual machines, with each receiving an isolated copy of the project and clean context in its own cloud environment, as part of ongoing cloud-agent and 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 dedicated virtual machines with isolated 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.
Cursor frames the release as part of improving always-on cloud agents as a system.
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 VM subagents and durable goals reduce cross-task context contamination when multiple autonomous workers touch the same repository, which is central to running parallel cloud-agent workflows safely.
Limits and uncertainties
The available changelog excerpt is truncated and does not fully document Slack integration, PR monitoring, or other referenced harness features beyond brief mentions.
Practical implications
Teams adopting cloud agents should plan how /goal scope, completion criteria, and per-subagent VM isolation map to their repo layout, secrets handling, and review gates before enabling parallel subagents.
What to watch
Whether Cursor publishes full documentation for /goal lifecycle behavior, subagent VM provisioning limits, and the announced Slack and PR monitoring capabilities beyond the truncated changelog summary.
