Cursor is now available in Microsoft Teams.
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.
Teams admins and Individual plan users can now customize the effort level Bugbot uses for its PR reviews, with three different configurations:
Customers must be on usage-based billing for Bugbot to customize effort levels. Learn more in our docs and go to your Bugbot dashboard to get started.
This release introduces a new PR review experience, faster execution on plans through parallel agents, and new quick-action pills for common workflows.
A new PR review experience is now available in Cursor 3. Take PRs from creation to merge all in one place.
You can see useful context like reviewer status and pending review banners, and quick action pills allow you to take next steps faster.
Cursor can now execute on plans faster by multitasking across tasks instead of tackling them one at a time.
Click "Build in Parallel" to have it identify independent parts of your plan and run them simultaneously using async subagents. Cursor will keep dependent steps in order when needed.
When multitasking in Cursor, you can now use a built-in quick action to split changes into PRs.
It will use chat context to identify logical slices, default to independent PRs unless dependencies are required, create a backup snapshot, and propose a split plan for your approval.
You can now pin your most commonly used skills as quick-action pills for faster access.
model: opus to have subagents always use the newest Opus model)./multitask is now available in the editor for running async subagents to parallelize your requests instead of adding them to the queue.You can now see a breakdown of your agent's context usage.
Use these stats to diagnose context issues and improve your setup across rules, skills, MCPs, and subagents.
This release introduces updates for Enterprise admins: a new system for model controls, updated spend management, and more detail for usage analytics.
Admins can now set more granular allow or blocklists at the model and provider level. You can block entire providers or specific model configurations for speed and context window size.
Enterprises also have the option to block new providers or model versions by default.
Customers with existing blocklists will need to migrate to the new system by June 1st. Admins should go to their team model settings in the Cursor dashboard to get started.
Admins can now set soft limits instead of hard limits to avoid blocking users. Cursor can also monitor usage and sends automatic alerts to users reaching 50%, 80%, and 100% of their soft or hard limits.
This keeps users productive while giving admins and users visibility into consumption patterns.
Go to the spend management settings in the Cursor dashboard to get started.
Admins can now filter usage by specific users, or break it down by product surface: clients, Cloud Agents, automations, Bugbot, and Security Review.
Go to the usage analytics tab in the Cursor dashboard to get started.
Cursor is now available in Microsoft Teams.
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.
Teams admins and Individual plan users can now customize the effort level Bugbot uses for its PR reviews, with three different configurations:
Customers must be on usage-based billing for Bugbot to customize effort levels. Learn more in our docs and go to your Bugbot dashboard to get started.
This release introduces a new PR review experience, faster execution on plans through parallel agents, and new quick-action pills for common workflows.
A new PR review experience is now available in Cursor 3. Take PRs from creation to merge all in one place.
You can see useful context like reviewer status and pending review banners, and quick action pills allow you to take next steps faster.
Cursor can now execute on plans faster by multitasking across tasks instead of tackling them one at a time.
Click "Build in Parallel" to have it identify independent parts of your plan and run them simultaneously using async subagents. Cursor will keep dependent steps in order when needed.
When multitasking in Cursor, you can now use a built-in quick action to split changes into PRs.
It will use chat context to identify logical slices, default to independent PRs unless dependencies are required, create a backup snapshot, and propose a split plan for your approval.
You can now pin your most commonly used skills as quick-action pills for faster access.
model: opus to have subagents always use the newest Opus model)./multitask is now available in the editor for running async subagents to parallelize your requests instead of adding them to the queue.You can now see a breakdown of your agent's context usage.
Use these stats to diagnose context issues and improve your setup across rules, skills, MCPs, and subagents.
This release introduces updates for Enterprise admins: a new system for model controls, updated spend management, and more detail for usage analytics.
Admins can now set more granular allow or blocklists at the model and provider level. You can block entire providers or specific model configurations for speed and context window size.
Enterprises also have the option to block new providers or model versions by default.
Customers with existing blocklists will need to migrate to the new system by June 1st. Admins should go to their team model settings in the Cursor dashboard to get started.
Admins can now set soft limits instead of hard limits to avoid blocking users. Cursor can also monitor usage and sends automatic alerts to users reaching 50%, 80%, and 100% of their soft or hard limits.
This keeps users productive while giving admins and users visibility into consumption patterns.
Go to the spend management settings in the Cursor dashboard to get started.
Admins can now filter usage by specific users, or break it down by product surface: clients, Cloud Agents, automations, Bugbot, and Security Review.
Go to the usage analytics tab in the Cursor dashboard to get started.