Loading…
Topic
Cursor
76 posts about Cursor. Every summary links to the original.
- 76 posts
- 4 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
IntelliJ IDEA’s Java and Kotlin for Cursor and VS Code Hits 1.0
IntelliJ IDEA’s Java and Kotlin language support extension has reached its 1.0 stable release, now available for VS Code and Cursor editors. The extension is powered by IntelliJ IDEA’s language server and debug adapter, providing smart code completion, navigation, code analysis, refactoring, and build tool support for Maven, Gradle, and Bazel. It also offers powerful debugging capabilities including emulated breakpoints and async stack traces, along with JUnit test runner support. The 1.0 release resulted from close collaboration with the Cursor team, making Java and Kotlin a first-class experience in Cursor’s Agents Window with dedicated support for nullability and Spring Framework specifics. Starting with 1.0, the extension requires an IntelliJ IDEA Ultimate subscription but provides a 30-day free trial, and future updates will enable agents to call the LSP directly for faster AI-assisted development, with announcements pending for purely agentic licensing.
Remote control for local agents
Cursor has introduced Remote Control, allowing users to view and interact with local agents running on their computer from the Cursor iOS app; agents appear in a list and users can tap one to see its activity or send a message. The feature is enabled by default for all users except Enterprise organizations; users tap their computer in the app and approve a pairing request in the Cursor desktop app. Agents remain running on the user’s computer, which must stay on and online; the app provides a “Keep this computer awake” setting to prevent sleep, and the computer must be plugged in with the lid open. Enterprise admins can enable Remote Control in Org settings under Security and identity. Remote Control does not rely on cloud agents and is available now in the Cursor iOS app.
Rollouts and Security Review
Cursor launched two bots for the last mile of shipping code: Rollouts and Security Review. Rollouts watches every change as it deploys and reports health per environment, with verdicts of verified healthy, regression detected, or inconclusive. It reads the diff and systems a pull request touches, writes a monitoring plan as a PR comment, and tracks deploy events per environment. Security Review reads every pull request in the context of the codebase and posts one review comment reporting exploitable bugs, including injection, authentication bypasses, and secrets. Both bots are available today on Teams and Enterprise plans, with usage credits for the next 10 days.
Cursor Projects
Cursor is launching Projects, a beta feature for taking on larger bodies of work such as features, migrations, and full applications. Each Project preserves context over months, runs on its own cloud computer through Cloud Agents, and coordinates parallel subagents rather than having the coordinator write code itself. Shared files synchronize across agents’ cloud and local machines, storing research, artifacts, codebase knowledge, and preferred working practices so later agents can use them. Projects can also subscribe to Slack channels, schedules, or pull requests and delegate work when signals arrive, while local agents handle testing that requires the user’s machine. Projects are accessible from Cursor’s left-hand navigation and are rolling out to all users in beta starting today.
Self-hosted machines
Cursor’s self-hosted machines keep tool execution inside an organization’s own network, leaving the codebase, build outputs, and secrets on internal infrastructure while the agent handles tool calls locally. The feature supports My Machines for connecting one laptop or VM and team pools that provide named queues of workers, with capacity expanding as requests arrive and contracting when workers disconnect. Pools are repository-independent, can hibernate idle machines, and can restore them within a reconnect window, avoiding the need to keep costly capacity warm. Cloud agents can run on infrastructure including AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B, while Linux and Mac workers add computer use for clicking, typing, screenshots, and browser control.
Start from scratch, without a repo
Cloud Agents can now start without a connected GitHub or other third-party source-control provider. Selecting Start from scratch in the repo picker lets someone prompt the agent immediately, while Cursor creates an Origin repo in the background. When the build is ready, Create repo saves it as a fully scaffolded Origin repo with a custom or suggested name and private or internal visibility; the Codebase tab provides access to the project. Cursor also port-forwards the cloud agent’s live environment to the browser for previews and design mode, and connecting a Vercel account enables publishing to a live URL for what was built.
Cloud Agents and Cursor Harness Improvements
Cursor’s release expands cloud agents and the Cursor harness for longer-running, event-driven software work. Cloud agents can subscribe to pull requests, Slack threads, or scheduled tasks, wake on events, keep goals until completion, and automatically address CI failures and bot comments on pull requests they create. Custom modes pin a selected skill in chat, while /goal supplies a long-lived objective that can be paired with a custom mode or /loop. Subagents can run on separate virtual machines with isolated project copies and clean context, supporting fresh testing or parallel fixes without collisions. Steering improvements let users send follow-ups that wait for the next tool call instead of interrupting an action.
Origin Code Hosting
Cursor is rolling out Origin, an early-beta code-hosting service for all paid plans, except enterprise organizations whose admins opt out, with repositories, pull requests, code browsing, and GitHub synchronization. Origin-hosted repositories treat Origin as the source of truth: users push through the CLI, while GitHub is not involved; GitHub-synced repositories instead keep GitHub authoritative and mirror changes to Origin in real time. Each repository includes pull-request timelines, commits, checks, file diffs, comments, reviews, and merging, with synced pull requests updating between Cursor and GitHub within seconds. Cursor also places agents alongside code and PRs, allowing them to answer questions, make changes, update pull requests, or push branches, while Vercel, Depot, and Buildkite integrations add preview deployments and CI options.
Firetiger joins Cursor
Cursor announced that the Firetiger team is joining the company, bringing together coding agents with agents focused on software after it reaches production. Founded in 2024 by Rustam Lalkaka and Achille Roussel, Firetiger builds agents that monitor rollouts, catch regressions, investigate incidents, and pass findings back to coding agents. The stated motivation is to reduce operational toil and connect code generation with production feedback, so an agent can ship a change, observe its behavior, and respond when something goes wrong. Firetiger’s work is expected to appear across Cursor as the companies develop long-running, autonomous, context-aware agents for teams, alongside Cursor Origin and the forthcoming Change Monitors, which will watch deployed changes and flag problems as they appear.
Cloud agents start 3x faster with builds
Cursor introduces builds for Cloud Agents, continuously prepared copies of development environments that replace just-in-time machine boot, repository cloning, dependency installation, and install-script execution. Builds run by default every hour; successful builds become the starting point for future agents, which fork warm live machines rather than restoring environments from disk. The post reports 10x faster internal environment boot times and 3x faster time to first token, while customers cite quick starts and uninterrupted automated runs when builds fail. If a dependency bump or Docker build breaks installation, the failed build stays inactive and sessions continue from the last successful version while debugging proceeds. The Cloud Agents dashboard exposes build status, logs, captured commit SHAs, and run-to-build links, while a git-state threshold and Cursor Cloud MCP support oversight; setup requires moving preparable work into install and reserving fresh services for start.
Cloud Agents Start 3x Faster with Builds
Cursor’s Cloud Agents now use Builds, ready-to-use copies of a development environment prepared in the background. These environments include cloned repositories, installed dependencies, and completed install commands, allowing agents to start without repeating setup each session. Cursor refreshes environments regularly, keeps warm copies, and activates only successful builds; internally, environments boot 10x faster and time to first token is 3x faster. If a commit or dependency update breaks a build, the last successful build remains active, while users receive a notification and can debug in the background. Builds can be inspected in the Cloud Agents dashboard, where logs, commit SHAs, statuses, and agent run associations are available, with tools for agents to inspect or manage them.
How Vercel used Cursor to build Queues
Vercel built its durable event streaming system, Vercel Queues, entirely with Cursor, using agents across three rewrites and validating changes against real AWS environments. Engineers had agents work on the Queues API, connect to AWS, inspect DynamoDB and Kinesis side effects, inject faults, simulate bugs, and verify results, while Cursor retained context through long sessions and compaction events. The workflow also supported model switching, parallel planning agents, inline review, stacked PRs, and asynchronous Cloud Agents. Among Vercel’s Cursor power users, PR throughput increased 54%, PR cycle time decreased 89%, resources per feature fell 27%, and the company reports 104 hours saved per developer annually. Product managers also use Cursor for repository analysis, product analytics, and small fixes without drawing on engineering resources.
Introducing Cursor Start
Cursor has launched Cursor Start, a monthly plan for developers in India priced at ₹649, with tax included and payment through UPI or card. The plan responds to requests for India-specific pricing and UPI support, and follows a reported tripling of Cursor’s Indian user base to more than 3M developers, making India its third-largest market globally. Start provides generous access to Grok 4.5 and Composer, more agent requests than the Free plan across desktop, web, iOS, and CLI, plus always-on cloud agents, Cursor for iOS, and workflow extensions through plugins, MCP servers, hooks, and skills. It sits between Free and Pro, offering everyday building capabilities while Pro adds broader model access and features such as Bugbot, Auto mode, Automations, and the Cursor SDK.
Cursor Router
Cursor Router now powers Auto mode, analyzing each request by task type and complexity before sending it to a suitable model. Frontier models handle demanding work, while price-efficient models handle other requests, with Cost, Balance, and Intelligence modes defining different positions on the cost-intelligence pareto frontier. Cost optimizes token spend, Balance targets strong quality, and Intelligence targets frontier quality; Balance and Intelligence bill at the routed model’s rate. Admins can enable routing by team or group, restrict modes, set defaults, allow or block underlying models, use soft or hard enforcement, and choose whether to display the routed model, while the feature is available across desktop, web, iOS, CLI, and the SDK and is on by default for Teams plans.
Build from anywhere with Cursor for iOS
Cursor for iOS is available in public beta on all paid plans, bringing agent-based development to a native mobile app. Users can choose a repository, select a frontier model, provide voice input or slash commands, and launch agents in the cloud or control agents running on their computers through Remote Control. The app supports asynchronous workflows with Live Activities and push notifications, while cloud agents use isolated virtual machines and full development environments to test, verify, and produce demos, screenshots, logs, and merge-ready pull requests. Developers can review diffs, provide follow-up instructions, merge pull requests, and hand sessions between local and cloud environments, including sending a local plan to the cloud or returning a cloud session to the computer for local testing. Cursor says repo-less chats are planned, and offers 75% off Composer 2.5 runs in the mobile app through July 5, 2026.
Cursor Mobile App for iOS
Cursor for iOS is available in public beta for all paid plans, bringing agent management and development workflows to mobile. Users can choose a repository, launch a cloud agent with any frontier model, provide voice input, and guide it with slash commands; agents run in isolated virtual machines with full development environments for testing, verification, and demos. Sessions can move from local to cloud, while Remote Control lets people continue directing a computer-based agent from the phone, with an option to keep the computer awake; Teams and Enterprise administrators must enable that feature in Cursor Dashboard. Live Activities and push notifications report agent status, including completion, requests for input, and review readiness, and the app supports reviewing artifacts such as demos, screenshots, logs, and diffs, leaving instructions, and merging pull requests.
How Notion used the Cursor SDK to embed coding agents
Notion integrated Cursor coding agents into its product so users can delegate work by tagging Cursor in a document, mentioning it in a thread, or assigning a database issue. Built with the Cursor SDK in a couple of weeks, the integration lets agents plan, build, test, verify work, and open pull requests while Notion focuses on product and user experience rather than agent infrastructure. Notion placed Cursor behind a provider-agnostic harness: a Notion thread maps to an agent, each message starts a run, and the first run can specify the prompt, repository, model, MCP servers, and automatic PR creation. Follow-up runs stream over SSE, support resumption after dropped connections, and use remote MCP to let Cursor read and write workspace state in real time; templates, custom instructions, selected tools, skills, subagents, and triggers provide further customization.
Coinbase reduces time from idea to production by 90% with Cursor
Coinbase redesigned its engineering model around agent-first infrastructure rather than retrofitting AI into legacy processes, making time from idea to production its north-star metric. More than 2,400 developers use Cursor; engineers define intent, write requirements for agents, plan work with Plan Mode, delegate implementation, and validate results, often running 5–7 asynchronous agents in parallel. The company reports that some teams cut idea-to-production time from 20 days to less than two days, while first PR creation fell from eight days to under 30 minutes; 75% of PRs are agent-created, and average developers save seven hours of coding weekly. Coinbase also uses smaller working groups, internal champions, speedruns, and Superbuilders to spread these workflows and build tooling.
Cloud Environment Setup and Cloud Subagents in Agents Window
This release updates cloud agents in the Agents Window of the Cursor desktop app, adding cloud environment setup, cloud subagents, and more reliable movement between local and cloud sessions. Cursor can help configure a development environment in under 10 minutes while showing progress in a shared terminal, then capture the result as a reusable snapshot for faster startup and software testing by future agents. The /in-cloud command launches a subagent in its own virtual machine and branch, isolating long-running or parallel tasks while the local workspace remains responsive; /babysit lets a cloud agent iterate on a pull request remotely. Cloud subagents can run in the background, and sessions can be pulled back to a local computer for testing, with multiple cloud agents running in parallel.
How Wayfair cut ML model costs by 90% (twice!) with Cursor
Wayfair’s Applied Research team used Cursor to automate and parallelize experiments for a product-tag validation model that checked attributes against images, descriptions, and reviews. The model was accurate but too expensive to run across the catalog. In December 2025, five researchers standardized the dataset and evaluation benchmark, then built and tested 110 distinct variants in four days; the winning architecture reduced inference costs by 94%, improved precision, and became the production baseline. In March 2026, the team benchmarked against that baseline, ran 140+ new experiments, and added genetic-algorithm searches, achieving another 90% cost reduction. The workflow used 20+ parallel agents, desktop and CLI surfaces, and cloud agents, leaving researchers to formulate hypotheses, interpret results, and choose candidates while Cursor implemented, ran, and measured variants.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.