Cursor adds /goal command and puts subagents on isolated cloud VMs
Cursor's August 19 changelog advances always-on cloud agents toward system-level automation. The headline addition is /goal, a command that lets agents pursue a long-lived objective until it is fully complete rather than stopping after a single turn. Subagents now run on their own virtual machines, each holding an isolated copy of the project, which reduces interference when parallel workstreams execute in the background. Cloud agents can also subscribe to pull requests, Slack threads, or scheduled tasks to pick up work automatically without manual prompting. Cursor frames these harness improvements as steps toward agents that build and ship software continuously. The changelog excerpt is truncated, so full rollout details, pricing, and enterprise constraints may not yet be visible from this release note alone.
Cursor adds /goal command and puts subagents on isolated cloud VMs
Cursor's Aug 19 changelog introduces /goal so agents can pursue a long-lived objective until it is fully complete. Subagents can now run on their own virtual machines with isolated project copies, and cloud agents can subscribe to PRs, Slack threads, or scheduled tasks to pick up work automatically.
Key takeaway
Cursor is shifting cloud agents from one-shot sessions toward persistent objectives, isolated subagent VMs, and event-driven triggers on PRs, Slack, and schedules.
What happened
In its August 19 changelog, Cursor announced Cloud Agents and Cursor Harness Improvements, including a new /goal command that gives agents a long-lived objective to work toward until it is fully complete.
The same release note states that subagents can now run on their own virtual machines with isolated project copies, and that cloud agents can subscribe to PRs, Slack threads, or scheduled tasks to pick up work automatically.
Evidence
Cursor introduced 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 subscribe to PRs, Slack threads, or scheduled tasks for automatic work pickup.
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run ht
Cursor positions the release as improving always-on cloud agents and the harness 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
Teams can delegate durable objectives and background subagent work without constant prompting, while external signals such as PR activity or Slack threads can restart agent execution.
Limits and uncertainties
The available changelog excerpt is truncated mid-sentence, so complete feature scope, configuration steps, and limits are not fully visible from this packet.
Practical implications
Operators can define persistent /goal objectives instead of repeatedly reissuing the same multi-step instructions across sessions.
Builders can run parallel subagents on isolated VMs to limit cross-task interference while cloud agents watch PRs, Slack threads, or schedules for new work.
What to watch
Whether Cursor publishes the full changelog details on VM isolation limits, subscription setup for PRs and Slack, and scheduled task behavior.
