Cursor ships /goal command and isolated subagent VMs for cloud agents
Cursor's August 19 changelog moves cloud agents closer to always-on automation by pairing a new /goal command with isolated subagent infrastructure. The /goal directive gives agents a long-lived objective they pursue until completion, rather than treating each prompt as a one-off task. Subagents can now run on separate virtual machines, each holding its own copy of the project, which reduces cross-task interference when parallel workstreams spin up. Cloud agents can also subscribe to external triggers, including pull requests, Slack threads, and scheduled tasks, then resume work automatically as new events arrive. Cursor frames the release as harness improvements meant to let agents operate as a coordinated system that builds and ships software continuously. Teams evaluating agent ops should note that changelog excerpts truncate details on Slack hooks and scheduling behavior, so production rollout still depends on reading the full post.
Cursor ships /goal command and isolated subagent VMs for cloud agents
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives and lets subagents run on isolated virtual machines with separate project copies. Cloud agents can subscribe to PRs, Slack threads, or scheduled tasks and automatically pick up work until goals are met.
Key takeaway
The /goal command and isolated subagent VMs turn Cursor cloud agents into persistent workers that can chase objectives across PR, Slack, and scheduled triggers.
What happened
According to Cursor's August 19, 2026 changelog, the platform added a /goal command that assigns agents a long-lived objective they work toward until fully complete, rather than stopping after a single interaction.
The same release lets subagents run on isolated virtual machines with separate project copies, and enables cloud agents to subscribe to pull requests, Slack threads, or scheduled tasks and automatically resume 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
Persistent cloud agents with isolated subagent VMs shift agent tooling from chat sessions toward automated software delivery pipelines that react to repository and team events.
Limits and uncertainties
Changelog excerpts in the evidence packet truncate Slack monitoring and scheduling details mid-sentence.
The packet does not specify VM sizing, concurrency limits, pricing, or enterprise availability for isolated subagent runs.
Practical implications
Teams can define durable /goal objectives and wire cloud agents to PR, Slack, or scheduled triggers instead of manually re-prompting each cycle.
Parallel subagents on isolated project copies may reduce interference but require planning for merge coordination across VM instances.
What to watch
Whether Cursor publishes full documentation on Slack thread monitoring, scheduled task hooks, and subagent VM limits beyond the truncated changelog excerpt.
