Cursor adds /goal command and isolated subagent VMs in cloud agent update
Cursor's August 19 changelog expands how cloud agents and the Cursor harness work as an always-on system for building and shipping software. The headline change is /goal, a command that gives agents a long-lived objective that persists until it is fully complete rather than ending when a single session stops. Subagents can now run on dedicated virtual machines, each holding an isolated copy of the project, which reduces interference when parallel workstreams execute. Cloud agents also gain subscriptions to pull requests, Slack threads, and scheduled tasks, so monitoring can extend beyond one-off prompts. Together, these updates push Cursor toward persistent, event-driven automation across repos and team channels. The published notes do not specify pricing, rollout tiers, or limits on VM count.
Cursor adds /goal command and isolated subagent VMs in cloud agent update
Cursor's Aug 19 changelog introduces /goal for long-lived agent objectives that persist until completion. 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.
Key takeaway
The /goal command and isolated subagent VMs move Cursor cloud agents from single-session assistants toward persistent, multi-channel automation.
What happened
According to Cursor's August 19, 2026 changelog, the company released updates to cloud agents and the Cursor harness aimed at letting always-on agents operate as a cohesive system for building and shipping software.
The release adds the /goal command for objectives that persist until completion, puts subagents on separate virtual machines with isolated project copies, and lets cloud agents subscribe to pull requests, Slack threads, and scheduled tasks.
Evidence
Cursor introduced the /goal command for long-lived agent objectives that persist until completion.
Cursor · attributed
Use /goal to give the agent a long-lived objective to work towards until it's fully complete.
Subagents can run on their own virtual machines with isolated 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.
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run ht
The changelog frames the work as improving cloud agents and the Cursor harness for always-on 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
Teams can wire agents to PRs, Slack, and schedules while parallel subagents work in sandboxed VMs, changing how long-running development workflows are automated.
Limits and uncertainties
The captured changelog excerpt is truncated mid-sentence and does not spell out full scheduled-task behavior.
The packet does not state pricing, enterprise availability, VM quotas, or rollout timing for the new features.
Practical implications
Operators can assign durable /goal objectives instead of re-prompting each session until work finishes.
Builders can run parallel subagents on isolated VMs to limit cross-contamination while cloud agents watch PRs, Slack threads, or scheduled triggers.
What to watch
Whether Cursor publishes full details on scheduled-task triggers, VM limits, and enterprise rollout for /goal and isolated subagent VMs.
