Cursor ships /goal, VM-isolated subagents, and event-driven cloud agents
Cursor's August 19 changelog advances cloud agents and the Cursor harness so always-on agents can operate as a coordinated system for building and shipping software. The release introduces /goal for long-lived objectives pursued until complete, VM-isolated subagents with separate project copies on their own machines, and subscriptions triggered by pull requests, Slack threads, or schedules. Cloud agents can automatically subscribe to PRs they open, fix CI failures, and address bot comments without manual restarts. The shift moves agent work from isolated sessions toward continuous automation on surfaces teams already monitor daily. The available excerpt does not spell out rollout scope, pricing, or enterprise controls, so operators should confirm workspace limits before redesigning workflows around unattended automation.
Cursor ships /goal, VM-isolated subagents, and event-driven cloud agents
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives, VM-isolated subagents, and subscriptions that react to PRs, Slack threads, or schedules. Cloud agents can auto-subscribe to PRs they open, fix CI, and address bot comments.
Key takeaway
Cursor's Aug 19 release turns cloud agents into event-driven workers with /goal objectives, VM-isolated subagents, and automated PR, Slack, and CI subscriptions.
What happened
Cursor published its August 19, 2026 changelog titled Cloud Agents and Cursor Harness Improvements, adding /goal for long-lived agent objectives, VM-isolated subagents, and event-driven subscriptions tied to PRs, Slack threads, or schedules.
According to the changelog and accompanying posts, subagents can run on their own virtual machines with an isolated copy of the project, and cloud agents can auto-subscribe to PRs they open, fix CI, and address bot comments.
Evidence
Cursor's Aug 19 changelog adds /goal, VM-isolated subagents, and subscriptions reacting to PRs, Slack threads, or schedules.
Cursor · attributed
Cursor's Aug 19 changelog adds /goal for long-lived agent objectives, VM-isolated subagents, and subscriptions that react to PRs, Slack threads, or schedules.
Cloud agents can auto-subscribe to PRs they open, fix CI, and address bot comments.
Cursor · attributed
Cloud agents can auto-subscribe to PRs they open, fix CI, and address bot comments.
/goal gives the agent a long-lived objective to work towards until fully complete.
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 an isolated copy of the project.
Cursor · attributed
Subagents can now run on their own virtual machines, each with an isolated copy of the project.
Cursor is improving cloud agents and the harness so always-on agents can operate as a system.
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
Teams can route agent work through existing PR, Slack, and schedule triggers instead of restarting sessions manually, while VM isolation limits cross-subagent interference on shared repositories.
Limits and uncertainties
The changelog excerpt in the packet is truncated and does not specify rollout scope, pricing, or enterprise controls.
The Slack integration description in the packet is cut off before full trigger and schedule details are stated.
Practical implications
Operators can assign durable /goal objectives and let cloud agents monitor PRs, Slack threads, or schedules rather than re-launching agents for each follow-up.
Builders can rely on VM-isolated subagents when parallel agent work needs separate project copies on dedicated machines.
Teams opening PRs via cloud agents can enable auto-subscription so agents fix CI and respond to bot comments on those PRs.
What to watch
Whether Cursor publishes full changelog details on Slack trigger options and schedule behavior beyond the truncated excerpt.
How auto-subscription to opened PRs performs on CI repair and bot-comment handling in production workspaces.
Any follow-up announcements on rollout limits, pricing, or enterprise controls for /goal and VM-isolated subagents.
