Cursor adds /goal command and VM-isolated subagents in Aug 19 cloud agent update
Cursor's August 19, 2026 product changelog adds infrastructure for longer-running cloud automation rather than one-off chat turns. Users can invoke /goal to set an objective that stays in force until the agent marks it finished, which changes how teams delegate multi-step work. Parallel subagents now spin up on dedicated virtual machines with duplicated project state, limiting bleed-over between concurrent branches of work. The same release extends cloud agents into pull-request surveillance and Slack thread watching, signaling tighter coupling between coding agents and everyday engineering channels. Cursor positions these harness upgrades as steps toward always-on agents that build and ship as a coordinated system. Published excerpts in the available record appear incomplete, so operators should consult the full changelog before changing production agent policies.
Cursor adds /goal command and VM-isolated subagents in Aug 19 cloud agent update
Cursor's Aug 19 changelog introduces /goal, giving agents a long-lived objective until completion. Subagents can now run on isolated virtual machines with separate project copies, while cloud agents monitor PRs and Slack threads.
Key takeaway
/goal gives Cursor cloud agents a durable completion target, while VM-isolated subagents and PR or Slack monitoring enable safer parallel, always-on workflows.
What happened
According to Cursor's August 19, 2026 changelog, the company is continuing to improve cloud agents and the Cursor harness so always-on agents can operate as a system for building and shipping software.
The release introduces the /goal command for long-lived objectives until completion, enables subagents on isolated virtual machines with separate project copies, and lets cloud agents monitor pull requests and Slack threads.
Evidence
Cursor added a /goal command that keeps an objective active until fully complete.
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 their own project copy.
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
Cloud agents gained monitoring for pull requests and Slack threads.
Cursor · attributed
Subagents can now run on isolated virtual machines with separate project copies, while cloud agents monitor PRs and Slack threads.
The update was published on August 19, 2026.
Cursor · attributed
Aug 19, 2026 · Changelog
Why it matters
The update moves Cursor agents from session prompts toward persistent orchestration across code review and chat, raising new questions about isolation cost and monitoring scope.
Limits and uncertainties
Available changelog text in the evidence packet ends mid-sentence after 'building and shipping softwa'.
Slack monitoring description in the packet is truncated at 'or run ht', leaving unspecified capabilities.
Practical implications
Teams adopting /goal should define completion criteria before delegating multi-step objectives to cloud agents.
Parallel subagent workflows may multiply VM and project-copy resources; capacity planning should precede wide rollout.
What to watch
Publication of the complete Aug 19 changelog sections on Slack integration and remaining cloud-agent features.
Operational documentation on /goal completion semantics and subagent VM lifecycle.
