Anysphere profile

Canvases 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.

<figure><video src="https://cursor.com/marketing-static/changelog/cloud-agent-canvases-and-environments.mp4" controls preload="metadata"></video></figure>

Learn more about sharing canvases.

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.

Origin now integrates with over 20 apps for deployments, CI, code review, security, monitoring, and project management, from partners including Cloudflare, Linear, Sentry, and Socket Security.

Starting today, the marketplace is also open to public submissions, so any team building developer tools can publish an app for Origin.

Apps for your stack

The marketplace now includes apps for:

• **Deployments:** Cloudflare, Netlify, Render, Spacelift, and Vercel
• **CI:** Buildkite, CircleCI, CloudBees, Depot, EngFlow, Namespace, and RWX
• **Code review:** CodeRabbit, Greptile, and Tenki
• **Security:** Artemis Security, Semgrep, Socket Security, and Upwind
• **Monitoring:** Sentry
• **Project management:** Linear

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/origin-apps-QQ9ZPw6HtXmhbhtleevXGQ5xw1ncs1.png" loading="lazy" alt="Origin App Marketplace listing apps across deployments, CI, code review, security, monitoring, and project management" /><figcaption>Origin App Marketplace listing apps across deployments, CI, code review, security, monitoring, and project management</figcaption></figure>

Publish to Marketplace

To submit an app:

1. Create an app in your namespace. It stays private to your namespace while you build.
2. Build against the Origin API. Apps authenticate with an app JWT and installation access tokens, receive webhook events, and write back check runs, pull request comments, and reviews.
3. Make the app public, then submit it from the app's page with a slug, suggested tags, and a demo video. The video should show install, uninstall, and your core product flows.
4. We review the submission and list the app once it's approved.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/origin-submit-marketplace-XuhYvHQND62RTK4kNpUTDga6SIdPyu.png" loading="lazy" alt="Submitting an app to the Origin App Marketplace" /><figcaption>Submitting an app to the Origin App Marketplace</figcaption></figure>

Get started

Try the apps in the Origin App Marketplace today.

Want to build an Origin app? Start with the publishing guide and the Origin API reference.

The Origin Apps plugin can also answer questions from the live Origin API docs and plan a port to Origin for an app you already run.

You 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.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/remote-control-cl-pezewO3SZRrIQxMNaTzdpsP9TD1ChS.png" loading="lazy" alt="Remote Control for local agents in the Cursor iOS app" /><figcaption>Remote Control for local agents in the Cursor iOS app</figcaption></figure>

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.

Today we're launching two Cursor bots for the last mile of shipping code. Rollouts watches every change as it deploys and reports its health per environment. Security Review reports exploitable bugs on every pull request.

Both are available today on Teams and Enterprise plans.

Rollouts

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. It's the Cursor version of Firetiger Change Monitors, rebuilt with the Bot Development Kit.

Enable it from the dashboard and connect source control, your deploy system, and your telemetry provider. Rollouts starts watching on the next pull request.

Monitoring plans

When a pull request opens, Rollouts reads the diff and the systems it touches, then writes a monitoring plan as a PR comment. The plan lists the risks it identified, the effect the change is meant to have, the signals it will check, and any gaps in instrumentation that would make the change hard to verify. Edit the plan in the PR and Rollouts uses your version.

Deploy tracking

Rollouts wakes on deploy events for the change's commit and runs the plan against your logs, metrics, and traces. It tracks each environment separately, so a change can be verified in staging and still flagged in production. Rollouts checks the change's intended effect alongside error and latency signals, and reports back on the PR when it reaches a verdict.

Regressions

When Rollouts detects a regression, it names the change it suspects and notifies the author. Depending on configuration, it can also open a revert PR for review or hand the finding to a cloud agent for a fix. Rollouts does not merge or roll back on its own today.

Integrations

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. Feature flag integration is coming soon.

Security Review

Security Review is available today. It reads every pull request in the context of the codebase and posts one review comment reporting exploitable bugs. Style and quality stay with Bugbot.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/security-review-N8azgyLevr8FvNIRqJN6hk71os2Oxu.png" loading="lazy" alt="Security Review comment on a pull request reporting an exploitable bug with a severity and proposed fix" /><figcaption>Security Review comment on a pull request reporting an exploitable bug with a severity and proposed fix</figcaption></figure>

Enable it from the dashboard for the repositories you want reviewed. Draft PRs are skipped.

What it reports

Security Review looks for injection across SQL, command, and template surfaces, along with authentication and authorization bypasses, including checks that a refactor stopped running. It also flags secrets and credentials committed to source, SSRF and unvalidated redirects, unsafe deserialization, and dependency changes that introduce known vulnerabilities. It traces where user input enters and what it passes through.

Findings

Each finding carries a severity, the attack path, and a proposed fix. Dismiss one with a reason and Security Review won't raise it again on that PR.

Team rules

Add rules for your codebase, such as which client external calls must go through or which tables are never queried from a request handler, and Security Review enforces them on every PR.

Get started

Rollouts and Security Reviewer are available today on Teams and Enterprise plans. Enable either bot from the automations tab.

For the next 10 days, we're including usage credits so teams can try Rollouts on real changes. Teams and Enterprise customers receive credits for roughly 50 and 500 changes, respectively.

Today we're launching Projects in Cursor. Projects 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. Coordinators create and manage agents on your behalf, running as many in parallel as the work needs.

Powered by Cloud Agents

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.

Shared context

You shouldn't have to onboard an agent every time you start a task. Each Project maintains a set of files that sync across every cloud and local machine its agents use. Agents add research and artifacts, along with what they learn about the codebase and how you prefer work to be done. If one agent figures out how to test a service, for example, every future agent can use those instructions. The shared context grows with the Project, making the coordinator more effective over time.

Subscriptions

Tell the coordinator agent to watch a Slack channel, run on a schedule, or follow all your PRs. This way it can take action based on signals it detects, without waiting for your prompt.

Connect Slack and point it at a bug-report channel, and it starts delegating each time a bug comes in.

Projects are available in beta and rolling out to all users starting today.

Cursor supports **self-hosted machines**, which let you keep tool execution entirely in your own network.

Your codebase, build outputs, and secrets all stay on internal machines running in your infrastructure, while the agent handles tool calls locally.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/uploads/remote-machines-QjJ0ZzGDelSdT7v2CXDdh0BQHqjmH0.png" loading="lazy" alt="Run on menu showing Remote Machines with self-hosted options lambda-test, cloud-demo, and jacks-desktop" /><figcaption>Run on menu showing Remote Machines with self-hosted options lambda-test, cloud-demo, and jacks-desktop</figcaption></figure>

Dynamic pool scheduling

**My Machines** connects a single laptop or VM to your account for personal workflows.

**Team pools** are named queues of workers for a team or enterprise. Capacity can grow as requests arrive and shrink when workers disconnect, so your self-hosted machines can scale with demand. Pools are not tied to one repository: name the pool, and any available worker can claim the request.

Pools can also hibernate idle machines, then restore within a reconnect window when a follow-up arrives, so you don't keep expensive capacity warm just for the next prompt.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/uploads/pools-mNNea8rJyNxaBuz7rSVT2SJOKkRsmv.png" loading="lazy" alt="Cloud Agents dashboard listing Self-hosted Machines pools with active and idle worker counts" /><figcaption>Cloud Agents dashboard listing Self-hosted Machines pools with active and idle worker counts</figcaption></figure>

Run on your sandboxes

Cloud agents can now execute on infrastructure you already use, including from AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B.

Computer use on Linux and Mac

Self-hosted workers now support computer use on Linux and Mac. With the right desktop packages, an agent can click, type, take screenshots, and drive the browser. You can watch its desktop or take control from Cursor.

Cloud Agents no longer require a connected GitHub or other third-party SCM provider to get started. Prompt from the get-go, then save your work to a Cursor Origin repo.

Get started

Select **Start from scratch** in the repo picker, then prompt the agent. In the background, Cursor creates an Origin repo for you.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/start-from-scratch-QflXlxizUwAvBbal0Kst46I0mEZT93.png" loading="lazy" alt="Start from scratch in the repo picker" /><figcaption>Start from scratch in the repo picker</figcaption></figure>

Turn it into a real repo, whenever you want

Once the agent's build is to your liking, click the **Create repo** button to save your work in an Origin repo. Choose a custom name or pick one of the suggested ones, then set the visibility to private or internal. You'll get a fully scaffolded Origin repo, ready to share or keep building on. Navigate to the Codebase tab to find your repo and access your project.

A live preview, right in the browser

Cursor now port-forwards your cloud agent's live environment straight to your browser, so you can preview it and use tools like design mode.

Publish your work

Connect a Vercel account and hit publish to get a live URL for what you built.

A Vercel account is required to use the publish feature.

Get started today.

We're continuing to improve cloud agents and the Cursor harness so always-on agents can operate as a system, building and shipping software on their own without the need for intervention at each loop.

With this release, cloud agents can automatically pick up work in response to events, hold a goal until it's met, and stay on course through long-running sessions.

Subscriptions

Cursor can now monitor your PRs, watch a Slack thread, or run scheduled tasks. Cursor Agent subscribes to an event source (a thread or conversation) and wakes when something happens. Subscriptions are available for cloud agents only, for now.

Cloud agents automatically subscribe to PRs they create and drive them to completion, fixing CI and addressing bot comments. In Slack, ask `@cursor check back in an hour and keep going until that feedback is in`.

<figure><video src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/2026-08-13-changelog-subscriptions-ObbzEOzAUiaMhh70DUYG6fJZwv2SQ8.mov" controls preload="metadata" loop></video></figure>

Custom modes

Use any skill as a Custom Mode: a skill that stays pinned in the chat. Custom modes keep agents focused on a skill - you can think about it like "always on" skills.

From `/`, pick a skill and press ⌥⏎ (Mac) or Alt+Enter (Windows), or choose **Use as Mode**.

<figure><video src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/2026-08-13-changelog-sticky-skills-GyjHI2f0MGVFngQBebLBnlQjEkkxQm.mp4" controls preload="metadata" loop></video></figure>

Subagents on their own machines

Subagents can now run on their own virtual machines. Each gets an isolated copy of the project with clean context in its own cloud environment.

Have subagents test the parent agent's changes in fresh environments or swarm independent fixes without collisions. Try `run a swarm of subagents to test my app for bugs, each in its own environment`.

<figure><video src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/2026-08-13-changelog-subagents-YD3SIKspySs8zoib2kY7RAPA9Injca.mp4" controls preload="metadata" loop></video></figure>

/goal

Use `/goal` to give the agent a long-lived objective to work towards until it's fully complete.

Try `/goal fix all flaky tests and make CI green` in a new chat. Pair it with a custom mode to follow a playbook, or `/loop` for recurring check-ins.

<figure><video src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/2026-08-13-changelog-goal-CPDEcewlxhbdqRa131C8yZjhDdOGzb.mp4" controls preload="metadata" loop></video></figure>

Steering improvements

You can now send a message to steer the agent while it's working without interruption. Follow-ups wait for the next tool call instead of cutting the agent off mid-action.

Type a follow-up and hit Send now, or press ⏎ twice.

Cursor can now host your code.

Origin begins rolling out today in early beta on all paid plans. We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync. Agent-native features ship soon.

Origin Repos

The new **Codebase** tab is home for Origin repos.

Click **+New** to create a new repo and name it. Once you do, a page shows you how to install the CLI, with commands for how to clone a repo or push a local project. Push, and your code is hosted on Origin.

For Origin-hosted repos, Origin is the source of truth. Pushes land on Origin, and GitHub is not in the path.

Name your codebase when you create your first repo. That name becomes part of every repo's URL: cursor.com/codebase/`acme-corp`.

Bring your GitHub repos

Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync. Select one and Cursor pulls it in. You choose what gets synced and can disconnect a repo at any time. Anyone with read or write access to a synced repo can view it in Cursor too.

Synced repos update in real time. Browse, search, and pull from the copy in Origin. For synced repos, GitHub stays the source of truth: pushes keep going to GitHub, and Origin mirrors the result. Icons next to each repo name tell you which ones Cursor hosts and which came from GitHub.

Pull requests

Every repo has pull requests. Open one to see the timeline, commits, checks, and files changed. Review the diff, leave comments, and merge.

Pull requests on synced repos sync both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor within seconds. Got a review assigned to you on GitHub? Review and merge it from Cursor.

Agents in every repo

Your code, PRs, and agents are now in the same place. Ask Cursor questions about code you're browsing. It can answer, make changes, update PRs, or push a branch.

App extensions for Cursor repos

We're building an app ecosystem so your whole stack works seamlessly with Origin. Integrations with Vercel, Depot, and Buildkite are already available, with more coming soon.

Connect Vercel from a repo's **Apps** tab and every PR gets a preview deployment where you can test and make comments. Merge, and it ships to production. For CI, connect Depot or Buildkite. Both run your existing GitHub Actions workflows and Buildkite also runs its native pipelines.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/origin-apps-VXN2qUBlVUoZVFkdDCeojn1GkN4IIb.png" loading="lazy" alt="Vercel, Depot, and Buildkite apps connected to an Origin repo" /><figcaption>Vercel, Depot, and Buildkite apps connected to an Origin repo</figcaption></figure>

Settings

Every repo has settings. Check sync status for GitHub repos, manage who has access, and see which apps are connected.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/origin-settings-tipE1aGfr5qnTYJlRVBbwYwqsxfCSC.png" loading="lazy" alt="Origin repo settings showing sync status, access, and connected apps" /><figcaption>Origin repo settings showing sync status, access, and connected apps</figcaption></figure>

Origin is rolling out in early beta to all paid plan users starting today, except enterprise orgs whose admins opt out. Name your codebase and create your first repo.

Learn more in our docs or get started today.

Agents do their best work when they start in a ready environment: repos cloned, dependencies installed, and your install script already run.

This release introduces **builds**: ready-to-use copies of your development environment that Cursor prepares in the background. Agents boot into a ready environment instead of setting up from scratch each session. Builds are included with Cloud Agents at no additional cost.

Faster starts

Cursor runs a new build of your environment regularly. When a build succeeds, it becomes the environment future agents start from. Cursor keeps warm copies ready so the next agent does not wait. Internally, our environments now boot 10x faster, with 3x faster time to first token.

Use your install command for anything that can be prepared ahead of time. The start command still runs when you first prompt an agent and should focus on services that need to be fresh in the session.

More resilient agent runs

When a bad commit or dependency update breaks your environment, agents keep using the last successful build. The broken build never becomes active, you are notified of the issue, and your agents keep working while you debug in the background.

Build history and debugging

Each environment has a **Builds** tab in the Cloud Agents dashboard. You can inspect build status, logs, commit SHAs, and which build each agent run used. Agents can also inspect and manage builds using built-in tools.

Getting started

New environments use Builds automatically. For an existing environment, open it in the Cloud Agents dashboard, go to the **Builds** tab, and click **Enable Builds**. Or click **Run setup agent** first to test the migration and review any proposed config changes.

You can also trigger a Build manually, debug a failing Build with an agent, and control how stale Builds refresh with a configurable threshold.

Learn more in our announcement post and docs.

Cursor can now read, write, and act across your Google Workspace.

New plugins give coding agents direct access to Gmail, Google Drive, and Calendar, so you can pull context, draft and update files, and manage your inbox and calendar without leaving Cursor.

Install plugins to connect:

• **Google Drive:** search files and folders, open and download content, create and organize files
• **Gmail:** search and read mail, draft and send messages, apply labels and manage threads
• **Google Calendar:** read schedules, create and update events, find free time

Browse the new plugins in the Cursor Marketplace or install them from the Customize page in Cursor. Learn more in our docs.

Cursor for iPad is now available on all paid plans.

New to both iPhone and iPad: an inbox to stay organized, and a review experience that covers the full PR. Create, review, and merge from anywhere.

Built for the bigger screen

The iPad layout is rebuilt around the extra space. Sidebar chats stay pinned so you can watch several agents run at once. Split screen keeps a review open next to a chat, and file diffs render in full.

Markup gets more room to work too. Attach a screenshot, then tap to drop a comment at a specific point, or draw directly on the image with Apple Pencil.

A full review surface

On iPhone and iPad, the review screen now covers the full PR: comments, checks, and approvals. Add or change reviewers, read comments, and prompt the agent to resolve them. The whole path from agent output to merged PR now travels with you.

Inbox

An Inbox helps you and your agents stay organized. See what's in progress, what needs your attention, and which PRs are in review.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/inbox-43-WUi5D4anOQABnh7gqHuJgCky6upWm6.png" loading="lazy" alt="Inbox on Cursor for iPad" /><figcaption>Inbox on Cursor for iPad</figcaption></figure>

Additional improvements for Cursor on iPhone and iPad

• Bitbucket and Azure DevOps SCM support
• Multi-PR sessions: when one chat creates multiple PRs, you can now open every one of them, not just the last.
• Switch between teams that you belong to directly in the app

Download the Cursor App or read our docs to learn more.

We're introducing Cursor Start, a new ₹649 monthly plan for developers in India, making daily agentic development accessible and payment easy with local pricing and UPI.

Existing Free users in India can upgrade their plan from the dashboard. New users in India can visit cursor.com/signup and select the Start plan during onboarding.

Start bills monthly with auto-renewal and is available from July 28, 2026.

Cursor Start includes:

• **Generous access to Cursor models:** Grok and Composer, with enough usage to build with agents every day.
• **Always-on cloud agents** that build, test, and ship code while you keep working.
• **Cursor for iOS** with remote control, so you can launch and steer agents from your phone.
• **Plugins, MCP servers, hooks, and skills** to extend Cursor across your workflows.
• **Local pricing** at ₹649 per month, tax inclusive, billed in INR with UPI or card.

Learn more in our announcement and docs.

Auto mode is now powered by Cursor Router.

Cursor Router is our intelligent model router. It analyzes each request and sends it to the right model for the job. Frontier models handle work that demands them. Price-efficient models handle the rest.

Optimization modes

Select Auto, then choose how the router optimizes:

• **Intelligence:** Frontier quality, matching the most expensive and powerful models that might be out of reach for daily use.
• **Balance:** Strong quality, matching the frontier models that most people like to daily drive.
• **Cost:** Good quality, reaching the highest available intelligence while optimizing token spend.

Balance and Intelligence bill at the routed model’s rate. Each mode moves you along the cost-intelligence pareto frontier.

Admin controls

Admins can enable the router per team or group, restrict which optimization modes members can use, set the default mode, and allow or block underlying models.

Cursor Router is available across desktop, web, iOS, CLI, and our SDK. It is on by default for Teams plans. Enterprise admins can enable it from the dashboard.

Learn more in our announcement and docs.

Improvements

• Per-request classification by task type and complexity
• Optimization modes: Cost, Balance, and Intelligence
• Admin controls: per-team and per-group enablement, mode restrictions, default mode, and model allow and block lists
• Routed model can be displayed or hidden (hidden by default)
• Soft and hard enforcement options for standardizing on Auto
• Grok 4.5 required as a price-efficient routing option

Cursor in Slack now shares a plan before it starts, runs in multi-repo environments, and can work across channels and threads.

Interaction improvements

Cursor now responds with a plan before it begins, so you can jump in and redirect early. As it works, it updates its status so you can follow each step.

We also refined how Cursor's responses look in Slack. In-message buttons are gone, replaced by compact footer links. Tables, PRs, and artifacts now render more cleanly.

Multi-repo environment support

From Slack, Cursor can now start in a named multi-repo environment instead of a single default repository. If your frontend, backend, and shared code live in separate repos, Cursor reads your request and targets the environment that gives it access to all of them.

Mid-task, when Cursor needs a repo outside the current environment, it prompts you with a **Switch repository** button. Click it, choose the repo or environment, and Cursor picks up right where it left off.

Cross-channel workflows

Cursor can now read from and send messages to other Slack channels and threads. During a task, it can pull context from elsewhere in the workspace and post updates back in the original thread or the relevant channel.

Learn more in our Slack docs.

This release makes it easier to stay in flow with side chats that run alongside your main chat, the ability to search agent transcripts, and simplified project and repo pickers.

Side chats

Open a side chat to ask questions, explore ideas, and investigate tangents without interrupting your main agent conversation. Use `/side`, `/btw`, or the plus button at the top of the chat panel to create a new side chat that has context from the main chat.

Each side chat is a durable, full agent conversation that you can follow up on, revisit later, and at-mention to pull context back into the main thread.

By default, side chats focus on reading, searching, and answering. Use them to ask clarification questions, research alternatives without committing to a pivot, and sanity-check a decision while the main agent continues running.

Conversation search

Find past agent chats faster with search results that go beyond names and PR numbers. In the Agents Window, you can search agent transcripts from the command palette (Cmd+K). Cursor builds a local search index that scales search to thousands of conversations with snappy performance.

You can also search within an existing conversation using Cmd+F. Jump between matches, see a match counter, and keep searching as you scroll through long transcripts.

Redesigned project and repo pickers

We've simplified the project and repo pickers and made them more powerful. You can now stay in the picker for workflows that used to send you elsewhere. For example, you can create a project and connect GitHub, GitLab, or Azure DevOps without leaving the picker.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/redesigned-picker.png" loading="lazy" alt="Redesigned project and repo pickers" /><figcaption>Redesigned project and repo pickers</figcaption></figure>

Search is now scoped to where you're working—This Computer, Cloud, or a specific remote machine—instead of one global search box. You can also remove projects from Recents with one click.

New cloud agent hooks

Cloud agents already support team hooks around tool execution and file/shell work. We've added new hooks that let you observe and control the agent conversation itself: prompts, responses, thinking, subagents, compaction, and turn completion. See all the supported hooks in our docs.

New hooks like `beforeSubmitPrompt`, `afterAgentResponse`, `afterAgentThought`, `stop`, `subagentStart`, and more allow you to better observe output and reasoning, control subagents, and build self-correcting loops with cloud agents.

Picker Improvements

• Improved repo picker grouping with options under No Repo, On This Computer, and Cloud.
• Added the "Run on" picker that shows where your agent can run (Cloud, This Computer, or Remote Machines) and drills into the relevant choices (environments, local options, and so on) from there.
• The branch picker opens on your default branch and recently used branches instead of a long flat list, with search for everything else.
• Removed the Home concept so working without a repo is an explicit No Repo choice.
• Combined all remote options—your machines, team pools, and existing remote workspaces—into one searchable Remote Machines menu.
• Multi-repo and multi-root selection is a Select Multiple toggle inside the Cloud and This Computer flyouts, replacing the separate Set Up Workspace builder.
• Moved search to the top of the menu.
• Simplified the footer.
• Added the ability to find the No Repo option by typing `none` or `no repo`.
• If a repo exists only in the cloud, the picker suggests cloning it locally.
• Added clearer section dividers.
• Added folder icons with a small cloud badge for cloud repos.
• Removed redundant `Current` tag in the branch list.

We've expanded team marketplaces to support Team MCPs and organization groups.

Team MCPs in team marketplaces

Admins can now configure Team MCP servers once and distribute them across cloud agents, the agents window, IDE, and CLI.

When an admin sets up Team MCP servers for cloud agents, they can make those same servers available in a team marketplace from **Dashboard -> Plugins & MCPs**. This allows members of the team to install approved integrations locally without configuring servers themselves.

Learn more in the docs on migrating existing Team MCPs.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/team-mcps.png" loading="lazy" alt="Team MCP servers" /><figcaption>Team MCP servers</figcaption></figure>

Marketplace access by organization group

Team marketplaces now support organization groups, in addition to team-level SCIM directory groups.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/marketplace-orgs.png" loading="lazy" alt="Marketplace organization groups" /><figcaption>Marketplace organization groups</figcaption></figure>

Under **Dashboard -> Plugins & MCPs -> Team Marketplaces**, restrict marketplace access to specific organization groups. Marketplaces that already use SCIM directory groups keep that configuration.

Get started in the Cursor dashboard.

Cursor for iOS is now available in public beta on all paid plans. Launch and manage always-on agents from anywhere.

Cloud agents on mobile

Open the Cursor mobile app, choose a repo, and launch an agent the same way you would on the desktop app. Pick any frontier model, describe ideas out loud with voice input, and use slash commands to guide Cursor in the right direction.

Cloud agents run in isolated virtual machines with full development environments to test, verify, and demo work. Move sessions from local to cloud to keep them running with your laptop closed.

Remote Control

Use Remote Control in the Agents Window to take an agent you're running on your computer and keep directing it from your phone.

<figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/remote-control.png" loading="lazy" alt="Remote Control" /><figcaption>Remote Control</figcaption></figure>

You can also turn on a setting to keep your computer awake, so your machine stays reachable while you're away from your desk.

On Teams and Enterprise plans, admins must enable Remote Control from the Cursor Dashboard.

Live Activities and push notifications

Track the status of your agents with Live Activities on your lock screen. Get push notifications when an agent finishes, needs input, or is ready for review.

Artifacts and SCM

Review demos, screenshots, logs, and diffs from your phone. Leave follow-up instructions, or merge the PR directly from the app.

Download Cursor for iOS to start building from your phone. Read our announcement or the docs to learn more.

Plugins, skills, and MCPs let you customize Cursor for your workflows. The new Customize page brings them into one place.

You can now add and manage plugins, skills, MCPs, subagents, rules, commands, and hooks at the user, team, or workspace level, and even bring your own custom MCPs.

Marketplace leaderboard

Cursor now shows you a leaderboard of the most popular plugins, skills, and MCPs across your team.

Add any to your setup with one click from the new Customize page and extend Cursor for your workflow.

Plugin canvases

Plugins now support prebuilt canvases: shared setup templates your team can open and reuse.

Use the Hex Canvas to build data visualizations.

Use the Atlassian Canvas to see a realtime view of all our issues, projects, and documents.

New Team Marketplaces

Team marketplaces now support imports of plugin repositories from GitLab, BitBucket, or Azure DevOps so you easily add plugins and distribute them to your team.

Learn more in our docs.

Cursor Automations save you time by automating repetitive tasks with always-on agents. This release introduces the **/automate** skill, new triggers for GitHub and Slack, and support for computer use.

/automate skill

Use **/automate** to create an automation directly in your local agent session.

Describe the task you want to automate in plain language and Cursor will configure the triggers, instructions, and tools for you.

An emoji trigger for Slack

React to any Slack message with a designated emoji to kick off an automation. At Cursor, we use this to trigger specific automations right from Slack.

New GitHub triggers

Automations now support five additional GitHub triggers:

• **Issue comment:** when a comment is made on a non-PR issue
• **PR review comment:** when an inline comment is left on a pull request diff
• **PR review submitted:** when a PR review is submitted
• **Review thread updated:** when a review thread on a pull request is marked resolved or unresolved
• **Workflow run completed:** when a GitHub Actions workflow run finishes on a pull request or branch

We've added new templates for triaging failed GitHub actions and auto-fixing PR review comments to the Cursor Marketplace to help you get started.

Computer use tool for automations

Cloud agents kicked off by automations can now use their own computers to produce demos or artifacts of their work.

The computer use tool is enabled by default for every automation, just tell the agent to include a demo of its work in your instructions.

To get started, update to the latest version of Cursor. Learn more in our docs.

Improvements (3)

• Automations can now be saved in an incomplete state, so you can navigate away to set up an MCP auth without losing your progress
• Automations can now open PRs by default; so you no longer have to specify that tool in the UI
• You can now delete memory files in the UI, or prompt your automation to delete outdated memories when it runs