Cursor

Composer 2.5 shipped alongside cloud agent integrations for Jira and Microsoft Teams, extending the agent runtime beyond the editor into existing engineering workflows.

First-party models moved to Composer 2.5.

• Composer 2 (March) set a new baseline for coding performance; Composer 2.5 (May) improves sustained work on long-running tasks and instruction-following
• Standard tier at $0.50/$2.50 per million tokens; Fast tier at $3.00/$15.00

Cursor 3 reorganized the interface around parallel agents.

• The Agents Window runs multiple agents across repos, branches, worktrees, and cloud environments simultaneously
• Tiled layout, /multitask for async subagents, and multi-root workspace support landed in April
• Canvases produce durable interactive dashboards and visualizations in the side panel

Cloud agents expanded reach via integrations and a public SDK.

• Self-hosted deployment keeps code and execution inside your own network (March)
• Jira and Microsoft Teams integrations trigger cloud agents directly from tickets and threads (May)
• Multi-repo environments support Dockerfile-based configuration, build secrets, and dependency installation
• The Cursor SDK (@cursor/sdk) exposes the same agent runtime programmatically via TypeScript

Security tooling added two always-on review agents.

• Security Reviewer checks every PR for auth regressions, privacy risks, and prompt injection, leaving inline comments at the diff location
• Vulnerability Scanner runs scheduled scans; both are available in beta on Teams and Enterprise plans
• Bugbot gained self-improving learned rules, MCP support, and configurable effort levels

Enterprise admin controls expanded.

• Granular model allow/blocklists at the provider and configuration level, with a migration deadline of June 1
• Soft spend limits, per-surface usage analytics, and team marketplaces for distributing plugins to members