Cursor ships /goal command and isolated VM subagents in cloud agents update
Cursor's August 19 changelog expands its cloud agent stack with a /goal command for persistent objectives and isolated virtual machines for subagents. The /goal directive lets agents pursue a long-lived objective until it is fully complete rather than stopping after a single turn. Subagents can now execute on dedicated VMs, each carrying an isolated copy of the project, which reduces cross-task interference when parallel work runs. Cloud agents may also subscribe to pull requests, Slack threads, or scheduled tasks and resume automatically until configured goals are satisfied. Cursor frames the release as harness improvements aimed at always-on agents operating as a coordinated system that builds and ships software. Operators should treat this as an infrastructure shift toward autonomous, event-driven agent loops, though the public changelog excerpt does not spell out pricing, enterprise limits, or full Slack integration details.
Cursor ships /goal command and isolated VM subagents in cloud agents update
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives and lets subagents run on their own virtual machines with isolated project copies. Cloud agents can subscribe to PRs, Slack threads, or scheduled tasks and automatically pick up work until goals are met.
Key takeaway
Cursor now ties cloud agents to durable /goal objectives, VM-isolated subagents, and automated triggers from PRs, Slack, or schedules.
What happened
Cursor published its August 19, 2026 changelog under Cloud Agents and Cursor Harness Improvements, announcing a /goal command for long-lived agent objectives and subagents that run on their own virtual machines.
According to Cursor's changelog summary, each subagent VM holds an isolated copy of the project, and cloud agents can subscribe to pull requests, Slack threads, or scheduled tasks and automatically pick up work until goals are met.
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.
Cloud agents can subscribe to PRs, Slack threads, or scheduled tasks and keep working until goals are met.
Cursor · attributed
Cloud agents can subscribe to PRs, Slack threads, or scheduled tasks and automatically pick up work until goals are met.
Cursor is improving cloud agents and the harness so always-on agents operate 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 running always-on coding agents gain a clearer path from event triggers to finished outcomes without manually restarting sessions after each notification.
Limits and uncertainties
The provided changelog text is truncated before it fully describes Slack monitoring or scheduled-task behavior.
Pricing, enterprise controls, and VM resource limits are not specified in the available excerpt.
Practical implications
Builders can define long-lived /goal objectives instead of re-prompting agents after each incremental task.
Parallel subagent work should be routed to isolated VMs to avoid conflicting edits in a shared workspace.
What to watch
Whether Cursor publishes full details on Slack thread monitoring and scheduled-task triggers in the complete changelog.
How subagent VM isolation performs on large repositories and long-running goals.
