Cursor adds /goal command and isolated VM subagents in Aug 19 cloud agent update
Cursor's August 19, 2026 changelog expands how cloud agents operate as persistent systems rather than one-off sessions. The release adds a /goal command so agents can pursue long-lived objectives until completion, and moves subagents onto dedicated virtual machines with isolated project copies, reducing interference between parallel workstreams. Cloud agents also gain event-driven hooks to monitor pull requests, watch Slack threads, and run scheduled tasks through subscriptions. Cursor frames the update as part of broader harness improvements for always-on agents that build and ship software. Teams evaluating autonomous coding workflows should weigh how isolated VM subagents change parallelism and how goal persistence alters supervision models. The published changelog excerpts do not specify pricing, rollout tiers, or limits on concurrent subagents.
Cursor adds /goal command and isolated VM subagents in Aug 19 cloud agent update
Cursor's Aug 19 changelog introduces /goal for persistent agent objectives and puts subagents on isolated virtual machines with separate project copies. Cloud agents can monitor PRs, watch Slack threads, and run scheduled tasks through event subscriptions.
Key takeaway
Persistent /goal objectives plus VM-isolated subagents mark a shift toward always-on cloud agents with event-driven PR and Slack automation.
What happened
According to Cursor's August 19, 2026 changelog, the product now supports a /goal command that gives agents a long-lived objective to work toward until it is fully complete, alongside broader cloud agent and harness improvements.
The same changelog states that subagents can run on their own virtual machines, each with an isolated copy of the project, and that cloud agents can monitor pull requests, watch Slack threads, and run scheduled tasks through event subscriptions.
Evidence
Cursor added a /goal command for persistent agent objectives.
Cursor · attributed
Use /goal to give the agent a long-lived objective to work towards until it's fully complete.
Subagents now 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 monitor PRs, watch Slack threads, and run scheduled tasks via event subscriptions.
Cursor · attributed
Cloud agents can monitor PRs, watch Slack threads, and run scheduled tasks through event subscriptions.
Cursor published the update on August 19, 2026 as part of cloud agent and harness improvements.
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 update treats agents as ongoing systems—goals, isolated VMs, and event subscriptions—rather than single-session coding assistants.
Limits and uncertainties
The available changelog excerpt is truncated and does not document pricing, enterprise rollout, or caps on concurrent subagents.
The packet does not specify which cloud agent tiers receive VM-isolated subagents or event subscriptions.
Practical implications
Operators can assign durable /goal objectives instead of re-prompting for multi-step work that spans sessions.
Builders running parallel subagents should plan for per-VM project copies when estimating compute and sync overhead.
Teams can wire cloud agents to PR monitoring, Slack thread watching, and scheduled tasks through event subscriptions.
What to watch
Whether Cursor publishes full changelog details on subagent VM limits, scheduling behavior, and Slack integration scope.
How /goal completion criteria and handoff between parent agents and VM subagents are documented in product docs.
