Cursor adds /goal command, VM subagents, and event-driven cloud agents
Cursor's August 19 changelog broadens always-on cloud agents from interactive sessions into an event-driven system that can pursue objectives, spawn isolated workers, and react to external signals. The new /goal command defines a long-lived objective the agent works toward until completion, rather than treating each prompt as a one-off task. Subagents can run on dedicated virtual machines with isolated project copies, reducing interference when parallel work is needed. Cloud agents also gain subscriptions to monitor pull requests, watch Slack threads, and run scheduled tasks, framing Cursor's harness as infrastructure for agents that build and ship over time. The public notes do not spell out pricing, limits, or enterprise rollout timelines.
Cursor adds /goal command, VM subagents, and event-driven cloud agents
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives and subagents that run on their own virtual machines with isolated project copies. Cloud agents can now monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
Key takeaway
Cursor is moving cloud agents toward persistent, event-triggered workflows with /goal objectives and VM-isolated subagents rather than single-turn chat.
What happened
According to Cursor's August 19, 2026 changelog, the product now supports a /goal command that gives an agent a long-lived objective to work toward until it is fully complete, extending how users steer always-on cloud agents.
The same release adds subagents that run on their own virtual machines, each with an isolated copy of the project, and lets cloud agents monitor pull requests, watch Slack threads, and run scheduled tasks through event subscriptions.
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 dedicated 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 monitor PRs, Slack threads, and scheduled tasks via event subscriptions.
Cursor · attributed
Cloud agents can now monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
The changelog frames these updates as improvements to cloud agents and the Cursor harness.
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
Operators can delegate ongoing build-and-ship work to agents that react to PRs, Slack activity, and schedules without manually re-prompting every cycle.
Limits and uncertainties
The published changelog excerpt in the packet is truncated and does not document pricing, quotas, or enterprise availability.
The packet does not specify which cloud agent plans or environments receive VM subagents and event subscriptions on day one.
Practical implications
Builders can set a /goal for multi-step objectives instead of chaining one-off prompts for work that spans days or weeks.
Teams can assign parallel subagents on isolated VMs when tasks need separate project copies without shared workspace contention.
Workflow owners can wire agents to PR monitoring, Slack thread watching, and scheduled runs rather than polling manually.
What to watch
Whether Cursor publishes full documentation on event subscription setup, VM subagent limits, and /goal completion criteria.
How teams report reliability and isolation when multiple VM subagents modify separate copies of the same repository.
