New PR Review Experience and Parallel Building
TL;DR
Introduces a unified PR review interface with inline threads and commit history. New 'Build in Parallel' feature allows Cursor to execute independent plan tasks simultaneously using async subagents to speed up development.
What changed
Cursor released a unified PR review interface on May 7, 2026. The Reviews tab now displays inline threads and top-level comments together. A separate Commits tab shows focused history, while the Changes tab adds a file tree for larger diffs.
The same update added Build in Parallel. This feature scans a plan, identifies independent tasks, and runs them at the same time with async subagents. Dependent steps stay ordered. Quick-action pills for splitting changes into PRs and pinning skills were included as well.
Why it matters
Solo builders gain speed on multi-step work without managing separate terminals or agents. The parallel execution reduces wall time on plans that previously ran sequentially. This shifts Cursor from single-thread assistance toward coordinated task fleets inside one workspace.
Teams using Cursor for end-to-end work now have a tighter loop between planning, building, and merging. The PR interface keeps context inside the editor instead of forcing context switches to GitHub. The bet is that faster iteration inside Cursor will increase daily output more than external review tools can match.
How to use it
Open any plan in Cursor 3 and click the new Build in Parallel button. Subagents launch automatically on independent steps. For PR reviews, switch to the Reviews tab inside the PR view to see threads and commit history in one place.
Access quick actions by pinning skills in settings or using the split-changes pill after multitasking. The features are live for all users on the current release with no extra plan required.
Watch for
Confirm the bet if parallel runs produce fewer merge conflicts and review time drops measurably. It breaks if subagent coordination creates hidden state bugs or inconsistent outputs across branches. Expect Cursor to add dependency-aware scheduling and cross-repo task handoff next.
Harsh’s take
Cursor's parallel build and unified PR view reduce context switching for solo operators who already live inside the editor. The real trade-off is hidden cost: async subagents consume more tokens per plan, and the speed gain only appears on tasks that split cleanly. Messy or tightly coupled work still serializes and may produce noisier diffs.
Review quality inside Cursor improves visibility but does not replace external stakeholder sign-off. Builders who skip GitHub comments risk shipping changes that pass internal checks yet fail production norms.
Do this now: test Build in Parallel on your next three-feature plan, measure token spend against baseline, and decide whether the time saved justifies the extra usage.
by Harsh Desai
About Cursor
View the full Cursor page →All Cursor updatesMore from Cursor
- App UpdateCustomize Bugbot PR Review Effort
Admins and Individual plan users can now set Bugbot's effort level to Default, High, or Custom. High effort allows for deeper reasoning to find more bugs, while Custom effort uses natural language instructions to determine review intensity.
- IntegrationIntegrate Cursor with Microsoft Teams
Cursor is now available in Microsoft Teams. Users can mention @Cursor in any channel to delegate tasks to cloud agents, which can read thread context, select repositories, and create pull requests directly from the chat.
- FeatureConfigure Agent Development Environments
New tools allow teams to configure development environments for agents using Dockerfile-based configuration with build secrets and layer caching. Supports multi-repo environments and provides full version history and audit logs for governance.