Cursor adds /goal command and isolated subagent VMs in Aug 19 cloud agents update
Cursor's August 19, 2026 changelog expands cloud agents and the Cursor harness toward always-on, system-level automation. The headline features are the /goal command, which gives an agent a long-lived objective until completion, and isolated subagent virtual machines that each hold a separate copy of the project. Cloud agents can also monitor pull requests, watch Slack threads, and execute scheduled work through event subscriptions. Together, these changes move Cursor from session-based assistance toward persistent agents that can coordinate parallel work and react to external signals. Teams evaluating autonomous coding workflows should note that the public packet describes capabilities at a high level; pricing, enterprise controls, and operational limits for VM-backed subagents are not detailed in the cited changelog excerpt.
Cursor adds /goal command and isolated subagent VMs in Aug 19 cloud agents update
Cursor's Aug 19, 2026 changelog adds /goal for long-lived agent objectives and lets subagents run on their own virtual machines with isolated project copies. Cloud agents can also monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
Key takeaway
Cursor is positioning cloud agents as persistent operators: /goal for durable objectives, VM-isolated subagents, and event-driven PR, Slack, and schedule hooks.
What happened
In its August 19, 2026 changelog, Cursor announced Cloud Agents and Cursor Harness Improvements aimed at letting always-on agents operate as a system for building and shipping software.
The release adds the /goal command for long-lived agent objectives, lets subagents run on dedicated virtual machines with isolated project copies, and enables cloud agents to monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
Evidence
Cursor added the /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.
Cloud agents can monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
Cursor · attributed
Cloud agents can also monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
The update is framed as improving cloud agents and the Cursor 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
Persistent objectives, isolated subagent VMs, and event subscriptions reduce the need for manual session restarts when coordinating multi-step or externally triggered engineering work.
Limits and uncertainties
The available changelog excerpt in the packet is truncated and does not specify pricing, quotas, enterprise policy controls, or full operational limits for VM-backed subagents.
Practical implications
Teams can define durable /goal objectives instead of re-prompting for multi-step work that spans sessions.
Parallel subagent work can be isolated per VM, which may reduce cross-task interference but increases infrastructure surface area to monitor.
PR monitoring, Slack thread watching, and scheduled event subscriptions enable automation triggered by repository and chat activity rather than manual agent launches.
What to watch
Whether Cursor publishes full changelog details on VM isolation boundaries, event subscription configuration, and enterprise governance for always-on cloud agents.
