New in June 2026: SpaceX closes the $60B acquisition

On June 16, 2026, SpaceX confirmed it has signed a definitive merger agreement to acquire Anysphere — Cursor’s parent company — in an all-stock deal valuing it at $60 billion. The April call option has been exercised. The deal landed four days after SpaceX’s ~$75 billion Nasdaq IPO, is expected to close in Q3 2026 pending regulatory approval, and is the largest acquisition of an AI developer-tools company on record.

For users, nothing changes today — the product ships on the same roadmap. Over the next year, expect Grok-based models to appear in the picker alongside Claude and GPT, Composer to get a major compute boost via xAI’s Colossus cluster, and data-handling terms worth re-reading if your codebase touches regulated data. Cursor’s bring-your-own-API-key policy remains your best hedge on model flexibility. Full breakdown: SpaceX Just Closed the $60B Cursor Deal. Sources: CNBC, Crunchbase News.

New in June 2026: Cursor 3.7 — Design Mode gets multi-select and voice-while-running

Released June 5, 2026. Two changes to Design Mode that, in combination, meaningfully reduce the context-switching overhead in visual iteration.

Multi-select editing lets you click two or more UI elements simultaneously in the browser preview. Cursor sees all the selected elements, their code, their surrounding layout, and the spatial relationships between them. You can then ask the agent to make one match the other, align a group of components, or remove repeated content across the selection — in a single instruction, across all the selected code at once. Previously you were editing one element at a time; now you’re editing the relationship between elements, which is how designers actually think.

Persistent voice input means the microphone stays available while an agent run is in progress. The old flow: describe a change, wait for the agent to finish, describe the next change. The new flow: describe a change, keep narrating as the agent works, queue the next edit by voice before the current one lands. For rapid visual iteration — the kind that used to require constant tab-switching between the tool and your notes — this cuts latency significantly.

Teams pricing update also shipped with 3.7: a new Premium seat tier for heavy agent users, increased usage limits on Standard seats, and real-time spend forecasting with smarter alerts. The cost-control improvements take effect for new customers immediately and for renewing teams on cycles starting July 1, 2026. Source: Cursor changelog 3.7.

Let’s get this out of the way upfront: Cursor is a code editor, not a no-code tool. If you’ve never written code before, Cursor will generate files full of things you can’t read, can’t debug, and can’t maintain. That’s not a Cursor problem — it’s a mismatch between the tool and the user. So if you’re a non-technical founder, the most useful thing this review can tell you is when Cursor is your problem to solve, and when it isn’t.

New in May 2026: Cursor 3.5 — Automations across repos, Teams, and Jira

Three updates shipped in the past week that collectively make Cursor look less like a coding tool and more like a full engineering orchestration platform.

Cursor 3.5 (May 20) focused on Automations — the always-on background agents that can run tasks on a schedule or in response to events, without you sitting at a keyboard. The key changes: you can now attach multiple repos to a single Automation, so an agent working across a frontend and a shared component library doesn’t lose context mid-task. You can also create Automations with no attached repo at all — five new no-repo templates are available in the Cursor Marketplace for things like market research sweeps, changelog summarization, and dependency auditing. Both Automations types are now manageable directly from the Agents Window in your IDE, rather than only through cursor.com. For the first seven days after launch, all agent runs for newly created Automations were 50% off. Source: Cursor changelog May 20.

Cursor in Jira (May 18–19) is the more significant product move. In partnership with Atlassian, you can now assign a Jira ticket directly to Cursor — the cloud agent reads the ticket title, description, comments, and your repo settings, then starts building. When it needs a decision or is ready for review, it notifies you inside Jira. When it opens a PR, it links back to the ticket automatically. The workflow requires Cursor admin access and Jira Commercial Cloud with Rovo enabled. For teams that live in Jira, this closes the last significant context-switch in their agent workflow: you no longer need to re-explain a ticket to the AI because the AI can read the ticket itself. Sources: Atlassian blog, Cursor changelog May 19.

Cursor in Microsoft Teams (May 11) landed earlier in the month. Mention @Cursor in any Teams channel and the agent reads the full thread, picks the right repo and model based on context, and opens a PR for your team to review — all without switching apps. For companies already standardized on Microsoft 365, this reduces the gap between “we talked about building this” and “Cursor started building this” to a single @mention. Source: Cursor changelog.

The pattern here is consistent with where Cursor has been heading since 3.0: the IDE is increasingly a control surface, not a place you spend all day. The goal is that more coding work gets assigned, monitored, and reviewed from wherever your team already works — Jira, Teams, Slack — with Cursor handling the actual implementation in the background.

New in May 2026: Cloud agent environments get enterprise-grade infra

On May 13, Cursor shipped a significant upgrade to its cloud agent infrastructure — the part of Cursor 3 that runs agents in isolated environments on remote machines rather than your local laptop. The update lands squarely in Teams and Enterprise territory, but the direction matters for any founder evaluating Cursor at scale.

Multi-repo environments are now first-class: you can configure a single cloud agent environment that spans multiple repositories, so an agent working on a cross-repo change (say, a frontend repo and a shared component library) doesn’t need to be retargeted on every hop. The agent reasons across repos and delivers changes that span the whole system.

Dockerfile-based configuration — already supported — got meaningfully more capable: build secrets are now natively supported, so your cloud agent can reach private package registries without hardcoding credentials into the environment definition. Layer caching was also upgraded, cutting Dockerfile rebuild time by 70% when only non-modified layers need updating.

Governance and audit tooling are the least glamorous additions and probably the most significant for anyone running Cursor on a real team. Every development environment now has version history with rollback (admin-only rollback can be enforced). An audit log captures every action team members take on environments. Egress and secrets are now scoped at the environment level — credentials configured for one environment are not visible from any other. This closes a meaningful compliance gap that had been a blocker for regulated industries.

For non-technical founders: cloud agents are not a feature you’ll use directly. What this update signals is that Cursor is engineering toward the enterprise deployment model that will define its post-SpaceX-acquisition product roadmap. The governance layer is what gets Cursor approved inside a Fortune 500 security review. Source: Cursor changelog — Development environments for cloud agents.

New in May 2026: Cursor 3.3 — context usage breakdown

Released May 6, 2026. Cursor 3.3 adds a context usage breakdown so you can see exactly where your agent’s working memory is going — a per-line breakdown of what’s consuming context across rules, skills, MCP connections, and subagents. It sounds like a debugging utility, but it’s actually a power-user lever: once you can see that your MCP connections are eating 40% of your available context on every run, you can trim them to the ones you actually use and get noticeably better agent performance. For technical founders who’ve been running Cursor agents at scale and hitting quality issues they couldn’t diagnose, this is the first transparent view into why. Source: Cursor changelog — Context Usage Breakdown.

New in May 2026: Always-on security agents land in beta

On May 1, Cursor opened the beta for Cursor Security Review on Teams and Enterprise plans — two new always-on security agents that sit on top of the editor. The first, Security Reviewer, runs on every PR and flags auth regressions, data-handling problems, prompt-injection risks, and any agent tool auto-approvals that look suspicious — leaving inline comments at the exact diff location with a severity tag and a remediation suggestion. The second, Vulnerability Scanner, runs on a schedule against the whole codebase to catch known CVEs, outdated dependencies, and misconfigurations, and it can pipe its findings into Slack rather than waiting for someone to log in and look.

Both agents are customizable: you can adjust what triggers them, give them custom tooling, hand them house-style instructions, and pick how their output gets shared. This is Cursor’s first credible answer to the “vibe-coded apps have a security debt problem” narrative that’s dominated coverage of the category since the Lovable BOLA exposure and Base44 critical vulnerability earlier this year. For non-technical founders, the practical impact is small (these are Teams/Enterprise plan features, and you need a real PR review process to use them), but the strategic signal is meaningful: the editor that’s under SpaceX acquisition pressure is also the editor shipping the most aggressive built-in security tooling. Source: Cursor changelog.

New in April 2026: Cursor 3.2 ships with /multitask, plus GPT-5.5 lands

On April 24, Cursor shipped 3.2 alongside same-day support for OpenAI’s GPT-5.5 — both arrived together because OpenAI flipped the GPT-5.5 API on the same day, and Cursor was ready for it. The 3.2 release adds three orchestration upgrades that build on the Cursor 3 thesis (manage agents, don’t write every line). First, a new /multitask command tells Cursor to spin up async subagents that parallelize your requests instead of queuing them, and to break larger jobs into smaller chunks for a fleet of agents to tackle simultaneously — including pulling work out of a queued backlog. Second, Worktrees got a real home in the Agents Window: isolated background branches you can promote to the foreground with one click when you’re ready to test. Third, multi-root workspaces let a single agent session span multiple folders, so cross-repo changes (frontend / backend / shared lib) don’t require retargeting the agent on every hop.

Together with GPT-5.5 in the model picker, this is the most usable Cursor setup for genuine multi-task agentic work to date. For technical founders running a small team, the worktrees + multi-root combo is the change that’s most likely to land in your daily workflow — it’s the first version of Cursor where running three agent sessions across two repos doesn’t require fighting the tool. Source: Cursor changelog — Multitask, Worktrees, and Multi-root Workspaces.

New in April 2026: SpaceX signs a $60B call option on Cursor

On April 21, SpaceX and Cursor announced a partnership with an acquisition twist. SpaceX has paid for the right — a call option — to either acquire Cursor outright for $60 billion later in 2026 or pay $10 billion for “our work together” if the acquisition doesn’t close. In practical terms, Cursor becomes the AI coding arm of Elon Musk’s tech stack, and SpaceX’s Colossus supercomputer (the 230,000-GPU Memphis cluster run by xAI, which SpaceX merged with in February) becomes Cursor’s training infrastructure. Cursor CEO Michael Truell said the company had been “bottlenecked by compute” and will use Colossus to scale up its Composer model family. This effectively leapfrogs the $2B/$50B raise Cursor was in talks on as of April 17 — that round is now superseded by the SpaceX terms. For Cursor users, the product doesn’t change today. What changes is the ownership trajectory and the model supply chain. If you’re worried about vendor risk under Musk-controlled entities — that’s a legitimate consideration for customer-data-heavy apps built on Cursor-managed infra, and worth weighing alongside the underlying developer experience. See our explainer on the SpaceX-Cursor deal for what it means for founders and PMs making tool choices right now.

Business update: $2B ARR, the $50B raise that’s now moot

By April 2026, Anysphere — Cursor’s parent company — has crossed $2 billion in annualized revenue, roughly doubling its run rate in three months. On April 17, Bloomberg and TechCrunch confirmed the company was raising $2 billion at a $50 billion pre-money valuation — that financing was superseded four days later by the SpaceX deal above. About 60% of revenue now comes from enterprise, with more than half the Fortune 500 using Cursor across engineering teams. At the implied $60B acquisition price, Cursor is being valued as core software infrastructure, not a developer productivity tool. That’s a significant distinction for anyone making long-term tool bets — the ownership question now lives inside the Musk/xAI/SpaceX orbit rather than a conventional private-tech cap table.

Also in April 2026: BugBot gets smarter

Cursor shipped a meaningful BugBot update this week. BugBot — which reviews new code every time you push a change — now supports MCP (Model Context Protocol), meaning it can pull context from external tools like Linear, Jira, or Notion when reviewing a PR. It also gained real-time self-improvement: BugBot now learns from reviewer feedback on pull requests, automatically promoting useful review patterns into standing rules. Autofix has been enhanced so BugBot can not only flag issues but propose and apply patches. At 2 million PRs reviewed per month, the feedback loop is compounding fast. For technical founders using Cursor as their primary environment, these updates make the automated review layer genuinely worth enabling.

New in April 2026: Cursor 3

Cursor 3 launched on April 2, 2026 — built under the internal codename “Glass” — and it’s a more fundamental rethink than a version bump suggests. The core idea: most code will be written by AI agents, and the developer’s job is to orchestrate them, not type every line. The interface reflects that assumption completely.

The headline addition is the Agents Window: a persistent, standalone hub separate from the IDE where you spin up, monitor, and control multiple AI agents running simultaneously. Each agent gets its own task — one refactoring a module, another writing tests, another updating documentation — and you track their status, reasoning, and progress in real time from a unified sidebar. You can trigger agents from mobile, Slack, GitHub, or Linear, not just from inside the editor.

Other meaningful additions include Design Mode, which lets you annotate UI elements directly in the browser and pass those references to an agent for precise iteration; a /worktree command that creates isolated git worktrees so agents work in parallel on the same repo without conflicts; and native multi-repo support so a single session can span more than one codebase.

For non-technical founders, the Agents Window is still not an entry point — it’s a developer orchestration layer. But the broader direction here (manage agents, not write code) is converging on what tools like Lovable and Bolt have offered from day one. Cursor 3 is Cursor’s direct answer to Claude Code and OpenAI Codex eating into its market share among agentic workflows.

What Cursor actually is

Cursor is a fork of VS Code — the text editor that most professional developers use — with AI features deeply built in. Unlike GitHub Copilot, which adds AI as a plugin, Cursor redesigns the whole experience around AI assistance. It has a chat panel that understands your full codebase, autocomplete that predicts blocks of code rather than single lines, and a “Composer” mode that can make coordinated changes across multiple files from a single description.

For a developer, this is a productivity multiplier. Experienced engineers report writing 40–60% less code manually because Cursor’s suggestions are good enough to accept. Multi-file changes that used to take an hour can be drafted in five minutes.

The non-technical founder reality check

Here’s the honest question: can you use Cursor to build something if you don’t code?

Technically yes. Practically, it depends.

If you have some coding background — a CS degree from ten years ago, a bootcamp under your belt, comfortable reading JavaScript even if you can’t write it cold — Cursor is actually powerful in your hands. You can describe what you want in plain English, review the changes it proposes, and accept or reject them. You won’t write much code, but you’ll understand enough to stay in control.

If you have zero technical background, you’ll run into a wall quickly. Cursor will generate code. You’ll hit an error. The error message will be meaningless. Cursor will try to fix it and create two more problems. Without the ability to read what it’s producing and reason about what went wrong, you’re flying blind. This isn’t Cursor failing — it’s the wrong tool for the job.

When a no-code tool is the right call

If you’re at the “I need to validate this idea” or “I need a working prototype by next week” stage, and you don’t have a technical co-founder, start with Lovable, Bolt, or Base44. These tools build complete apps from prompts and hide the code entirely. You’ll ship faster, and you won’t need to understand what’s under the hood.

Come back to Cursor — or hire someone who uses it — when you have a real product, real users, and complexity that no-code tools can’t handle.

Pricing

The free tier gives you a limited monthly allowance of AI completions. Most people who use it daily will hit the limit within a week. The Pro plan at $20/month removes those limits and gives you access to faster models. You can also bring your own Anthropic or OpenAI API key to control costs directly.

Bottom line

Cursor is the best AI-powered code editor available, and with Cursor 3’s chatbot mode, it’s now accessible to a wider range of builders than ever. If you have coding skills or a developer on your team, the IDE experience is unmatched. If you don’t, the chatbot mode gives you a real way in — though you’ll still benefit from understanding what the AI is producing. Cursor 3 is Cursor’s attempt to meet Lovable users halfway. Whether it’s convincing enough depends on whether you want a developer tool with AI bolted on (classic Cursor) or an AI-first builder with more power underneath (new Cursor).

Was this helpful?