Skip to content

Developer tools

Subagents get their own VMs in Cursor update

2 min read

Written by an AI model from the linked sources and checked against them by a second model. How we work

All about: Coding agents →
Video: threads.com

Cursor’s subagents can now each run on a virtual machine of their own, with an isolated copy of the project, according to the company’s August 19 changelog, which Cursor announced in a post on Threads. The same update adds the /goal command and lets cloud agents start work when something happens, so you don’t have to prompt them first.

Cursor can now monitor your PRs, watch a Slack thread, or run scheduled tasks.

The isolation builds on how cloud agents already worked. Cursor’s documentation describes them as running in isolated cloud VMs that hold a full development environment, close to a laptop setup: cloned repos, installed dependencies, secrets, startup commands and network access. An agent clones the repo from GitHub, GitLab, Azure DevOps Services or Bitbucket Cloud, works on a separate branch and pushes its changes for handoff. Until now that setup applied to the agent as a whole. With this update, each subagent the main agent hands part of a task to gets its own machine and its own copy of the code. The docs also say an agent that can write code but can’t run tests, query services or reach APIs can’t close the loop on its work. Each environment can be set up by the agent itself, from a saved snapshot, or from a Dockerfile in .cursor/environment.json.

The /goal command covers long-running work. Cursor says cloud agents now hold a goal until it’s met and stay on course through long sessions. Agents could already be launched by hand from Slack with @cursor, by mentioning @cursor on a GitHub or Bitbucket PR or issue, from Linear, or through the API. Now they also pick up work on their own when an event comes in, such as activity on a PR they’re monitoring, a new message in a Slack thread they’re watching, or a scheduled task coming due. Custom modes, also part of the update, keep an agent focused on a single skill.

Slack access runs through Cursor’s app on Slack. The update came two days after Origin, Cursor’s git forge, shipped on August 17. Cursor says subscriptions are available only for cloud agents, for now.

No comments yet. Be the first.

Join the conversation

Sign in to leave a comment. It appears after moderation.