Cursor adds /goal command and VM-isolated subagents for cloud agents
Cursor's August 19, 2026 changelog moves always-on cloud agents toward system-level operation with the /goal command, which sets long-lived objectives agents pursue until completion. Subagents can now run on dedicated virtual machines, each with an isolated project copy, limiting cross-task interference during parallel work. Event-driven cloud agents can monitor pull requests or Slack threads and maintain direction across extended sessions. The release also bundles harness improvements and Slack integration updates for agents that build and ship software continuously. Operators should treat /goal as the control surface for durable missions and VM-backed subagents as the isolation layer for parallel exploration. The published entry does not specify pricing, regional availability, or operational limits for VM subagents.
Cursor adds /goal command and VM-isolated subagents for cloud agents
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 also pick up event-driven work, monitor PRs or Slack threads, and stay on course through long-running sessions.
Key takeaway
Cursor now pairs durable /goal missions with VM-isolated subagents so cloud agents can run parallel, event-driven work without sharing one mutable workspace.
What happened
In its August 19, 2026 changelog titled Cloud Agents and Cursor Harness Improvements, Cursor reported new capabilities for always-on cloud agents and the Cursor harness.
The entry adds the /goal command for long-lived objectives, lets subagents run on separate virtual machines with isolated project copies, and enables cloud agents to handle event-driven tasks such as monitoring pull requests or Slack threads across long-running sessions.
Evidence
Cursor added the /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 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 take event-driven work and monitor PRs or Slack threads.
Cursor · attributed
Cloud agents can also pick up event-driven work, monitor PRs or Slack threads, and stay on course through long-running sessions.
The changelog was published on August 19, 2026.
Cursor · attributed
Aug 19, 2026 · Changelog 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
The shift from single-session assistants to goal-bound, VM-partitioned subagents signals Cursor is targeting always-on automation that watches external signals and ships work over extended runs.
Limits and uncertainties
The captured changelog excerpt is truncated and does not spell out pricing, quotas, or full operational limits for VM subagents.
Related coverage in the packet lists no additional independent sources beyond Cursor's own changelog entry.
Practical implications
Define explicit /goal objectives for long-running cloud agent jobs instead of relying on one-off prompts.
Use VM-isolated subagents when parallel tasks need separate project copies rather than a shared working tree.
Wire PR or Slack monitoring into event-driven agent workflows where continuous supervision replaces manual polling.
What to watch
Follow-up changelog or docs detailing VM subagent limits, billing, and how /goal completion is determined.
Whether Slack integration and PR monitoring behavior is documented with concrete setup steps beyond the announcement.
