Cursor

We’re introducing Cursor 3. It is simpler, more powerful, and built for a world where all code is written by agents, while keeping the depth of a development environment.

A conversation with @sirupsen on scaling Shopify, building turbopuffer, and the future of databases. 0:00 - Scaling Shopify through flash sales and outages 8:13 - How top infrastructure teams collaborated in the 2010s 10:35 - Engineering principles from Logrus and on-call 17:38 - The story behind Simon’s famous-ish blog, Napkin Math 23:05 - Why new database companies keep winning 32:21 - How Simon became a fan of databases 35:45 - AI coding, and where agents still fail 42:10 - Hiring P99 engineers in the AI era 48:45 - What’s next for databases

Customers like Decagon, Amplitude, BILT, and Snyk use development environments to let their agents handle tasks end-to-end. Learn more: cursor.com/blog/cloud-age…

Each environment now has its own version history with rollback. An audit log captures every change. Egress and secrets can be scoped per environment. Secrets in one environment aren't accessible from any other.

Starting today, you can run cloud agents inside fully configured development environments. Set them up the same way you'd set up a laptop for an engineer: cloned repos, installed dependencies, and toolchain credentials.

Fast mode for Claude Opus 4.7 is now available in Cursor! It's 2.5x the speed at 6x the cost. For most tasks, we recommend using the standard speed.

Cursor reads the entire thread for context before implementing a solution and creating a PR for your team to review. Learn more: cursor.com/changelog/micr…

Cursor is now available in Microsoft Teams. Mention @​Cursor in any channel to delegate tasks to an agent or pull information from Cursor into Teams.

Effort levels are now available to all users on usage-based Bugbot and can be configured from your Bugbot dashboard. Learn more: #effort-levels" target="_blank" rel="nofollow noopener">cursor.com/docs/bugbot#ef…

Over 80% of issues detected with default effort are resolved by users at merge time. And with high effort, Bugbot finds 35% more bugs with the same resolution rate.

You can now customize how deeply Bugbot thinks during a PR review. At Cursor, we use high effort for changes to our infrastructure and backend so Bugbot detects more issues. Other PRs get default effort.

See everything new in Cursor: cursor.com/changelog/05-0…

Pin your most commonly used skills as quick-action pills for easy access.

A new PR review experience is now available in Cursor 3. Take PRs from creation to merge, all in one place. You can see comments, diffs, commits, and review status to understand what changed and next steps. Navigate larger PRs more quickly with the file tree and changes picker.

To try the /orchestrate skill with the Cursor SDK, download the plugin from our marketplace: cursor.com/marketplace/cu…

This builds on our existing research on multi-agent systems, with a key addition: verifiers. Planners spawn workers that write code and verifiers that run it. If verification fails, the planner spawns a new worker to fix it.

Introducing /orchestrate, a skill that recursively spawns agents to tackle your most ambitious tasks with the Cursor SDK. We’ve used it to: - Autoresearch our internal skills, cutting token use by 20% while improving evals - Cut cold start times on our internal backend by 80%

We use previous generations of Composer to train future ones. Our autoinstall system has earlier Composer models set up dev environments for RL training. That way, the next generation can focus on learning to solve harder problems. cursor.com/blog/bootstrap…