What's New in Cursor in 2026

The current Cursor release story runs from Compile through the July 22 Cursor Router launch. Compile put Origin, larger model training and Cursor Mobile on the roadmap; the June wave shipped Automations, Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition., Design ModeA way to point at an element in Cursor's built-in browser and change it directly, instead of describing it in words. Press Enter for the full definition., Canvas, SDK agents and Organizations; 3.11 (July 10) added side chats, July 17 improved Cursor in Slack, and July 22 made Auto router-powered on Teams and Enterprise.

Knowing what shipped is the easy part. Turning latest Cursor releases into something a team relies on takes a few deliberate steps, mapped below.

1. 1Start with the workflow surface: local agent, cloud agent, automation, review, SDK or enterprise admin.
2. 2If Compile, Origin or mobile are on your roadmap, read those announcements before the rest of the June release wave.
3. 3Read the primary release page for that surface before quoting mechanics.
4. 4Update prompts, policies, training and pricing examples together so learners see one current story.
5. 5Re-check dates and price claims before using the content in sales, security or procurement conversations.

New capability comes with new ways to get it wrong. Keep these boundaries in place as you adopt it.

This release wave touched a lot of surfaces at once. Each one has its own guide with the detail and the sources, so jump to whichever you actually need.

Two ways, both built to dodge a stuffed context window once you pass roughly 80%. In a new chat, @past chats pulls compressed context from a prior conversation. It smushes the earlier context as concise as it can and drops the completed external and MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. tool calls, so you spin a fresh thread off the gist instead of the full history. The second is fork a chat, which takes a prior chat's context and starts a new chat from it.

Because the team expects review to be the next bottleneck. Every agent change is already inspectable through a review button at the bottom of the chat that shows all edits the agent made, including the ones that built a chart or touched a config. The bet: the more code AI generates, the more it has to be reviewed, so review becomes where the work piles up.

A few directions were flagged as forward-looking, not released. Treat them as signals, not features you can use today.

• Simulators in cloud agents for iOS and Android, a deeper integration than today's MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. cross-app bridge. Because Android is Linux-based, someone on the team already got a cloud agent to run an Android simulator with a lot of manual instructions, but a no-hand-holding version is not rolled out and has no date.
• Customer-customizable PR security loops. Cursor runs security bug-finding internally with a security BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition., and teased unannounced features to let customers build a validation loop on top of PRs.
• More sandbox controls, actively being built to give users finer say over what the agent can and cannot run.
• A very exciting update to the Supabase and Postgres integrations was mentioned without detail. Verify the specifics against the changelog before relying on it.

Start with the ones that act on you whether or not you act on them. On this list that is Cursor Router, which shipped on July 22 and is on by default for Teams plans. Auto is now routed per request, and only Cost mode keeps the bundled Auto pricing that the Auto plus ComposerCursor's own fast coding model, tuned for the editor and priced well below frontier models; the recommended day-to-day model for executing a plan. Press Enter for the full definition. usage pool assumes. Nobody on the team has to change a setting for the billing basis to have changed underneath them.

On Enterprise the same feature inverts. The router is off until an admin turns it on, so Enterprise has a decision sitting unmade while Teams has a default to go and check. Enterprise model access controls interact with it too, since the router routes around blocked models and Cursor says blocking too many reduces routing quality and can disable routing altogether.

Everything else in the June and July wave waits for somebody to want it. Automations, cloud environment setup, side chats, Design ModeA way to point at an element in Cursor's built-in browser and change it directly, instead of describing it in words. Press Enter for the full definition. in canvases, team marketplaces: capability you go and pick up, safe to read about the week you have a use for it. Origin and the larger from-scratch model are a third category again, a waitlist and a training programme, and neither belongs in a plan yet.

That three-way sort is most of the value in a page like this one. Default-on, opt-in, announced. The middle bucket is where people spend their reading time, and the first bucket, I think, is where the surprises come from.

Because Cursor publishes three, against three different baselines, and the feature is a saving or a spend depending on which one describes your team. Measured against bundled Auto Cost pricing, Cursor states that Balance and Intelligence average about twice the cost, and up to two to four times depending on the mode selected. Measured against pinning every request to Opus 4.8, Cursor reports early-access customers paying 30 to 50% less on Auto-routed requests, with Balance about 36% lower.

The widely repeated 60% figure belongs to a third baseline again. It is measured against Fable 5, not Opus 4.8.

A team that has been living on Auto's bundled pricing should therefore read the router as an increase, and a team that pinned an expensive model for everything should read it as a decrease. Same feature, opposite direction, and what decides it is only what the last invoice was built on.

Intelligence is the mode where this gets misread most often. Cursor's own numbers put it at about 15% higher satisfaction than Opus 4.8 at close to the same cost, $6.76 against $7.34 per commit, so the saving on pinned Opus 4.8 traffic sits with Balance rather than with Intelligence. Budget a 60% cut on that migration and you will be wrong by a wide margin.

Never quote one of these figures without naming its baseline. It is the easiest mistake to make with this release, and it is the kind that gets caught in a procurement conversation rather than in an editing pass.

Separate the claims that expire from the ones that do not. A mechanic (what /in-cloud does, what a side chat inherits) holds until Cursor changes the feature. A number (review time, cost multiple, price per seat) expires quietly, and a status word like beta or waitlist expires the moment somebody ships. This tracker carries its own checked date rather than the site-wide one for that reason, since a release page's only real claim is currency.

Status words deserve the most suspicion, in both directions. Origin is a waitlist with no published pricing, migration tooling or security terms, so a slide that treats it as next year's plan is a commitment nobody can keep. The larger model is training work. Meanwhile Cursor for iOS moved from something you described carefully to a public beta with its own product page, and Android is still web rather than native.

The small releases are where the detail actually bites, and side chats are a good example. They arrived in 3.11, they go one level deep because a side chat cannot spawn another, and they are local-only today with Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition. support flagged as coming soon. Any one of those can invalidate a workflow you were about to build on the feature.

So the habit is smaller than the page. Read the release note for the surface you own rather than a summary of all of them, then update the prompt, the policy and the pricing example together. A training deck that teaches the new mechanic on last quarter's pricing confuses a new hire more than one that is out of date all the way through.