Cursor Adds Projects (Multi-Agent, Beta) and Self-Hosted Machines
In September 2026 Cursor launched self-hosted machines (2 Sept), which keep agent tool execution on your own laptops, VMs or sandboxes, and Projects (10 Sept, beta), where a coordinator agent plans long-running work and delegates it to parallel agents that can react to Slack, schedules and pull requests.
Cursor shipped two features in September 2026 that push it further from "AI editor" toward "agent platform". (What Is Cursor?)
Self-hosted machines (2 September)
Cursor's cloud agents can now run their tool execution on machines you control, so code, build outputs and secrets stay inside your network:
- "My Machines" connects a single laptop or VM for personal use.
- Team pools scale with demand and can hibernate idle machines.
- Cloud agents can also run in your own sandboxes — Cursor names AWS Lambda, Modal and E2B as examples.
- Self-hosted workers support computer use on Linux and Mac.
This answers the most common enterprise objection to cloud agents: "our code can't run on someone else's machines."
Projects (10 September, beta)
Projects are for larger, longer efforts — a feature, a migration, a full app build over weeks or months:
- A coordinator agent plans the work and delegates implementation to other agents running in parallel. Cursor stresses that the coordinator "doesn't write code itself".
- Projects run in the cloud and share context files across machines.
- Subscriptions let a project react to the outside world: watch a Slack channel (say, a bug-report channel, delegating each new bug), run on a schedule, or follow your pull requests.
It's rolling out in beta to all users.
How it compares
The pattern is converging across tools:
| Cursor | Claude Code | Codex | |
|---|---|---|---|
| Parallel agents | Projects (coordinator + workers) | Subagents, agent teams, background sessions | /agents view, cloud tasks |
| Runs on your infrastructure | Self-hosted machines | Your machine, self-hosted environments | Local CLI |
| Reacts to events/schedules | Project subscriptions | Routines (schedule, API, GitHub) | Scheduled and automatic reviews |
(Claude Code Background Sessions, Claude Code Routines, OpenAI DevDay 2026: Codex)
What it means for you
- Cursor users on teams: self-hosted machines may unblock cloud agents in regulated environments.
- Anyone using multi-agent features: parallel agents multiply usage and review load. Split work into well-defined chunks and review each branch properly. (Review AI-Generated Pull Requests)
Source: Cursor changelog
EasySpawn takes the "your own machine" idea one step further: a persistent server per project where Claude Code, your app and your database live together. See how it works or join the waitlist.
Related: Claude Code vs Cursor · Cursor vs Windsurf · Claude Code in Cursor · Cursor Remote Control and Rollouts
Keep reading
Cursor: Remote Control for Local Agents, Plus Rollouts and Security Review Bots
Cursor's iOS app can now show and reply to agents running on your own computer (6 October 2026), without cloud agents. Earlier, on 23 September, Cursor launched Rollouts, which monitors a pull request from merge to production and flags regressions, and Security Review, which posts exploitable-bug findings on each PR, for Teams and Enterprise.
What Is Windsurf? The AI Code Editor, Now Called Devin Desktop
Windsurf was an AI-first code editor built on VS Code, known for its Cascade agent and Tab completions. Cognition bought it in 2025 and renamed it Devin Desktop in June 2026. What it is, what changed, how it compares with Cursor and Claude Code, and what existing users should know.