Skip to main content
Cursor

Cursor

Complete Changelog

Visit Website

AI-first code editor

Complete changelog with every version since the first release.

Latest Version:2026-09-10
Total Releases:80
Source:Web Changelog

Releases (80)

2026-09-10

Cursor Projects

September 10, 2026

  • •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.
  • •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.
  • •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.
  • •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.
2026-09-02

Self-hosted machines

September 2, 2026

  • •Your codebase, build outputs, and secrets all stay on internal machines running in your infrastructure, while the agent handles tool calls locally.
  • •Run on menu showing Remote Machines with self-hosted options lambda-test, cloud-demo, and jacks-desktop
  • •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.
  • •Cloud Agents dashboard listing Self-hosted Machines pools with active and idle worker counts
  • •Cloud agents can now execute on infrastructure you already use, including from AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B.
  • •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.
2026-08-27

Start from scratch, without a repo

August 27, 2026

  • •Select Start from scratch in the repo picker, then prompt the agent. In the background, Cursor creates an Origin repo for you.
  • •Start from scratch in the repo picker
  • •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.
  • •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.
  • •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.
2026-08-19

Cloud Agents and Cursor Harness Improvements

August 19, 2026

  • •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.
  • •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.
  • •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.
  • •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.
  • •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.
  • •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.
2026-08-17

Origin Code Hosting

August 17, 2026

  • •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.
  • •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.
  • •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.
  • •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.
  • •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.
  • •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.
  • •Vercel, Depot, and Buildkite apps connected to an Origin repo
  • •Every repo has settings. Check sync status for GitHub repos, manage who has access, and see which apps are connected.
  • •Origin repo settings showing sync status, access, and connected apps
2026-08-13

Cloud Agents Start 3x Faster with Builds

August 13, 2026

  • •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.
  • •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.
  • •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.
  • •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.
  • •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.
2026-08-03

Google Workspace Plugins

August 3, 2026

  • •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
2026-07-29

Cursor, now on iPad

July 29, 2026

  • •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
2026-07-28

Cursor Start

July 28, 2026

  • •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.
2026-07-22

Cursor Router

July 22, 2026

  • •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.
  • •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
2026-07-17

Improvements to Cursor in Slack

July 17, 2026

  • •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.
  • •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.
  • •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.
2026-07-10

Side Chats and Conversation Search

July 10, 2026

  • •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.
2026-06-30

MCPs and Organizations in Team Marketplaces

June 30, 2026

  • •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.
  • •Team MCP servers
  • •Team marketplaces now support organization groups, in addition to team-level SCIM directory groups.
  • •Marketplace organization groups
  • •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.
2026-06-29

Cursor Mobile App for iOS

June 29, 2026

  • •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.
  • •Use Remote Control in the Agents Window to take an agent you're running on your computer and keep directing it from your phone.
  • •Remote Control
  • •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.
  • •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.
  • •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.
2026-06-22

Customize Cursor

June 22, 2026

  • •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.
  • •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.
  • •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.
  • •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.
2026-06-18

Improvements to Cursor Automations

June 18, 2026

  • •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
  • •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
2026-06-17

Cloud Environment Setup and Cloud Subagents in Agents Window

June 17, 2026

  • •Cursor can now help you set up your dev environment in the cloud in less than 10 minutes. You can watch the agent's progress in a shared terminal session as it handles setup tasks like installing dependencies.
  • •Your environment is captured in a reusable snapshot, so future cloud agents start up faster with the ability to test changes by running your software. It can iterate over long time horizons until outputs are verified. This benefits your entire team when committed to .cursor/environment.json.
  • •Cloud environment setup
  • •Use /in-cloud to spin up a cloud subagent in its own VM to work on the next task you submit. It runs on its own VM and branch, so your local workspace stays clean and responsive.
  • •This is especially useful for isolating long-running or parallel work like fixing CI, investigating an issue, or exploring a codebase while you keep working locally.
  • •You can also ask a cloud subagent to babysit a PR by clicking on the quick-action pill or using /babysit. The cloud agent will iterate remotely to prepare your PR for merge without tying up the local session.
  • •The cloud subagent can run in the background without interrupting the parent agent, which can continue to run locally or in the cloud.
  • •Move agent sessions more reliably between your local computer and the cloud. You can offload long-running work from your machine and run as many cloud agents in parallel as you want. Pull a cloud agent back down to local to test changes yourself.
  • •Handoff between local and cloud
2026-06-10

Bugbot is now over 3x faster, 22% cheaper, and finds 10% more bugs

June 10, 2026

  • •Bugbot is now over 3x faster, 22% cheaper, and finds 10% more bugs per review.
  • •These performance gains are made possible by progress we've made training Composer 2.5, which now powers Bugbot. Bugbot respects model block lists, and speed and performance can vary depending on your configuration.
  • •You can now run Bugbot and Security Review with /review before pushing code. /review prompts you to choose which agents to run, or use /review-bugbot and /review-security directly.
  • •/review also syncs with Bugbot on GitHub and GitLab. If you run /review and then open a PR with the same diff, Bugbot recognizes it, skips the review, and leaves a comment noting it has already reviewed that diff.
  • •Available in Cursor 3.7+ and on cursor.com/agents, with support in CLI coming soon.
  • •You can now configure Bugbot to only review what's new since the last review, keeping feedback focused on your latest updates.
  • •Learn more in our docs.
2026-06-05

Design Mode Improvements

June 5, 2026

  • •Click on two or more elements together in the browser. Cursor sees the selected elements, their code, the surrounding layout, and the visual relationships on the page.
  • •Ask the agent to make one match the other, remove repeated content, or adjust a group of components at once.
  • •Narrate changes through the Design Mode overlay. The mic stays available while an agent is mid-run, so you can queue the next change by voice without waiting for the previous one to finish.
2026-06-04

Custom stores, custom tools, and auto-review for the Cursor SDK

June 4, 2026

  • •Run correlation: Every send() now carries a platform-generated requestId, exposed on Run and RunResult and persisted across the in-memory, SQLite, and JSONL stores. Tie a script or CI run to backend logs, analytics, and support threads without inferring it from agentId.
  • •Reliable `wait()` on local runs: Local runs no longer resolve wait() before the terminal result is written. Hydration keeps refreshing until the run reaches a final state, so automation reads a complete result.
  • •Safe checkpoints on dispose: Disposing a local agent no longer removes checkpoint data when a root reference is missing but checkpoint blobs still exist. The agent directory is only cleared when there's genuinely nothing left to keep.
  • •Cloud streaming over HTTP/1.1: Cloud agent sessions now stream correctly on HTTP/1.1 transports used by some proxies, older Node fetch stacks, and certain CI images. HTTP/2 behavior is unchanged.
  • •Lighter import: Importing @cursor/sdk no longer eagerly loads the full local agent stack. Cloud-only and type-only consumers skip the local runtime cost until the first local call, with no API change. The first local call pays a one-time import, then stays cached.
  • •Self-contained TypeScript types: Published .d.ts files no longer reference unpublished workspace packages. This fixes TS2305 and TS2307 errors under skipLibCheck: false and silent any on stream types like TurnEndedUpdate.
  • •Bundled ripgrep: Local shell runs use the bundled platform rg binary without modifying your global PATH. On Windows, prepending ripgrep no longer clobbers the Path variable.
  • •Composer 2 routes to Composer 2.5: SDK clients still pinning retired composer-2 slugs are routed to Composer 2.5 automatically, keeping fast variants intact, so older scripts keep running.
  • •Workspace-scoped `list_runs`: Client, AsyncClient, and Agent.list_runs take an optional cwd, and the bridge falls back to its launch workspace. This fixes spurious "agent not found" results when the bridge runs as a subprocess.
  • •Clearer not-found errors: Looking up an agent that isn't in the resolved workspace returns a clear not-found error instead of an opaque internal error.
  • •0.1.6 release and analytics: cursor-sdk 0.1.6 documents the Buildkite release path and labels SDK usage as sdk-python- for clearer analytics.
2026-06-04

Canvas Design Mode and Context Usage Report

June 4, 2026

  • •Shared canvases can now be opened full-screen in the browser, making them easier to present to others.
  • •Added the ability for agents to embed buttons in canvases that will run a specific prompt when clicked.
  • •Improved the agent's ability to fix canvas type errors.
  • •Improved component styling, and added more chart customization functionality.
2026-06-03

Organizations for Cursor Enterprise

June 3, 2026

  • •Multi-team support so users can be on multiple teams at once
  • •Organization-level IDP management
  • •Organization-level usage analytics, with drill downs to each team
  • •Admins can move users between teams through the dashboard, API, or CSV
  • •New users joining a team inherit settings and permissions automatically
2026-05-29

Auto-review Run Mode

May 29, 2026

  • •Auto-review applies to Shell, MCP, and Fetch tool calls. Allowlisted calls run immediately, and calls that can be sandboxed run in the sandbox. All other agent actions go to a classifier subagent that decides whether to allow the call, try a different approach, or ask for your approval.
  • •Configure your run mode in Settings > Cursor Settings > Agents > Approvals & Execution. You can also steer the classifier agent by giving it custom instructions.
  • •Learn more in our docs.
2026-05-20

Shared Canvases and /loop Skill

May 20, 2026

  • •Canvases are interactive artifacts created by agents, like reports, dashboards, and custom interfaces. Instead of sharing a full chat thread, you can share a link to a live snapshot of a canvas for teammates to open in the browser.
  • •Teammates open a shared canvas from its link with read-only access. The Shared Canvases page in the Cursor Dashboard lists the canvases you've published, so you can manage your own shares. Shared canvases are available on Pro, Teams, and Enterprise plans.
  • •Learn more in our docs.
  • •With /loop, Cursor can run a prompt repeatedly on a local schedule, until a certain outcome is achieved, or until you stop it. If you don't specify a fixed interval, the agent decides when or what event should wake it.
  • •Use the /loop skill for local long-running agents. For example, you can ask it to “check deploy status every 5 minutes” or “work on this feature until tests pass.”
2026-05-20

Improvements to Cursor Automations

May 20, 2026

  • •Slack digest agent: Summarizes unread DMs and key Slack channels every morning and prioritizes them by importance
  • •Product analytics agent: Delivers a weekly digest of key metrics from your data warehouse like Databricks
  • •Product FAQ agent: Watches a Slack channel for questions and writes a first response based on docs, codebase context, and past threads
  • •Product finance agent: Pulls financial data from a billing provider like Stripe for recurring revenue reports
  • •Customer health agent: Monitors key systems like Granola, Slack, and Databricks and flags accounts where health signals are shifting
2026-05-19

Cursor in Jira

May 19, 2026

  • •Assign work items to Cursor, or mention @Cursor in a comment to kick off a cloud agent. Cursor uses the work item title, description, comments, and your team's repository settings to scope the task.
  • •You can ask Cursor to fix bugs, add features, update tests, or investigate something described in the ticket. When the agent finishes, Jira shows completion updates and includes a link to the pull request.
  • •Install the integration from Cursor integrations. You need Cursor admin access and Jira Commercial Cloud with Rovo enabled. Learn more in our docs.
v2.5

Composer 2.5

May 18, 2026

  • •Standard: \$0.50/M input, \$2.50/M output tokens
  • •Fast (default): \$3.00/M input, \$15.00/M output tokens
2026-05-13

Full-screen Tabs and Compact Chats

May 13, 2026

  • •Compact: shows concise results with minimal tool traces
  • •Balanced: includes important intermediate steps
  • •Detailed: provides near-complete step-by-step context
  • •Improved PR tabs by adding clearer review states, better reviewer/thread visibility, and more predictable PR tab actions.
  • •Improved long-chat scrolling to make it smoother, added better undo grouping in prompt input, and improved behavior while streaming.
  • •Added clearer status text for background/resumed tasks.
  • •Added cleaner environment/repo selection and better persistence when switching contexts.
  • •Improved MCP auth token lifecycle handling.
  • •Removed noisy in-app terminal notifications and improved shortcut behavior.
  • •Clarified model naming and selection behavior in the model picker and added stronger fallback handling.
  • •Improved search and navigation to make it faster and more reliable in large workspaces.
  • •Fixed PR tab bugs affecting branch lookup, header state, and diff loading.
  • •Fixed background task reliability issues like resume failures, interrupt edge cases, and incorrect status scoping on resumed subagents.
  • •Fixed cloud agents bugs blocking setup, state merge/persistence bugs, and multi-repo identity issues.
  • •Fixed MCP/OAuth reliability bugs like transient 401/stale-token cases and large-token handling edge cases.
2026-05-13

Development environments for cloud agents

May 13, 2026

  • •This release introduces new tools for teams to configure development environments for their agents. Cursor also can use these tools to set up and maintain environments for you. Together, this makes it easier for teams to run fleets of parallelized agents that handle tasks from end-to-end, inside development environments you fully control.
  • •Cloud agents and automations now support multi-repo environments, building off our work on multi-root workspaces. You can configure a single environment with all the repositories an agent needs for its work, with re-use across sessions.
  • •To make it easier to change, debug, and review environment definitions, we have improved Dockerfile-based configuration.
  • •This includes support for build secrets, making it easy to securely access private package registries directly from your Dockerfiles. Build secrets are scoped to the build step and aren't passed to the running agent's environment.
  • •We've also upgraded layer caching, so that only the updated layers of your image rebuild when you change the Dockerfile. Builds that hit the cache run 70% faster.
  • •As Cursor configures your environment, it will ask you questions, flag missing credentials, and validate that your environment is set up properly.
  • •Cursor will always show you the version of the environment your agent is running in. If your environment configuration fails, it will default to a base image with clear warning signs so that your cloud agents can keep running instead of immediately failing.
  • •Every development environment now has its own version history that users can review and roll back. Admins can also restrict rollback permissions to admins only. An audit log captures every action team members take on environments, giving security teams full visibility into who changed what.
  • •Egress and secrets can now be scoped at the development environment level. Secrets configured for one environment aren't accessible from any other.
  • •Learn more about agent development environments in our announcement and docs.
2026-05-11

Cursor in Microsoft Teams

May 12, 2026

  • •Mention @Cursor in any Teams channel to delegate a task to a cloud agent or pull information from Cursor into Teams.
  • •Cursor automatically picks the right repository and model based on your prompt and recent agent activity. It reads the entire thread for context before implementing a solution and creating a PR for your team to review.
  • •Get started by installing the integration in the Cursor dashboard. Learn more in our docs.
Showing 30 of 80