Cursor

• June 24, 2026: Fresh source check confirmed Cursor’s pricing page and Teams pricing update still list Hobby free, Individual from $20/month, Teams Standard at $40/user/month, Teams Premium at $120/user/month monthly, Enterprise custom, Pro+ for daily agent users, and Ultra for agent power users. No buyer recommendation changed, but the price range now explicitly reflects Teams Premium.
• June 23, 2026: Fresh source check confirmed Cursor’s pricing page and Teams pricing update still list Hobby free, Individual from $20/month, Teams Standard at $40/user/month, Teams Premium at $120/user/month monthly, Enterprise custom, Pro+ for daily agent users, and Ultra for agent power users. No buyer recommendation changed.
• June 15, 2026: Disney’s AI coding push turned token budgets and release quality into buyer checks. The reported Disney guidance is a useful enterprise signal for Cursor buyers: measure accepted, reviewed, test-passing work rather than raw token usage, and keep rollback, backup, and post-release quality gates in the rollout plan.
• June 20, 2026: Cursor was rechecked for the Cursor vs Grok loop against official pricing, changelog, Teams pricing, and the current xAI pricing, model, Grok Build, and enterprise docs. The buyer split is now sharper: Cursor is the finished daily AI IDE and agent workbench, while Grok is an xAI-native coding-agent/API lane to benchmark when X context, Grok Build, or broader xAI platform fit matters.
• June 20, 2026: Cursor was rechecked for the Cursor vs DeepSeek loop against official pricing, changelog, Teams pricing, Data Use, Enterprise, CLI, and Composer 2.5 sources. The buyer split is now clearer: Cursor is the full AI-native IDE and agent workbench, while DeepSeek is a low-cost coding-model/API route. Cursor also added Automations improvements on June 18 and cloud subagents plus cloud environment setup on June 17, so agent cost controls now need to cover always-on automations, /in-cloud work, Bugbot, and Teams Standard/Premium usage pools.
• June 10, 2026: Cursor says Bugbot is now over 3x faster, 22% cheaper per run, and finds 10% more bugs on average. It is now powered by Composer 2.5, respects model block lists, supports /review, /review-bugbot, and /review-security before pushing, and can sync local review results with GitHub/GitLab PR review.
• June 5, 2026: Cursor 3.7 improved Design Mode so agents can act on multi-selected UI elements and queued voice feedback in the browser. This matters for front-end teams because Cursor is now a visual editing loop as much as a code editor.
• June 4, 2026: Cursor added SDK custom tools, auto-review for local tool calls, JSONL/custom run stores, nested subagents, and reliability fixes. This makes Cursor more relevant to CI, custom internal agents, and scripted automation, not just desktop IDE use.
• June 3, 2026: Enterprise organizations became generally available, giving admins organization, team, and group layers for security, governance, budget, feature, model-access, spend-limit, and agent-permission controls.
• May 22, 2026: Cursor said Gartner named it a Leader in the 2026 Magic Quadrant for Enterprise AI Coding Agents. Treat this as an enterprise-procurement signal, not a substitute for hands-on testing against Codex, Claude Code, and GitHub Copilot on your own repos.
• May 20, 2026: Cursor 3.5 added Automations to the Agents Window, plus multi-repo and no-repo automation setups. This makes Cursor less just an IDE and more a recurring-agent control plane.
• May 18, 2026: Cursor released Composer 2.5, its latest in-house coding model. Cursor says it is substantially better than Composer 2 for sustained long-running tasks and complex instruction following; published pricing is $0.50/M input and $2.50/M output for Standard, with Fast/default at $3.00/M input and $15.00/M output.
• May 6, 2026: ServiceNow Build Agent reached Cursor and other major AI coding tools. Cursor users building ServiceNow apps can pull platform context into their IDE workflow, but teams should review permissions and deployment approvals before broad rollout.
• May 1, 2026: The MCP STDIO command-execution flaw made Cursor’s MCP layer part of the shell-access threat model. Cursor users should audit mcp.json, disable automatic registration where possible, and sandbox third-party servers.
• May 1, 2026: Replit argued for independence as Cursor deal talk reshaped AI coding. Cursor’s reported SpaceX/xAI acquisition option keeps strategic-owner risk and infrastructure upside central to how enterprises evaluate the IDE.
• April 27, 2026: Cursor and Claude were named in a reported PocketOS database-deletion incident. Treat it as an agent-permissions and backup-design warning, not proof that AI coding tools should never touch infrastructure.
• April 22, 2026: SpaceX and xAI lined up a $60B option to buy Cursor. It is an option and partnership, not a completed acquisition, but it makes Cursor’s long-term independence a live strategic question.
• April 23, 2026: Google discloses 75% of internal new code is AI-generated. Hyperscaler benchmark for agentic-coding adoption; validates Cursor’s position as mainstream IDE default.
• April 21, 2026: Moonshot Kimi K2.6 ships with Agent Swarm mode. Strong open-weights coding scores (SWE-Bench Pro 58.6, HLE-with-tools 54.0) make Kimi a viable BYO-key backbone for self-hosted enterprise Cursor deployments.
• April 17: Cursor in talks for $2B+ round at $50B valuation. Nearly doubles the $29.3B valuation from 6 months ago. $2B ARR in Feb 2026. Thrive and a16z co-lead; Nvidia and Battery participating.
• April 16: Systemic MCP vulnerability exposes 200k servers. Cursor’s MCP servers; prefer first-party or sandboxed.
• April 16: OpenAI Codex Desktop ships as “super app” with computer use plus Memory combo is the long-term threat to IDE-as-home paradigm.
• April 17: Cursor shipped same-week support for Anthropic’s then-new flagship model, alongside Windsurf, Zed, and Continue. Treat exact model availability as a live model-catalog question, not a permanent page claim.
• April 2: Cursor 3 release makes the Agents Window the primary interface. Agent-first IDE shift; traditional editor view moves to a background role for users opting into the new layout.

Cursor’s supported model catalog, Auto routing, and in-house Composer 2.5 are the model story. Exact third-party model availability, token pricing, data-retention posture, and usage burn are plan/account dependent, so buyers should check the live model picker, usage dashboard, and admin policy settings before procurement.

Pick Cursor if you want the strongest GUI-first AI IDE in June 2026. Cursor’s Agents Window orchestrates parallel agents across local worktrees, cloud sandboxes, browser/mobile cloud surfaces, and remote SSH, with Design Mode for selecting UI elements in a live browser preview and Bugbot for PR review. Composer 2.5, CLI/SDK agents, and Automations make it more than autocomplete.

Skip it if a CLI agent loop is what you actually want. Claude Code outmatches Cursor on autonomous terminal workflows, and GitHub Copilot is cheaper ($10/mo) if you’re happy with single-file completions on stock VS Code. JetBrains, Vim/Neovim, and Zed users have no path into Cursor. It’s a full editor fork, not an extension.

Who pays which tier: Hobby (free) for evaluation, Individual starting at $20/mo for serious users, Pro+ for daily agent users, Ultra for agent power users, Teams at $40/user/mo for collaboration/admin, and Enterprise for pooled usage, SCIM, model/MCP/repository controls, audit logs, and larger governance needs.

• Individual usage can burn fast. The entry paid plan can run short for heavy agent users. Power users should check Pro+/Ultra-style upgrade economics before assuming $20/month is enough.
• Frontier-model routing is the cost trap. Higher-capability third-party models consume usage faster than routine options. Use Composer 2.5 Standard or Auto mode for routine work and reserve expensive models for hard problems.
• Bugbot is not free review magic. The June 10 update improves speed and per-run economics, but broad /review or PR automation can still create meaningful usage if teams review every branch without rules.
• SDK and CLI agents need policy. Custom tools, nested subagents, headless CLI runs, and auto-review can be powerful in CI, but teams should define tool permissions before letting agents mutate repos or infrastructure.
• Enterprise controls have layers. Organizations, teams, and groups can create different model, budget, and permission outcomes. The most permissive setting can win when users belong to multiple scopes, so test admin policy inheritance.
• VS Code lock-in. Cursor is a full editor fork. JetBrains, Vim/Neovim, Zed, and Emacs users have no entry path. Migrating out later means reinstalling extensions and settings on stock VS Code.
• Not a fully autonomous agent. Cloud Agents iterate inside a sandbox, but the Agents Window is still a supervised workbench. Claude Code’s terminal loop is more aggressive at self-correcting on test failures and build errors.
• Diff UI can desync on long agent runs. Multi-agent sessions in worktrees occasionally surface stale diffs in the Agents Window; refresh or reopen the worktree to force-sync.
• MCP configs can become shell access. The May 1 MCP STDIO flaw makes plugin/config hygiene a first-order security requirement for Cursor teams using MCP.
• Model-hopping inflates spend. Users switch models mid-session and burn more usage than expected. Pin a default and deviate deliberately.
• Background/Cloud Agents rename is still confusing. Cursor 2.0 (Oct 2025) renamed Background Agents to Cloud Agents. Documentation and third-party tutorials from late 2025 still use both names interchangeably.
• Privacy Mode is not the same as no processing. Cursor’s June 9 data-use page says Privacy Mode prevents training by Cursor and model providers and uses ZDR agreements, but backend prompt-building, codebase indexing, temporary encrypted file caching, provider abuse classifiers, and non-ZDR model opt-ins still need review.

This page was produced by the aipedia.wiki editorial pipeline, an automated system that ingests vendor documentation, normalizes factual claims, verifies pricing and model details against primary sources, and generates the editorial analysis you are reading. No individual human wrote this review. Scoring follows the four-dimension rubric at /about/scoring/ (Utility x Value x Moat x Longevity, unweighted average). Last verified 2026-06-24 against cursor.com/pricing, Cursor Data Use, Cursor Enterprise, Cursor CLI, the Cursor changelog, Cursor Teams pricing, the Cursor Composer 2.5 changelog, and the Cursor Gartner recognition post.

Is Cursor free to use? Yes. The Hobby plan is free with limited Tab completions and Agent requests. It’s enough to evaluate Cursor but not for daily professional work. Pro at $20/mo is the standard paid entry point.

How should I think about models in Cursor? Treat model access as a live product surface. Cursor supports a plan/account-dependent catalog plus Auto routing and Composer 2.5. The current official product pages name Cursor, Anthropic, OpenAI, Gemini, xAI, and Auto-style routing, but account policy, model block lists, pricing, and retention settings still decide what your team can actually use.

What’s new in Cursor 3.0? Cursor 3.0 (released April 2, 2026) reorganizes the editor around the Agents Window: a multi-agent workbench with parallel agents across local, worktree, cloud, and remote-SSH environments, Design Mode for clicking on UI elements in a live browser preview, and Best-of-N runs for side-by-side model comparison.

Cursor 3.1 (April 13) added a tiled layout and upgraded voice input. The April 15 release introduced Canvases (interactive visualizations inside the Agents Window).

Cursor 3.5 (May 20) added Automations to the Agents Window, including multi-repo and no-repo automation setups. Composer 2.5 arrived on May 18 as Cursor’s latest in-house coding model. The June 3-10 updates added Enterprise organizations, SDK custom tools/auto-review/nested subagents, Design Mode/context-reporting improvements, and a faster Composer 2.5-powered Bugbot.

What’s the difference between Pro, Pro+, and Ultra? All three are aimed at different usage intensity. The public pricing page shows Individual starting at $20/month, recommends Pro+ for daily agent users, and recommends Ultra for agent power users. Heavy Cloud Agents, Composer, CLI/SDK automation, Bugbot, and frontier-model sessions should be modeled from the live usage dashboard rather than the sticker price alone.

How does Cursor use my code data? Cursor’s June 9 data-use page says Privacy Mode prevents training by Cursor and model providers and uses zero-data-retention provider agreements. It also says requests still go through Cursor’s backend for prompt building, indexing uploads code chunks for embeddings, temporary encrypted file caching is used, and abuse classifiers/provider policies can still affect retention. Regulated teams should read the Data Use and Security pages before rollout.

Cursor or Claude Code? Different shapes. Cursor is a GUI-first editor with a multi-agent window. Claude Code is a terminal-first autonomous agent.

Use Cursor when you want an editor with an Agents Window attached. Use Claude Code when you want the agent to run the whole loop in a terminal with minimal human supervision. Many developers use both: Cursor for interactive work, Claude Code for batch agentic runs.

What happened to Background Agents? Cursor 2.0 (October 29, 2025) renamed Background Agents to Cloud Agents. Functionality expanded in Cursor 3.0 with local-to-cloud handoff and self-hosted deployment support for enterprises that need code and execution to stay inside their own network.

Does Cursor work with JetBrains, Vim, or Zed? No. Cursor is a VS Code fork, not a plugin. Users on other editors should look at GitHub Copilot, Cline, Continue, or Aider depending on the editor and workflow.

• Category: AI Coding
• Alternatives: Claude Code · GitHub Copilot · Windsurf · Cline · Aider · Continue · Zed
• Compare: Antigravity vs Cursor, Cursor vs Windsurf