Cursor adds /goal command and VM-isolated subagents for cloud agents
Cursor's August 19 changelog pushes cloud agents toward always-on, event-driven operation rather than one-shot chat sessions. The headline additions are a /goal command that gives agents a durable objective to pursue until completion, and VM-isolated subagents that each receive their own virtual machine and separate copy of the project. Cloud agents can also subscribe to pull requests, Slack threads, and scheduled tasks so work can start when those systems fire events. Cursor frames the bundle as harness improvements meant to let agents operate as a coordinated system that builds and ships software. The published materials emphasize capability announcements more than rollout timing, pricing, or enterprise controls, so teams should verify availability on their plan before redesigning workflows around event-triggered agents.
Cursor adds /goal command and VM-isolated subagents for cloud agents
Cursor's Aug 19 changelog introduces /goal for long-lived agent objectives and runs subagents on isolated virtual machines with separate project copies. Cloud agents can also subscribe to PRs, Slack threads, and scheduled tasks to pick up work from events.
Key takeaway
Cursor is shifting cloud agents toward durable /goal objectives, VM-isolated subagents with separate project copies, and event subscriptions on PRs, Slack, and schedules.
What happened
In its August 19, 2026 changelog, Cursor announced Cloud Agents and Cursor Harness Improvements, including a new /goal command for long-lived agent objectives that agents work toward until fully complete.
The same release runs subagents on isolated virtual machines, each with its own copy of the project, and lets cloud agents subscribe to pull requests, Slack threads, and scheduled tasks to pick up work from those events.
Evidence
Cursor introduced a /goal command for long-lived objectives.
Cursor · attributed
Use /goal to give the agent a long-lived objective to work towards until it's fully complete.
Subagents run on isolated VMs 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, and scheduled tasks.
Cursor · attributed
Cloud agents can also subscribe to PRs, Slack threads, and scheduled tasks to pick up work from events.
Cursor frames the release as harness improvements for always-on agent systems.
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
Always-on agents that react to PR, Slack, and schedule events change how teams design triggers, isolation, and oversight for autonomous software work.
Limits and uncertainties
The packet excerpt cuts off mid-sentence on scheduled-task monitoring and does not spell out full feature scope or limits.
The evidence does not state rollout timing, plan tiers, pricing, or enterprise availability for the new cloud-agent capabilities.
Practical implications
Operators may need to define how /goal objectives end, how VM-isolated subagents share or diverge on project copies, and which PR, Slack, or schedule events should authorize agent runs.
What to watch
Whether Cursor publishes full changelog details on PR monitoring, Slack thread watching, scheduled-task triggers, and enterprise rollout constraints.
