Cursor says Origin now integrates with more than 20 deployment, CI, code-review, security, monitoring and project-management apps, and it opened marketplace submissions to external developer-tool teams. Origin apps use app JWTs and installation tokens, receive webhooks, and can write checks, pull-request comments and reviews.
Why it matters: Origin can now act across a much broader delivery chain, while third parties gain a path to publish executable integrations. That makes installation scope, webhook provenance, token rotation and write permissions practical adoption decisions rather than…
Cursor's iOS app can now discover paired computers, show local agents running on them and send those agents messages. Execution remains on the user's computer, which must stay powered, online and awake; Enterprise organizations must explicitly enable Remote Control.
Why it matters: A phone becomes an intervention surface for agents holding local code, credentials and tools. That is useful for long-running work, but it expands the session, device-pairing and notification boundary without moving execution into an isolated cloud…
Cursor released two bots for Teams and Enterprise plans. Rollouts writes an editable monitoring plan for each pull request, follows the matching commit through deployment telemetry and reports healthy, regressed or inconclusive status per environment. Security Review inspects pull requests for exploitable flaws and posts one severity-rated review with an attack path and proposed fix.
Why it matters: The release moves coding agents beyond code generation into deployment verification and exploit-focused review. It can connect source, delivery and telemetry evidence on the pull request where a team decides whether to ship or revert.
Cursor launched Projects in beta with a coordinator that plans larger bodies of work, delegates implementation to cloud or local agents, and maintains shared files and learned context across machines. Projects can also subscribe to schedules, Slack channels and pull requests so work starts from external signals without a fresh prompt.
Why it matters: The feature combines durable memory, high parallelism and event-driven execution in one coding workspace, raising the leverage and the blast radius of stale context, excessive permissions or incorrect delegation.
Cursor added self-hosted machines for agent tool execution inside a customer's network. Code, build outputs and secrets remain on internal infrastructure while the agent issues tool calls locally, and teams can assign machines to managed pools.
Why it matters: Organizations with private networks or regulated build systems gain a deployment option that separates model orchestration from where code and credentials are executed.
Cursor launched Cloud Agent Builds: background-prepared bootable snapshots containing repositories, dependencies, and completed install steps. New environments use Builds automatically, while existing environments can test and enable them from the Cloud Agents dashboard.
Why it matters: Moving clone and dependency work out of the agent startup path can reduce startup failures and latency, while recorded build commits and logs improve reproducibility when agent runs diverge.
Cursor introduced a new agent-centered workspace with multi-repository navigation, parallel local and cloud agents, handoff between those execution modes and a path back into the traditional IDE. Agents launched from desktop, web, mobile, Slack, GitHub and Linear appear in one interface, and cloud agents return demos and screenshots for review.
Why it matters: The developer interface is moving from one chat beside one repository to a control room for many asynchronous workers. Verification artifacts and handoff state become first-class UX, not afterthoughts.
Cursor released Composer 2 as its own coding model, trained with continued pretraining and reinforcement learning on long-horizon tasks. It was available in Cursor at $0.50 per million input tokens and $2.50 per million output tokens, with a faster serving tier at higher prices.
Why it matters: Coding-tool companies are becoming model developers, optimizing model, harness, repository context and interface together. Low prices can make persistent background coding viable if the model actually finishes tasks without expensive review or retries.
Cursor cloud agents gained the ability to run and use the software they created inside isolated virtual machines. They could return merge-ready pull requests with videos, screenshots, and logs, and were accessible from Cursor's web, desktop, mobile, Slack, and GitHub surfaces.
Why it matters: A coding agent could close the loop from implementation to visible runtime evidence, making reviews more grounded than a code diff alone.
Cursor released long-running agents that plan before acting and work autonomously on larger software tasks. The research preview was available through Cursor's cloud agents for Ultra, Teams, and Enterprise plans.
Why it matters: Coding-agent sessions began extending from quick edits into larger pull requests that could continue without a developer continuously present.
Cursor 1.0 made its Background Agent generally available, introduced Bugbot for pull-request review, added one-click MCP installation and allowed agents to edit Jupyter notebook cells.
Why it matters: AI coding products were consolidating repository work, asynchronous execution, review and tool connection into one operating surface.
Cursor began gradually previewing Background Agent on May 15 with parallel remote environments, status checks, follow-ups, and takeover. On May 19, GitHub put Copilot coding agent into public preview, letting users assign issues that produced tested draft pull requests in a GitHub Actions environment.
Why it matters: Coding assistance became asynchronous delegation: the unit of value shifted from an inline suggestion to a reviewable pull request created while the developer did other work.