What's New in Cursor: How to Always Know

If you have ever opened Cursor and spotted a new panel, a different model picker, or a capability that was not there last week, you already know the problem: figuring out what's new in Cursor is harder than it should be. Cursor ships changes frequently and across several layers at once, the editor itself, the underlying models it routes to, and the plans that gate certain features. Any article that tries to list "the latest features" goes out of date almost immediately. So this guide does something more durable: it teaches a repeatable method for always knowing what changed, using Cursor's official sources of record plus a notification layer so the news finds you.

The goal is not to memorize today's feature list. It is to build a small, reliable habit: anchor on a few first-party pages, learn to read a changelog entry quickly, and let a push notification tell you the day something ships. Do that and you will never have to wonder whether you are missing something. (One note up front: Cursor Drops, the app referenced later, is an independent project and is not affiliated with or endorsed by Cursor or Anysphere.)

Why "what's new in Cursor" is a moving target

Cursor is not one product with one frozen feature set. It is an AI code editor that sits on top of frequently updated models, wrapped in subscription tiers that decide who gets what and how much. A change can appear in any of those layers. A new capability might roll out gradually, ship behind a setting you have to enable, or arrive first on a specific plan. Two developers updating to the same build on the same day can genuinely have different experiences depending on their plan and settings.

That is why stating specifics as if they were permanent is a trap. Model names, pricing, request limits, which features belong to which plan, and the exact look of the interface all change over time. The reliable move is to learn where the current truth lives and check it when it matters, rather than trusting a snapshot from months ago. Below are the durable capabilities worth knowing, followed by the sources that always reflect the present state.

Durable Cursor capabilities worth knowing

While the specifics churn, several broad capabilities have been part of Cursor long enough to treat as stable categories. Knowing these gives you a mental map, so when a changelog entry mentions an improvement, you know which bucket it falls into:

• Inline code completion: predictive suggestions as you type, the everyday autocomplete layer that speeds up writing and editing code.
• Chat and inline editing: asking questions about your code and applying AI edits directly in the editor, with the model aware of the surrounding context.
• Agentic, multi-file changes: describing a task in natural language and letting Cursor plan and apply edits across several files, then reviewing the diff.
• Codebase awareness: indexing your project so answers and edits can reference relevant files instead of just the open buffer.
• Model choice and routing: selecting among supported models for different tasks, with availability depending on your plan.
• Rules and context configuration: shaping how the assistant behaves in your repository through project rules and supplied context.

The official sources of record

Everything reliable about what's new in Cursor traces back to a handful of first-party pages. These are the records of truth; every third-party summary, including any tracker, ultimately derives from them. Learn which one answers which question:

For day-to-day editor changes, the Cursor changelog is the place to start: it records dated, version-tagged updates so you can confirm what officially shipped instead of guessing from a UI difference. For deeper detail on how a feature works or how to configure it, the documentation at docs.cursor.com always reflects current behavior. The blog gives you the narrative behind major launches. If you want a structured walkthrough of how to read these dated entries, our companion piece on the Cursor changelog guide breaks down the terminology.

How to read a Cursor update quickly

Knowing where to look is half the battle; the other half is skimming efficiently so you only spend real time on changes that affect you. When a new changelog entry lands, run it through a quick filter:

1. Identify the layer. Is this an editor feature, a model change, a plan or pricing change, or a fix? That tells you whether it can even reach your workflow.
2. Check the scope. Note whether it is rolling out gradually, limited to certain plans, or behind a setting you must enable. "Available" rarely means "available to everyone at once."
3. Ask if it touches your work. Does it change a feature you actually use, or a model you actually select? If not, note it and move on.
4. Verify before relying on it. For anything important, especially model details and limits, confirm against the official docs and pricing page, which always describe the current state.
5. Capture one takeaway. If a change is useful, try it or write a one-line note the same day, otherwise it evaporates.

Get notified the day something ships

The reason most developers fall behind is simple: opening a changelog page is a chore nobody remembers to do. The fix is to make discovery push-based instead of pull-based, so a new release pings you the day it lands and you decide in a minute whether it matters. That is exactly the gap Cursor Drops is built to close. It is an independent iOS app and website that watches Cursor's public release activity and sends a push notification when something new ships, then lets you browse a readable, dated feed of changes.

The practical benefit is that you stop maintaining a mental checklist of pages to visit. You get notified once and triage from there, and you can browse the full history any time on the Cursor Drops changelog. If it suits you, the app is on the App Store. Think of it as a convenience layer over the official sources, not a replacement: anything it surfaces should be confirmed against the first-party changelog and docs when accuracy matters. For a deeper look at how often these updates land, see our overview of Cursor's release cadence.

Bottom line

You cannot reliably know what's new in Cursor by checking one page once in a while, because Cursor does not change in one place and does not roll out to everyone at the same time. Anchor on the official sources, the Cursor changelog for editor features and the documentation for how things work and which plan includes them, then make at least one channel push-based so releases reach you automatically. If you want that push layer without assembling it yourself, Cursor Drops notifies you when Cursor changes ship and keeps a readable history on its changelog. Pair the convenience of a notification with the authority of the official docs, and keeping up with Cursor stops being a chore and becomes a habit that runs itself.