Cursor 2.5 ships Build in Parallel + Microsoft Teams integration — coding-agent UX consolidates around concurrent execution

Cursor's 2.5 release added Build in Parallel (concurrent sub-agent execution on the same code state), Microsoft Teams integration, and matched Opus 4.7 and GPT-5.5 on benchmarks at $0.50/M input / $2.50/M output. The Teams integration is the procurement-friendly part of the release — enterprise buyers running M365 get IDE collaboration without a separate identity layer.

Build in Parallel is the substantive engineering work. The pattern is: planner agent decomposes the change, multiple sub-agents execute non-overlapping sub-changes against the same git working tree concurrently, then a reviewer agent reconciles. For codebases where the change set naturally decomposes (test additions, doc generation, formatter fixes), the throughput gain is straightforward. For codebases with tight inter-file coupling, the reconciler becomes the bottleneck.

The competitive picture against Windsurf 2.0's bundled Devin and the new Gemini Spark consumer agent is clarifying. Cursor owns the in-IDE concurrent-orchestration lane; Windsurf owns the autonomous-cloud-engineer lane; Spark owns the cross-app personal-task lane. Three distinct agent surfaces, three distinct moats. See our analysis →.

Lushbinary — AI coding agents 2026 → · Shareuhack — Cursor vs Claude Code vs Windsurf 2026 →