LoginSign Up
← Back to all sparks
C

Cursor

INFRA · APIS
Velocity8.8

Cursor builds the full software delivery loop: ship, monitor, host, and secure inside one platform.

cloud-agentsdevops-automationsecurity-reviewagentic-platformself-hostedorigin-repos
◆Current state
Cursor has expanded from a code editor into a full software delivery platform. In six weeks it launched Projects (coordinator agents delegating to thousands of subagents in the cloud), Origin (its own git hosting with bidirectional GitHub sync and PR workflows), Rollouts (per-deployment health monitoring per environment), and Security Review (per-PR exploitable bug reporting). The product can now receive events, delegate implementation in parallel, host code, and watch changes in production.
◆Where it's heading
The arc is closing every gap in the write-review-deploy-monitor loop. Rollouts positions Cursor as a post-merge player — not just a code generator — by watching its own output in production. Origin bets that owning the SCM layer unlocks agentic features impossible to build on top of a third-party repo. The next open gap is auto-remediation: Rollouts explicitly says it doesn't revert today, and Security Review doesn't yet fix-and-merge high-confidence findings.
◆Prediction
Auto-remediation lands next: Rollouts will gain the ability to open revert PRs autonomously, and Security Review will gain fix-and-merge for high-confidence findings. Pricing will shift toward agent-action units or compute-time at enterprise scale, since per-seat models undersell the value when customers run thousands of subagents.

◆Recent moves

  1. 3d ago

    # Rollouts

    ⚡ SPARK

    Rollouts closes the last gap in Cursor's agentic delivery loop: production observability. The monitor writes a risk-and-signal plan when a PR opens, tracks the change per environment during deploy, and flags regressions by name — the first time Cursor has eyes on what happens after an agent ships code. Security Review ships in the same release and posts one comment per PR with exploitable bugs, attack paths, and proposed fixes.

    View source ↗
  2. 16d ago

    # Powered by Cloud Agents

    ⚡ SPARK

    Projects formalizes the coordinator-subagent pattern that was implicit in earlier cloud agent releases. The coordinator never writes code itself — it plans, delegates to subagents running in parallel, and brings results back for review. Shared context that persists across agents and sessions is the architectural bet: each agent builds on what the last one learned, so the workspace gets more effective over time.

    View source ↗
  3. 24d ago

    Self-hosted pools, external sandboxes, and Linux/Mac computer use

    ⚡ SPARK

    Self-hosted machine pools gained dynamic capacity scaling and integrations with eight external sandbox providers — AWS Lambda, Modal, Vercel, Daytona, and others. Agents no longer need dedicated warm machines; pools scale on demand and can hibernate idle workers. Computer use on Linux and Mac extends the self-hosted surface to full desktop automation, including browser control.

    View source ↗
  4. 1mo ago

    Cloud Agents drop the GitHub requirement; live preview and Vercel publish added

    Cursor removed the GitHub prerequisite for Cloud Agents: you can now prompt immediately and create an Origin repo from the result, reducing time from first prompt to a shareable artifact. Live browser preview via port-forwarding and a Vercel publish button complete the path from agent output to deployed URL without leaving the product.

    View source ↗
  5. 1mo ago

    # Subscriptions

    ⚡ SPARK

    Subscriptions transform Cursor from a prompt-and-respond tool into an event-driven agent: it can now monitor PRs it created through CI, watch a Slack channel for bug reports, and run on a schedule. Paired with /goal for long-lived objectives and subagents running in isolated VMs, the product now has a persistent operational mode that runs without user prompting.

    View source ↗
  6. 1mo ago

    # Origin Repos

    ⚡ SPARK

    Origin is Cursor's bet that owning the SCM layer is necessary to ship the next generation of agentic features. By hosting repos, syncing with GitHub bidirectionally, and building PR workflows into the same surface as agent chat, Cursor removes the handoff friction that comes with round-tripping through a separate git provider. Vercel, Depot, and Buildkite integrations connect CI/CD to the same layer from day one.

    View source ↗