Cursor version history

The Cursor version history lists the Cursor releases and feature names that could be confirmed against Cursor’s changelog, Cursor’s documentation, and the npm and PyPI registries as of 26 September 2026. The page also gives a routine for turning any new Cursor release note into a tested team rollout. For everything else, Cursor’s own changelog is the record.

This page is for the developer or tech lead who owns a team’s Cursor setup: the committed rules, skills, hooks, and MCP servers, and any script that drives Cursor’s agent. Your onboarding doc still says “Background Agents”, a teammate mentions a command you have never seen, and three people run three different builds. Before anyone changes a setting, you need to know what changed, whether it touches your config, and how you would notice if an update made the agent worse.

What you get from this Cursor changelog

• The current state of every Cursor artifact you can pin, and the one you cannot.
• A table of renamed features, so your team docs and prompts use the names Cursor uses today.
• The release milestones this page could verify, each with its date and source.
• A six-step routine and three copy-paste prompts that take a release note to a team rollout, with a pass signal you read without reviewing every diff.

Which Cursor version is current?

As of 26 September 2026:

Item	Current value	How to check
Desktop app	The Cursor 3.x line. No build number could be confirmed against a Cursor source on 26 September 2026, so this page pins none	The version your app reports. Record it with the date: “Cursor 3.x build N, checked on YYYY-MM-DD”
TypeScript SDK	@cursor/sdk 1.0.32, published 2026-09-22. npm lists 10 stable releases between July and 22 September 2026	npm view @cursor/sdk version
Python SDK	cursor-sdk 1.0.32, uploaded 2026-09-22	pip index versions cursor-sdk, or the package page on PyPI
SDK runtime	Node.js 22.13 or later (engines field of @cursor/sdk)	node --version
Models	Grok 4.7 was available in Cursor from its release day, 2026-09-21 (secondary source: MarkTechPost). No Cursor default model or price is verified for this date	The models hub and Cursor’s model picker

The SDKs are the only Cursor artifacts with a public version history you can pin in CI. For how Cursor’s update channels work and how to roll back a desktop build, see Cursor upgrade guides.

Which Cursor feature names changed?

Old names survive in team wikis, prompts, and review checklists long after the product moves on. A prompt that asks for a “Background Agent” still works on a person, but it confuses a new hire searching Cursor’s docs.

If your docs say	Cursor’s current name	What to do in your repository
Background Agents	Cloud Agents (name checked 2026-08-28)	Rename in docs and prompts. See Cloud Agents and Automations
BugBot, BUGBOT	Bugbot	Rename in review checklists. See Bugbot
YOLO mode, Auto-Run	Run modes, the docs page under agent security	Re-read the page before you document any mode by name: the individual mode names were not verified on 26 September 2026
.cursorrules as the way to configure Cursor	Rules (cursor.com/docs/rules)	Check your rule files against the Rules page. See project rules
SDK docs at cursor.com/docs/sdk/typescript	cursor.com/docs/api/sdk/typescript (stated in the 1.0.32 README)	Update links in internal docs. See the Cursor SDK

What changed in Cursor, and which of it is verified?

Each row below was read on a Cursor page, a package registry, or (where marked) a secondary source, on the date in the last column. The site’s earlier, longer history of Cursor 0.x to 3.x could not be re-checked on 26 September 2026, so it is no longer reproduced here; read Cursor’s changelog for the full record.

Date	Change	Source	Checked
2026-09-22	@cursor/sdk 1.0.32 on npm and cursor-sdk 1.0.32 on PyPI	npm, PyPI	2026-09-26
2026-09-21	Grok 4.7 available in Cursor from day one	MarkTechPost (secondary)	2026-09-26
2026-08-19	/goal: “give the agent a long-lived objective to work towards until it’s fully complete”. Marked “Rolling out” in the CLI slash-command reference	Cursor changelog, CLI reference	2026-08-28
2026-08-19	Subagents can run on their own virtual machines, each with an isolated copy of the project and clean context	Cursor changelog	2026-08-28
2026-05-20	Cursor 3.5 (changelog entry shared-canvases): /loop runs a prompt repeatedly on a local schedule until an outcome is reached or you stop it. It is a bundled skill	Cursor changelog	2026-08-28
2026-05-13	First uploads of the Python cursor-sdk to PyPI: a 0.0.0 placeholder, then 0.1.0 the same day	PyPI	2026-09-26
2026-04-26	First release of @cursor/sdk on npm (1.0.7)	npm	2026-09-26

For how /goal and /loop compare with the same commands in Claude Code and Codex, see goal commands across tools and loop commands across tools.

Which Cursor features did the documentation describe in August 2026?

This inventory is what Cursor’s documentation described on 2026-08-28. Use it to check whether your team’s docs mention a feature under the right name and link to the right page on this site.

Area	Feature	What it does	On this site
Plan and build	Plan Mode	Creates an implementation plan before writing code	Agent modes
Parallel work	Worktrees, Subagents	Isolated Git checkouts for the agent; specialised assistants the agent delegates to	The Agents Window
Cloud	Cloud Agents, Builds, Automations, Cloud Agents API	Agents in isolated cloud VMs; background environment preparation; agents started on a schedule or by Slack, source-control, webhook, Linear, Sentry, or PagerDuty events; programmatic launch	Cloud Agents and Automations
Customisation	Rules, Agent Skills, Hooks, Plugins, MCP	System-level instructions; portable skill packages; processes that observe, block, or modify the agent loop over JSON on stdio; bundles of all of these; connections to external tools	Custom rules and templates
Review and release	Bugbot, Security Agents, PR Routing & Approval, Origin	PR review for bugs and security issues; security scanning; reviewer assignment and approval of low-risk PRs; Cursor’s git forge	Rollouts and approval
Scripting	CLI print mode (-p, --print), TypeScript and Python SDKs	Non-interactive runs for scripts and CI; Cursor’s agent called from your own code	The Cursor SDK

How do you turn a Cursor release note into a tested rollout?

Treat a Cursor update like a dependency bump: one owner, one written note, and a pass signal that comes from tests rather than from someone reading the agent’s diffs. The tech lead who owns the team’s Cursor config signs off in step 6.

1. Record what each person runs today. Ask the team to post the build their app reports, and write it down with the date. If you script Cursor, record the SDK version your project actually installs:

   npm ls @cursor/sdk
   pip show cursor-sdk

2. Read every entry on Cursor’s changelog since your last check, and sort each one into three buckets: changes a default, a permission, or billing; touches config you commit (rules, skills, hooks, MCP servers, plugins); new capability you can ignore for now. The first prompt below does the sorting. To see how far behind your pin is, check the latest published version, to compare against:

   npm view @cursor/sdk version
   pip index versions cursor-sdk

3. Check that your committed config still loads. Open a fresh agent chat on the updated build and run the second prompt below. Compare its answer with the files in your repository: a rule or MCP server that is missing from the answer is not loaded.

4. Run a canary set. Keep three to five real tasks from your backlog, each with acceptance tests written before the agent starts. Run them on the old and the new build, each in its own worktree, from the same commit. The third prompt below is the template. Your pass signal is the test suite, the type check, and the linter, not the diff.

5. Pin anything that runs unattended. In CI, install an exact SDK version and move the pin only in a pull request that also runs your headless job on a fixture:

   npm install --save-exact @cursor/sdk@TESTED_VERSION
   pip install cursor-sdk==TESTED_VERSION

   Replace TESTED_VERSION with the version your canary run passed on. The latest published version on 26 September 2026 was 1.0.32. Do not copy a version from a registry page: the registry moves ahead of what you tested.

6. Roll out in two stages. One volunteer uses the new build for a few working days; then the whole team moves. The owner approves the second stage when the canary results match the old build and the volunteer has no open config issue. If they do not match, follow the rollback steps in Cursor upgrade guides before you debug.

Copy-paste prompt: triage Cursor release notes for this repository

Below are Cursor changelog entries published since our last check. Paste them
verbatim after this prompt.

First, read this repository's Cursor configuration: everything under .cursor/,
any rules, skills, hooks, MCP server configs, and plugins, plus scripts or CI
jobs that call the Cursor CLI or @cursor/sdk.

Then build a table with one row per changelog item:
- item (quote the changelog sentence, do not paraphrase it)
- bucket: DEFAULT/PERMISSION/BILLING change, TOUCHES OUR CONFIG, or OPTIONAL
- the files in this repository it affects (path), or "none"
- what we must test before rolling it out, as a concrete check

Do not invent features, version numbers or settings that are not in the pasted
text. If an item is ambiguous, mark it UNCLEAR and say what we should read.
Do not edit any files.

The prompt asks for the changelog sentence behind every row, so the reviewer checks each claim against its source instead of trusting a summary.

Copy-paste prompt: confirm what the updated agent loaded

Before doing any work, list exactly what you have loaded in this session:
1. Every rule, with its file path and why it applies here.
2. Every skill you can use, with its name and source directory.
3. Every MCP server and the tools it exposes.
4. Every hook or subagent definition you know about from this project.
Then compare that list with the files that exist under .cursor/ and any other
Cursor config in this repository. Report files that exist but are NOT loaded,
and anything loaded that does NOT come from this repository.
Do not change any files.

The agent’s list is a self-report; for a rule that must load, add a line asking the agent to start replies with a unique marker and check for it.

Copy-paste prompt: run one canary task after a Cursor update

Canary task. Implement the change described in docs/canary/rate-limit-headers.md.
The acceptance tests are in tests/canary/rate-limit-headers.test.ts and are the
specification: do not edit, skip or weaken them.
Work only in src/middleware/. When you finish, run:
  npm test -- tests/canary
  npm run typecheck
  npm run lint
Stop when all three pass or after three failed attempts.
Report: each command, its exit code, the number of files changed, and any
assumption you made that the task file does not state.

Replace the task file, test path, and commands with one of your own canary tasks. Run the same prompt on both builds and compare the report: exit codes, attempts used, and files changed. A new build that needs more attempts or touches more files on the same task is a regression signal even when the tests pass.

What breaks after a Cursor update, and how do you recover?

• The agent ignores a rule it followed yesterday. Run the “confirm what the updated agent loaded” prompt. If the rule is missing, compare its file against the current Rules page and move the team back to the previous build while you fix it; the rollback steps are in Cursor upgrade guides.
• An MCP server or hook stops working after the update. Check its entry against Cursor’s MCP or Hooks page, restart the server, and re-run the loaded-config prompt. Keep the server out of the rollout until the canary set passes with it enabled.
• A CI job that uses the SDK fails after an unpinned install. Pin the last version that passed (npm install --save-exact @cursor/sdk@<LAST_GOOD_VERSION>), then read the SDK release on npm before you move the pin again. On an older runner, check that Node.js is 22.13 or later first.
• A model you relied on disappears from the picker, or its behaviour changes. Do not switch on a vendor benchmark table. Pick a candidate from the models hub, run the canary set on it, and follow the new-model playbook.
• The canary set passes, but with more attempts or larger diffs. Hold the team rollout. Reproduce on the previous build from the same commit, and report the difference to Cursor with both build numbers.
• A teammate cites a Cursor feature you cannot find in the changelog. Treat it as unconfirmed until you read it on a Cursor page. Many third-party summaries of Cursor releases circulate; this page leaves out anything it could not trace to one.
• Team docs still use old feature names. Search the docs and prompts for the left-hand column of the renamed-features table and replace each hit in one pull request.

Where to go next after a Cursor update

Cursor reference hub The other Cursor reference pages

Cursor upgrade guides Update channels, pre-flight checks, and rollback

Feature adoption strategies Decide which new Cursor features your team adopts, and when

The Cursor SDK Drive Cursor's agent from TypeScript or Python

Reading evidence instead of code Pass signals you can trust without reading every diff

Models hub Current models, prices, and defaults across tools

The sibling changelogs track the other two tools the same way: Claude Code version history and Codex version history.