LoginSign Up
← Back to all sparks
C

Cursor

INFRA · APIS
Velocity8.8

Cursor launches Projects: a coordinator agent that runs thousands of subagents in the cloud indefinitely.

multi-agentcloud-agentsautonomous-devcode-hostingenterprise-infra
◆Current state
Cursor has moved well past AI code editor into multi-agent development infrastructure. It now coordinates parallel subagents on cloud machines, hosts code natively via Origin Repos, and maintains persistent project context that grows across sessions. The Projects launch adds a coordinator layer that can delegate tasks to thousands of subagents, run without a local machine, and react to external triggers like Slack or GitHub PRs.
◆Where it's heading
Every release since mid-2026 has added a new layer of the autonomous-software-pipeline stack: code hosting (Origin Repos), always-on event-driven agents (Subscriptions), parallel subagent execution (team pools, per-VM isolation), and now a coordinator agent that owns long-running Projects end-to-end. The pattern is consistent — each release removes a human touchpoint that previously required manual intervention.
◆Prediction
The next move is likely billing and governance for agent-compute at scale. Projects running thousands of parallel subagents implies compute costs that don't fit per-seat pricing; enterprise contracts around agent-hours or compute credits are the natural next step, especially with the self-hosted pool infrastructure already in place.

◆Recent moves

  1. 6d ago

    Cursor launches Projects: coordinator-led multi-agent development

    ⚡ SPARK

    Projects is the most architecturally significant release in Cursor's history: a coordinator agent that plans work, delegates to thousands of parallel subagents, and runs continuously in the cloud without human prompting. It adds shared context that accumulates across agents and Slack/schedule-based subscriptions for always-on operation — completing the transition from editor to autonomous development platform.

    View source ↗
  2. 14d ago

    # Dynamic pool scheduling

    Dynamic pool scheduling brings enterprise-grade infrastructure controls to Cursor's self-hosted machine offering: auto-scaling team pools, hibernation for idle workers, and support for sandboxes from AWS Lambda, Coder, Modal, Vercel, and others. Computer use (click, type, screenshot) on Linux and Mac self-hosted workers rounds out the feature. This is the infrastructure layer that makes Projects and large-scale agentic workloads viable at enterprise scope.

    View source ↗
  3. 20d ago

    Cloud Agents no longer require a GitHub connection to start

    Cloud Agents no longer require a connected GitHub account to start — a meaningful friction reduction that lets users prompt first and wire up source control later. The addition of live browser previews and one-click Vercel publishing shortens the feedback loop from agent output to deployed URL, complementing the Origin Repos and Projects direction.

    View source ↗
  4. 28d ago

    # Subscriptions

    ⚡ SPARK

    Subscriptions — cloud agents that wake on PR events, Slack messages, or a schedule — moved Cursor from reactive tool to proactive system. Combined with /goal for long-running objectives and per-VM subagent isolation, this release was the architectural turning point that made the Projects coordinator possible. Every autonomous capability in the Sept 2026 launch was seeded here.

    View source ↗
  5. 1mo ago

    # Origin Repos

    ⚡ SPARK

    Origin Repos put Cursor in the code-hosting business: native repos, pull requests, GitHub sync, and agents embedded directly in the repo context. Entering a market dominated by GitHub is audacious on its own; the real play is tighter agent-repo integration — agents that can read, push, review, and merge without leaving the Cursor environment.

    View source ↗
  6. 1mo ago

    # Faster starts

    The Builds feature pre-warms development environments so agents don't spend session time on setup: 10x faster environment boots and 3x faster time to first token, with automatic fallback to the last successful build if an update breaks the environment. At the velocity Cursor is shipping agentic features, reducing per-session initialization cost is directly load-bearing for Projects-scale workloads.

    View source ↗