Products / Cursor Cloud Agents
cursor-cloud-agents
Cursor Cloud Agents
What version is Cursor Cloud Agents?
Cursor Cloud Agents current_version is 2026-11-05. last_updated is 2026-11-05. The catalog lists no channel versions for this product. Catalog generated_at is 2026-11-09T18:01:26+00:00. Always-on agents that pick up work from events and hold a goal. Catalog status is ga. Organization is cursor. Official source URL: https://cursor.com.
- id
- cursor-cloud-agents
- current_version
- 2026-11-05
- last_updated
- generated_at
- published_at (this UI deploy)
Features
Subscriptions
Monitor PRs, watch a Slack thread, or run scheduled tasks. Agents wake on events and can auto-subscribe to PRs they create.
/goal and /loop
Assign a long-lived objective (e.g. fix flaky tests and make CI green). Pair with /loop for recurring check-ins.
Subagents on their own machines
Subagents run on isolated VMs with clean project copies. Swarm them for independent tests.
Custom modes
Pin skills as always-on modes so agents stay focused. Select from the / menu.
Steering
Send a follow-up without interrupting the current turn. Press return twice or Send now.
Builds
Ready-to-use copies of the dev environment. Agents boot ~3× faster to first token; included with Cloud Agents.
Conversation hooks
Observe and control prompts, responses, thinking, subagents, compaction, and turn completion.
Start from scratch
Cloud Agents can start without a connected GitHub or other SCM. Cursor creates an Origin repo in the background; save with Create repo when ready.
Live preview
Port-forwards the cloud agent environment to the browser for preview and design mode.
Vercel publish
Connect a Vercel account and publish the agent build to a live URL.
Self-hosted machines
Run cloud agents on machines in your network. My Machines connects a laptop or VM; team pools scale workers on demand with hibernate and restore. Integrates with AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B. Self-hosted workers support computer use on Linux and Mac.
Projects
Long-running work with a coordinator agent that plans and delegates to implementing agents. Shared context files sync across cloud and local machines; runs on a cloud computer when the laptop is closed.
Rollouts
Change monitor on every pull request: writes a monitoring plan, tracks deploys per environment, and reports verified healthy, regression detected, or inconclusive. Connects Origin or GitHub, CD deploy events, and telemetry (Datadog and others).
Security Review
Posts one review comment per pull request reporting exploitable bugs (injection, auth bypass, secrets in source, SSRF, unsafe deserialization, vulnerable dependencies). Team rules enforce codebase-specific policies. Draft PRs are skipped.
Agent SDK
Agents as code: instructions.md, tools/, skills/, MCP connections, and channels. `agent-sdk dev` runs locally; `agent-sdk deploy` hosts on Cursor. Evals and `agent-sdk github replay` test PR-driven bots.
Live apps
Cloud agents scaffold web apps, provision Postgres and Cursor SSO auth, run security review, and publish to a chosen domain for team or public sharing.
Changelog
- Feature
Build Live Apps in Cursor
can · publish live apps from cloud agentssource · cursor.comAgents have lowered the cost of writing code, but most apps and tools that users build never make it off of localhost.
Now, you can build live apps directly in Cursor and share them with a link. Describe what you want to create and Cursor will handle the rest: build the app, set up a database, configure auth, and deploy it.
With this release, anyone in your org can now build useful tools for their work and share them with teammates. Update Cursor to try it out.
How it works
To get started, kick off a cloud agent and tell it explicitly that you want to build an app.
Cursor will scaffold the web app, spin up a Postgres database if needed, set up authentication behind Cursor SSO, and provision hosting. If the app needs to connect to your systems, like a data warehouse, Cursor will ask for the secrets it needs.
When you go to publish your app, you pick a unique domain and Cursor gets you back a live link.
At Cursor, users across sales, operations, legal, finance, and engineering are building internal apps. Some of the most useful ones are:
- Internal ops tools for event registration, account assignments, and desk seating
- Multimedia presentations for customers that combine slides, videos, and interactive demos
- Training, enablement, and onboarding experiences for new hires
- Live dashboards and tools for sales teams to understand their pipeline and opportunities
- Portals to manage engineering services
Cursor can deploy apps from new or existing repos across Cursor Origin and GitHub. Support for other git providers like GitLab is coming soon.
Controls and guardrails
When you publish an app, Cursor will run deterministic and agentic security checks to catch common issues, like secrets written in app files or exposed credentials. If a check fails, the agent tells you what it needs to fix. Nothing goes live until the checks pass and you explicitly publish the app.
Team admins can see every app and secret on the team. They can also add their own rules to the security review, approve publishes the review blocked, and unpublish any app.
Share with your team
Once the checks pass, Cursor deploys the app to the URL you chose. You can then share your app with specific people, groups, or your entire team, all behind Cursor sign-in. On individual plans, you can also share apps publicly.
You can also provision a Cursor API key if you want a script or Grok Bot to use your app.
Get started
This capability is now available on all paid plans with cloud agents enabled. Learn more by reading our docs.
- Feature
Agent SDK
can · Agent SDK GAsource · cursor.comThe Agent SDK is available today. It allows you to define an agent as a folder of code, test it with evals, and deploy it to Cursor or your own infrastructure.
Run
npx @cursor/agent-sdk init ./my-bot, thenagent-sdk devto start the bot locally with a playground. Pass--templateto start from a security reviewer, an owners-policy approver, a PR autofixer, or a Linear or Jira triager.Deploy agents wherever you need them
When you're ready to put an agent into use, you can deploy it to Cursor by running
agent-sdk deployfrom the project directory. The command builds the agent, gives it a URL, and starts it on our infrastructure. You can manage secrets and integrations from the dashboard, while continuing to use the same logs, evals, and playground available locally.Agents as code
An agent is a project.
instructions.mdis the prompt. Each file intools/is one typed action the model can call.skills/holds procedures the model loads on demand,mcp-connections/adds tools from MCP servers, andchannels/defines where the bot receives and answers messages.agent-sdk validatechecks the project andagent-sdk infoprints what was discovered.Channels
Agents wake on pull request, comment, and CI events from GitHub, GitLab, and Bitbucket; on mentions and DMs in Slack; on webhooks from any provider; and on a cron schedule. GitHub events pull through your Cursor account, so no public webhook URL is required. Slack is well-supported out of the box.
Each conversation keeps its own session and a complete record of every message and tool call. Follow-ups on a pull request or Slack thread resume the same session.
Evals
An eval sends a fixed message to the bot and asserts on what it did: which tools ran, with what input, and the shape of the reply. Run
agent-sdk evallocally or in CI.agent-sdk github replay <pr-url>turns a real pull request into signed webhook payloads and sends them to the bot, so GitHub-driven bots can be tested without waiting for a push. Add--dry-run --fixtures-dir fixtures/to save the payloads as eval fixtures.Get started
The Agent SDK is generally available today. Read the [docs](https://cursor.com/docs) and get started.
- Feature
Cloud Agent Canvases and Environment Improvements
can · cloud agents share canvasessource · cursor.comCanvases from cloud agents
Cloud agents can now build interactive canvases as part of their work. Share a finished canvas with your team by sending its link.
Environments API
The Environments API is now available in beta. Use it to programmatically create and manage the cloud environments your agents run in.
Larger, faster environments
Cloud agent environments now support up to 300 repositories. Large environments also load 5x faster.
- Feature
Remote control for local agents
can · remote-control local agents from iOSsource · cursor.comYou can now see and reply to the local agents running on your computer from the Cursor iOS app.
Get started
Remote Control is on by default for everyone except Enterprise organizations.
Download the Cursor iOS app and sign in. Computers on your account appear in the app automatically. Tap your computer in the app and approve your pairing request in the Cursor desktop app. Your local agents appear in a list. Tap one to see what it's doing or send it a message.
Agents keep running on your computer
Remote control doesn't move your agents anywhere. It keeps running on your computer, and the app connects to it. Your computer needs to stay on and online for remote control to work.
Keep your computer awake
To stop your computer from sleeping while you're away, turn on "Keep this computer awake" under Remote Control in Cursor's desktop settings. Your computer needs to be plugged in with the lid open.
For Enterprise teams
Remote control is on by default, except for Enterprise organizations. Enterprise admins can turn it on in Org settings > Security and identity > Remote control.
Remote control doesn't require cloud agents to work.
Remote control is available today in the Cursor iOS app.
- Feature
Rollouts and Security Review
can · ships Rollouts and Security Review botssource · cursor.comRollouts
Rollouts attaches a monitor to every pull request and watches the change as it deploys, reporting change health per environment: verified healthy, regression detected, or inconclusive.
When a pull request opens, Rollouts reads the diff and the systems it touches, then writes a monitoring plan as a PR comment. Edit the plan in the PR and Rollouts uses your version.
Rollouts wakes on deploy events for the change's commit and runs the plan against logs, metrics, and traces. It tracks each environment separately.
When Rollouts detects a regression, it names the change it suspects and notifies the author. Rollouts does not merge or roll back on its own today.
Rollouts connects to Origin or GitHub for source control, to your continuous delivery system for deploy events, and to Datadog and other telemetry providers for signals.
Security Review
Security Review reads every pull request in the context of the codebase and posts one review comment reporting exploitable bugs. Style and quality stay with Bugbot.
Enable it from the dashboard for the repositories you want reviewed. Draft PRs are skipped.
Security Review looks for injection across SQL, command, and template surfaces, authentication and authorization bypasses, secrets committed to source, SSRF and unvalidated redirects, unsafe deserialization, and dependency changes that introduce known vulnerabilities.
Each finding carries a severity, the attack path, and a proposed fix. Add team rules for your codebase and Security Review enforces them on every PR.
- Feature
Cursor Projects
can · ships Projects coordinatorssource · cursor.comProjects lets you take on larger bodies of work, such as a feature, a migration, or a full app. It maintains context over months of work, delegates tasks to thousands of subagents, and performs recurring work without being prompted.
Access Projects from the left-hand nav. The coordinator agent in a project doesn't write code itself; it plans the work, delegates it to agents that implement it, and brings the finished work back to you to check.
A Project runs on its own computer in the cloud, so closing your laptop doesn't stop it. When something needs testing on your machine, the coordinator spins up a local agent to run it there.
Each Project maintains a set of files that sync across every cloud and local machine its agents use.
Tell the coordinator agent to watch a Slack channel, run on a schedule, or follow all your PRs. Projects are available in beta and rolling out to all users starting today.
- Feature
Self-hosted machines
can · Cloud Agents run on self-hosted machinesCloud agents can run on self-hosted machines so codebase, build outputs, and secrets stay in your infrastructure. My Machines connects a personal laptop or VM; team pools are named queues that scale with demand and can hibernate idle workers. Integrations include AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B. Self-hosted workers support computer use on Linux and Mac.
source · cursor.com - Feature
Start from scratch, without a repo
can · Cloud Agents start without a repoCloud Agents can start without a connected GitHub or other SCM. Select Start from scratch in the repo picker; Cursor creates an Origin repo in the background. Create repo saves private or internal Origin repos. Live preview port-forwards the agent environment to the browser. Connect Vercel to publish a live URL.
source · cursor.com - Feature
Cloud Agents and harness improvements
Subscriptions, custom modes, subagents on isolated VMs, /goal, steering without interruption, and expanded conversation hooks.
source · cursor.com - Feature
Cloud Agents start 3× faster with Builds
can · Cloud Agents start 3× faster with BuildsBackground-prepared environments (clone, install, install script). Fallback to last successful build. Builds tab for logs and SHAs.
source · cursor.com