Cursor ships /goal command and isolated subagent VMs in cloud agents release
Cursor's August 19 changelog expands always-on cloud agents toward system-style operation rather than single-turn sessions. The release introduces /goal, which assigns a durable objective the agent pursues until completion, with follow-up work queued across tool calls in long-running sessions. Subagents now execute on isolated virtual machines, each receiving a separate copy of the project, reducing interference between parallel branches of work. Cloud agents can also subscribe to external events and monitor pull requests or Slack threads while retaining active goals. Together, the harness changes aim to let agents build and ship software continuously with clearer persistence and isolation. Availability and rollout details beyond the changelog entry were not specified in the published notes.
Cursor ships /goal command and isolated subagent VMs in cloud agents release
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives and lets subagents run on isolated virtual machines with their own project copies. Cloud agents can subscribe to events, monitor PRs and Slack threads, and hold goals through long-running sessions while follow-ups queue for the next tool call.
Key takeaway
Cursor is shifting cloud agents from reactive chat turns toward persistent, event-driven work with isolated subagent VMs and durable /goal objectives.
What happened
According to Cursor's August 19, 2026 changelog entry Cloud Agents and Cursor Harness Improvements, the company is improving cloud agents and the Cursor harness so always-on agents can operate as a coordinated system for building and shipping software.
The release adds the /goal command for long-lived objectives, lets subagents run on isolated virtual machines with their own project copies, and enables cloud agents to subscribe to events, monitor pull requests and Slack threads, and hold goals through long-running sessions while follow-ups queue for the next tool call.
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 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 events and monitor PRs and Slack threads while holding goals across sessions.
Cursor · attributed
Cloud agents can subscribe to events, monitor PRs and Slack threads, and hold goals through long-running sessions while follow-ups queue for the next tool call.
The changelog frames the release as harness improvements for always-on system-style agents.
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 goals, event subscriptions, and VM-isolated subagents change how teams can delegate multi-step software work, but the published notes do not spell out pricing, limits, or enterprise rollout timing.
Limits and uncertainties
The available changelog excerpt is truncated and does not document full feature scope, quotas, or regional availability.
No independent verification or benchmark data accompanies the release notes in the evidence packet.
Practical implications
Operators evaluating autonomous coding workflows should test /goal persistence and subagent VM isolation against their repo size and CI integration patterns.
Builders wiring cloud agents to Slack or PR monitors should plan how queued follow-ups behave when sessions span hours or days.
What to watch
Whether Cursor publishes fuller changelog details on subagent VM limits, Slack monitoring behavior, and /goal completion semantics.
How teams report cost and latency when multiple isolated subagent VMs run parallel copies of the same project.
