Cursor ships /goal for long-lived cloud agent objectives
Cursor’s August 19, 2026 changelog advances always-on cloud agents by introducing /goal, a command that sets a long-lived objective the agent pursues until completion rather than a single prompt. The release positions subagents on dedicated virtual machines with isolated project copies, and adds operational hooks for monitoring pull requests, watching Slack threads, and running scheduled tasks. Together, these changes frame Cursor’s harness as a coordinated system for building and shipping software continuously. Teams evaluating autonomous workflows should read the full changelog for scope, pricing, and enterprise constraints, because the packet excerpt truncates mid-sentence and does not spell out limits on goal duration, permissions, or integration setup.
Cursor ships /goal for long-lived cloud agent objectives
Use /goal to give the agent a long-lived objective to work towards until it's fully complete. Subagents can now run on their own virtual machines, and Cursor can now monitor your PRs, watch a Slack thread, or run scheduled tasks.
Key takeaway
The /goal command shifts cloud agents from one-shot prompts to persistent objectives pursued until fully complete.
What happened
On August 19, 2026, Cursor published a changelog titled Cloud Agents and Cursor Harness Improvements announcing the /goal command for long-lived cloud agent objectives.
The same release states subagents can run on their own virtual machines with isolated project copies, and that Cursor can monitor pull requests, watch Slack threads, or run scheduled tasks.
Evidence
Cursor added /goal for long-lived objectives that run until 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 dedicated 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.
Cursor can monitor PRs, watch Slack threads, and run scheduled tasks
Cursor · attributed
Cursor can now monitor your PRs, watch a Slack thread, or run scheduled tasks.
The August 19, 2026 changelog frames always-on agents as a coordinated system
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
Isolated VM subagents plus PR, Slack, and scheduled triggers let always-on agents operate as a coordinated shipping system rather than ad hoc chat sessions.
Limits and uncertainties
The provided link summary cuts off mid-sentence at building and shipping softwa, so full harness scope is not visible in the packet.
A Slack-related snippet in the packet ends at run ht, leaving integration details incomplete here.
The packet does not specify goal completion criteria, permission boundaries, or enterprise availability.
Practical implications
Review the full changelog before relying on /goal for production workflows that depend on completion guarantees.
Plan for subagent VM isolation and duplicated project copies when sizing cloud agent workloads.
Treat PR monitoring, Slack watching, and scheduled tasks as new operational surfaces requiring access and alerting policies.
What to watch
Full changelog text on goal lifecycle, completion rules, and harness limits once the truncated excerpt is available.
Documentation on Slack thread watching and scheduled task configuration beyond the partial snippet.
Enterprise and pricing guidance for cloud agents using /goal and isolated subagent VMs.
