Cursor ships /goal command and isolated subagent VMs for cloud agents
Cursor published its August 19, 2026 changelog with cloud-agent upgrades aimed at always-on automation. The new /goal command lets users give an agent a long-lived objective that stays active until the work is fully complete, instead of treating each prompt as a one-off task. Subagents can now run on their own virtual machines, each with an isolated copy of the project, which reduces interference when parallel agents work on the same codebase. The entry frames these as harness improvements so cloud agents can operate as a coordinated system for building and shipping software. Cursor also mentions broader updates including Slack integration and PR monitoring, though the available packet provides only partial detail on those items.
Cursor ships /goal command and isolated subagent VMs for cloud agents
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.
Key takeaway
Cursor's /goal command and VM-isolated subagents turn cloud agents into persistent, parallel workers rather than single-session chat turns.
What happened
According to Cursor's August 19, 2026 changelog, the company shipped a new /goal command for cloud agents. The command is designed to give an agent a long-lived objective to work toward until that objective is fully complete.
The same changelog states that subagents can now run on their own virtual machines, each with an isolated copy of the project. Cursor describes the release as part of ongoing cloud agent and harness improvements so always-on agents can operate as a system.
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 with an isolated copy of the project.
Cursor is improving cloud agents and the 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
The changelog also references PR monitoring and Slack thread watching
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run ht
Why it matters
Teams running always-on cloud agents gain clearer orchestration for multi-step objectives and safer parallel execution without shared workspace collisions.
Limits and uncertainties
The available evidence is truncated and does not fully describe Slack integration, PR monitoring, or other items mentioned in the changelog teaser.
Full feature behavior, limits, and pricing for isolated subagent VMs are not specified in the packet.
Practical implications
Operators can assign durable objectives with /goal instead of restating scope on every turn.
Parallel subagent workflows should be planned around per-VM project isolation rather than a single shared workspace.
What to watch
Whether Cursor publishes fuller documentation on isolated subagent VM limits, lifecycle, and cost.
How /goal completion criteria are defined and enforced in long-running cloud agent sessions.
