Subagents get their own VMs in Cursor update

Cursor has added a /goal command and moved subagents onto their own virtual machines, each with an isolated copy of the project, in a changelog dated August 19, 2026. The same update extends cloud agents so they start work in response to events, according to Cursor's changelog, relayed in a post on Threads.

At a glance

• Cloud agents can monitor pull requests, watch a Slack thread or run scheduled tasks, which means a run can start from an event in a repository or a channel rather than a typed prompt.
• According to Cursor, cloud agents hold a goal until it is met and stay on course through long-running sessions, the behaviour the newly supported /goal command is grouped with in the changelog.
• Subscriptions are available for cloud agents only for now, according to Cursor, and custom modes are listed as a way to keep an agent focused on a skill during those runs.

The direction reads as a shift from agents that wait for a prompt to agents that hold a queue of triggers: a pull request, a Slack thread, a scheduled slot. Machine-level isolation matters most for the parallel case, since agents sharing one working tree tend to collide on the same files. The cloud-only limit on subscriptions likely keeps the trigger surface inside infrastructure Cursor operates itself.

Each subagent runs on its own virtual machine with an isolated copy of the project

Subagents now run on their own virtual machines, each with an isolated copy of the project it works on. A virtual machine is a separate guest environment on shared hardware, with its own filesystem and process space, so files written inside one machine are not visible to the others.

The isolation is per subagent: each one gets its own machine and its own copy of the project, so a session that spawns several of them ends up with parallel copies of the repository rather than one shared working directory. Cursor lists the change among the main points of the August 19, 2026 update.

Cursor now supports the /goal command alongside custom modes in the same entry

Cursor now supports a /goal command. According to the changelog, cloud agents hold a goal until it is met and stay on course through long-running sessions, which is the behaviour the command is grouped with in that entry of the release notes. A slash command is a typed shortcut that triggers a defined behaviour instead of a free-form instruction.

Cursor describes custom modes as a way to keep an agent focused on a skill. The changelog lists them next to the /goal command, so the goal-holding behaviour and the mode restriction are presented as part of the same August 19, 2026 release.

Cloud agents can monitor pull requests, watch a Slack thread or run scheduled tasks

Cursor says cloud agents can monitor pull requests, watch a Slack thread or run scheduled tasks, picking up work when an event fires rather than when a developer types a prompt. The three triggers are listed together in the same changelog entry.

Watching a Slack thread runs through Cursor's app on Slack, an integration listed by both Slack and Cursor. The app puts the agent inside a workspace conversation, where the trigger is a posted message rather than a pull request or a schedule.

Cursor states that subscriptions are available for cloud agents only for now. The cloud agents in question run on Cursor's infrastructure, the same side of the product where subagents now receive their own virtual machines in this release. Cursor frames the restriction as applying for now.

When subscriptions leave the cloud

Cursor gives no date for extending subscriptions past cloud agents, and the changelog names no price for the virtual machines subagents now occupy. Whether the event triggers reach the local editor is left open, as is any limit on how many isolated project copies a single session may hold. Cursor describes the cloud-only restriction as applying for now.