Jonathon's AI Wiki

Cursor — AI-Native Code Editor (Anysphere)

15 min read

Source: ai-research/cursor-homepage-2026-07-02.md, ai-research/cursor-pricing-page-2026-07-02.md, ai-research/cursor-models-pricing-docs-2026-07-02.md, ai-research/cursor-agent-mode-docs-2026-07-02.md, ai-research/cursor-changelog-2026-07-02.md, ai-research/wikipedia-cursor-company-2026-07-02.md, ai-research/techcrunch-spacex-acquires-cursor-2026-07-02.md, ai-research/thenewstack-claude-code-vs-cursor-vs-codex-vs-antigravity-2026-07-02.md

Cursor is an AI-native code editor built by Anysphere — a VS Code fork with agentic coding designed into the architecture rather than bolted on as an extension. It ships an autonomous Agent mode, a multi-file Composer workflow, a purpose-built Tab autocomplete model, and support for essentially every frontier LLM (Claude, GPT, Gemini, Grok) alongside its own in-house Composer model. This wiki has referenced Cursor as a comparison point in 10+ Claude AI articles without ever giving it a dedicated page — this article is that reference, written for a Claude Code-first audience evaluating whether (or when) to also run Cursor. As of this writing Cursor is also mid-acquisition: SpaceX announced a $60 billion all-stock deal to buy it on June 16, 2026, folding it into Elon Musk’s xAI.

Key Takeaways

  • Anysphere, Inc., founded 2022 by four MIT students (Michael Truell — CEO, Sualeh Asif — CPO, Aman Sanger, Arvid Lunnemark), builds Cursor as a fork of VS Code. Headquartered in San Francisco, ~300 employees as of 2025.
  • Core product surface: Agent mode (autonomous multi-step coding), Composer (multi-file scaffolding + Cursor’s own model family), Tab (predictive autocomplete, originally from the acquired Supermaven), Cloud/Background Agents, Bugbot (PR code review), a CLI (cursor-agent), an iOS mobile app (public beta, June 2026), and Automations (always-on agents triggered by GitHub/Slack events).
  • Model-agnostic by design. Cursor runs Claude Fable 5, Claude Opus 4.8, Claude 4.6 Sonnet, GPT-5.5, GPT-5.3 Codex, Gemini 3.1 Pro, Gemini 3.5 Flash, and Grok Build 0.1, plus its own Composer 2.5 — model choice is the point of the product, not a vendor lock-in decision.
  • Pricing: Hobby (free) → Pro (60/mo) → Ultra (40/user/mo) or Premium ($120/user/mo); Enterprise (custom). All individual plans include unlimited Tab completions.
  • The defining 2026 story: the SpaceX/xAI acquisition. After a meteoric funding run (seed → 3B+ ARR by May 2026), Cursor was preempted out of a planned 50B-valuation raise when xAI struck a deal in April 2026 for the right to buy Cursor outright for $60B — which SpaceX exercised on June 16, 2026. Close expected Q3 2026.
  • Positioning vs. Claude Code, in one line (per The New Stack, June 2026): Claude Code is “terminal-native, approval-first” and built for teams that want to read every diff; Cursor is a “model-agnostic IDE” for editor-bound teams that want to pick their own model and avoid vendor lock-in. Neither positioning has “won” — most operators this wiki has tracked run both.

What Cursor Is

Cursor’s agent features can search across a codebase, edit files, run terminal commands, and carry out multi-step programming tasks from natural-language instructions — the same agentic shape as Claude Code, delivered inside a familiar VS Code-derived editor window instead of a terminal.

  • Origin of Tab: Cursor acquired Supermaven (an AI code-completion startup founded by Jacob Jackson) in November 2024; the Supermaven team was folded into Cursor and its standalone product wound down in late 2025. Supermaven’s technology underlies Fusion, the model that powers Cursor Tab.
  • Origin of Bugbot: launched July 2025 as a GitHub-PR-integrated code-review tool; by June 2026 Cursor’s own changelog reports it “over 3x faster, 22% cheaper, and finds 10% more bugs” than its earlier version.
  • December 2025: Cursor acquired Graphite, a New York-based code-review startup, in a cash-and-equity deal reported well above Graphite’s prior $290M valuation — folding code review further into the core product.
  • Self-description: Cursor’s own homepage frames the company as “an applied research team focused on building the future of software development,” not merely an editor vendor — publishing research notes on secure codebase indexing, semantic search, shadow workspaces, and reinforcement learning going back to 2022.
  • Enterprise claims: Cursor’s marketing states it is “trusted by over half of the Fortune 500,” with 64% Fortune 500 usage and 50,000+ enterprises cited in secondary reporting (unverified beyond Cursor’s own claims).

Core Features

  • Agent mode — Cursor’s autonomous assistant (Cmd/Ctrl+I). Built from three components: Instructions (system prompt + rules), Tools (file editing, codebase search, terminal execution), and Model (whichever LLM you pick). Cursor explicitly tunes instructions and tools per frontier model rather than running one generic harness across all of them. Tool surface: semantic codebase search, file/folder search, web search, rule-fetching, file read (including images, for vision-capable models), file edit, shell command execution, browser control (screenshots, navigation, visual verification), image generation, and mid-task clarifying questions. No limit on tool calls per task.
  • Checkpoints — automatic local snapshots before significant Agent changes, restorable from the chat timeline. Explicitly not a Git replacement — “use them for undoing Agent changes; use Git for permanent version control.”
  • Composer — scaffolds a multi-file change in one pass (read → propose → diff → apply); the Agent extends that with autonomy (run commands, react to errors, iterate until tests pass). “Composer” is also the name of Cursor’s own model family (see Model Support below) — the product feature and the underlying model share a name, which is a common source of confusion in outside coverage.
  • Cloud/Background Agents — agents that run on their own machines to build, test, and demo features for review, with handoff between local and cloud sessions. Cursor 3 (April 2026) introduced an Agents Window for running multiple agents in parallel across local machines, worktrees, cloud sandboxes, and remote SSH — with Agent Tabs for side-by-side or grid chat views. /in-cloud spins up an isolated cloud subagent per task; a cloud agent can be asked to /babysit a PR to prepare it for merge.
  • Automations — always-on agents triggered by GitHub events (issue comments, PR reviews, workflow completions) or a Slack emoji reaction, configurable in plain language via the /automate skill; can use computer-use to produce demo artifacts of their own work.
  • Marketplace — 30+ third-party plugins (Atlassian, Datadog, GitLab, Hugging Face, and others) plus team-level plugin/skill/MCP distribution with SCIM/org-group access controls.
  • CLI and mobile — cursor-agent runs Cursor from a terminal (curl https://cursor.com/install -fsS | bash); a public-beta iOS app (June 2026) adds cloud-agent launch, voice input, Live Activities/push notifications, and Remote Control — directing an agent running on your desktop from your phone.
  • Design Mode — annotate UI elements directly in a built-in browser (Cursor 3 feature).

Pricing (as of 2026-07-02, cursor.com/docs/models)

PlanPriceAPI usage includedNotes
HobbyFree—Limited Agent requests, limited Tab completions, no card required
Pro$20/mo$20Unlimited Tab; extended Agent limits; Bugbot; Cloud Agents
Pro Plus$60/mo$70Recommended for daily agent users
Ultra$200/mo$400Recommended for agent power users
Teams (Standard)$40/user/mopooledCentralized billing, SSO, team marketplace
Teams (Premium)$120/user/mopooled5x Standard’s Agent limits
EnterpriseCustompooledSCIM, audit logs, model/repo access controls, invoicing

Cursor’s own usage guidance: daily Tab-only users stay within the 60-100/mo total; power users running multiple agents/automations often exceed 10 input / 0.50 input / $2.50 output).

Model Support

Cursor does not train (or require) one house model — it’s a routing and harness layer over whichever frontier model you choose, plus its own agentic model tuned specifically for the editor. As of the 2026-07-02 fetch of cursor.com/docs/models, the roster is:

  • Anthropic: Claude Fable 5, Claude Opus 4.8, Claude 4.6 Sonnet
  • OpenAI: GPT-5.5, GPT-5.3 Codex
  • Google: Gemini 3.1 Pro, Gemini 3.5 Flash
  • xAI: Grok Build 0.1
  • Cursor’s own: Composer 2.5 (and a faster variant) — trained via continued pretraining on the open Kimi K2.5 base model plus large-scale reinforcement learning in environments meant to emulate real Cursor usage; Cursor’s own technical report (Composer 2, March 2026) claims roughly 4x the speed of similarly capable models, finishing most interactive turns in under 30 seconds.
  • Auto routing — Cursor selects a model automatically to balance intelligence, cost, and reliability for everyday tasks.

This model roster is a moving target — Cursor ships new model support within days of a lab’s release (Claude Fable 5, launched 2026-06-09, was already listed by this fetch). Confirm the current list at cursor.com/docs/models before relying on specifics.

The SpaceX/xAI Acquisition

The single most consequential Cursor story of mid-2026. Compressed funding and revenue timeline (Wikipedia, citing TechCrunch/Bloomberg/The Information):

DateEvent
Oct 2023$8M seed, OpenAI Startup Fund
~2024Series A, 400M valuation; by Nov 2024 bid up toward ~$2.5B
Jun 20259.9B valuation
Nov 13, 202529.3B valuation
Early 2026Reported in talks for ~50-60B valuation
Apr 21, 2026xAI strikes deal: option to buy Cursor for 10B break-up fee
Jun 16, 2026SpaceX exercises the option — $60B all-stock acquisition, Cursor placed under the xAI subsidiary; expected to close Q3 2026

Revenue climbed in step: 500M (Jun 2025) → 3B+ (May 2026), per Bloomberg.

Per TechCrunch’s reporting on the deal: the acquisition is meant to help SpaceX’s AI division (built around xAI, which SpaceX merged with earlier in 2026) “catch up to the major AI labs,” at a moment when xAI itself was in turmoil — all 11 of Musk’s xAI co-founders had left by end of March 2026, and Musk publicly said xAI “was not built right the first time around.” Before the SpaceX offer, Cursor was reportedly not going to break even on its planned $2B raise alone. The deal closed the loop on a partnership that started with xAI hiring two Cursor engineering leaders and renting Cursor compute capacity on its data centers earlier in 2026.

What this means for a Cursor evaluation today: the product roadmap, model-neutrality (will Cursor keep shipping Claude models under an xAI/Musk-owned parent?), and pricing stability are all open questions once the deal closes. This wiki will track it — see Open Questions below.

Cursor vs. Claude Code

This is the comparison this wiki’s readers actually care about. Four independent angles, from four different sources:

1. The positioning split (The New Stack, June 2026). Cursor “went the other way and stayed model-agnostic. It runs inside a familiar VS Code surface and lets you point Cursor at whichever frontier model you already pay for, so a team is not tied to one vendor’s release calendar… it asks for no workflow migration, letting developers add agency without leaving the files, tabs, diffs, and shortcuts they navigate by reflex.” Claude Code “stayed close to where it started, living in the terminal and leaning on Anthropic’s long-context reasoning, compaction, and an approval-heavy flow, which makes it strong on large-codebase work where an agent has to hold a lot in its head before touching a line… the friction is deliberate, since on a serious codebase the riskiest moment is the one just before a command runs or a file changes, and Claude Code puts a human at exactly that point.”

Claude CodeCursor
Center of gravityTerminal-native, approval-firstModel-agnostic IDE (VS Code fork)
Pulls ahead onDeep reasoning, large-codebase work, teams that want to read every diffEditor-bound teams that want to choose their own model and avoid vendor lock-in
Entry pricing (2026)~$20/mo (Pro)~$20/mo (Pro)
Instruction fileCLAUDE.md (own convention)Reads the shared AGENTS.md convention (also read by Codex, Copilot, Windsurf)

2. Harness architecture (Anthropic’s own Agent Platform team, on the AI and I podcast). Angela and Caitlin (Head of Product / Head of Engineering, Claude Platform) argue the industry is shifting from “generic harness, hot-swap models” to “the harness and the model get very paired” — and speculate that Cursor and similar model-agnostic tools “may already be running per-model harnesses” to get the best out of each one, though Angela stops short of confirming this for Cursor specifically. Cursor’s own Agent docs corroborate the shape of this claim directly: “Cursor’s agent orchestrates these components for each model we support, tuning instructions and tools specifically for every frontier model.” See Inside Claude’s Agent Platform.

3. Real-world dual-tool workflow (Chris’s 2026-05 coding workflow update). A solo developer running both at once on the top tier of each (200/mo Cursor Ultra): 70% Claude Code / 30% Cursor split, defaulting to Claude Code (Opus 4.7, max thinking) and switching to Cursor (GPT-5.5 extra-high, 1M context) for “very complex bugs with many edge cases” — “too expensive to use for everything” is his explicit caveat on the Cursor side. He also argues Claude Code’s remote control beats Cursor’s cloud agents for one specific reason: remote control gives a phone session access to all the local MCPs and CLIs installed on his Mac, where Cursor’s cloud agents “only have a handful of remote MCPs available.” See Chris’s AI Coding Workflow Update.

4. The vibe-coding distinction (Erik Schluntz, Anthropic, Code with Claude). Schluntz draws a sharp line: “Tight feedback loops with Cursor or Copilot are not vibe coding by Karpathy’s original definition.” Using Cursor’s Tab/Cmd+K/Agent slider while reviewing every diff as it streams is “heavy AI-assisted coding,” not vibe coding — vibe coding requires “forget[ting] that the code even exists.” Schluntz personally uses both tools together: “Claude Code starts things, Cursor for surgical line-level changes when he knows exactly what needs to change.” See Vibe Coding in Prod.

Bottom line for a WEO Marketly / Claude-Code-first operator: Cursor is not a Claude Code replacement so much as a second, editor-native surface worth having open in parallel — most operators this wiki has tracked run both rather than picking one. The decision axis is less “which is smarter” (frontier model scores are converging across tools per The New Stack) and more: do you want a terminal-approval-gated agent that reads your whole repo before touching a line (Claude Code), or an in-editor agent where you can freely swap the underlying model per task (Cursor)?

Cursor vs. GitHub Copilot and Windsurf

Briefly, since these are secondary to the Claude Code comparison above:

  • GitHub Copilot is deliberately the safe, compliant, low-disruption enterprise default — its home-field advantage is that GitHub already owns the surface where issues, PRs, reviews, and Actions live, so agent-written work flows to where it gets merged without leaving the platform. The New Stack calls this “a home-field edge as agent-written work flows to where it gets merged.”
  • Windsurf is the other prominent agentic-IDE competitor; after a widely-reported three-way 2025 acquisition scramble (a failed ~2.4B Google reverse-acquihire of its CEO and research leads, and finally an outright acquisition), Windsurf’s product, brand, and remaining team are now owned by Cognition (maker of the Devin coding agent), acquired July 2025.
  • All four tools (Codex, Cursor, Copilot, Windsurf) — but notably not Claude Code — read the shared AGENTS.md repo-convention file; Claude Code keeps its own CLAUDE.md format. This is the one genuine format fork in an otherwise converging market.

Open Questions

  • Exact comparative market share is genuinely contested as of this ingest. Different 2026 sources rank Cursor and Claude Code in opposite orders depending on methodology — self-reported developer-adoption surveys, enterprise card-spend trackers, and revenue-based rankings each tell a different story, and even outlets citing the same named survey (JetBrains) report different percentages. This article deliberately does not repeat a specific “X% market share” figure for either tool; treat any single headline number with skepticism until its methodology is stated.
  • Post-acquisition trajectory unknown. The SpaceX/xAI deal is expected to close Q3 2026. Whether Cursor keeps its model-agnostic positioning (including continued first-class Claude support) under xAI ownership, and whether pricing or product priorities shift, is unresolved and worth a dedicated refresh once the deal closes.
  • Independent verification of enterprise-adoption claims (“over half the Fortune 500,” 64% Fortune 500, 50,000+ enterprises) — these come from Cursor’s own marketing; no independent audit was found in this research pass.
  • Chris’s AI Coding Workflow Update — the richest real-world dual-tool account in this wiki: 70/30 Claude Code/Cursor split, when-to-switch heuristics, remote control vs. cloud agents, CMUX replacing Cursor’s terminal.
  • Inside Claude’s Agent Platform — Angela & Caitlin — the harness-pairing theory (“the harness and the model get very paired”) that frames why Cursor’s per-model tuning is architecturally significant, not cosmetic.
  • Vibe Coding in Prod — Erik Schluntz — draws the line between Cursor’s tight-feedback-loop assisted coding and true vibe coding, plus a concrete Claude-Code-starts / Cursor-finishes workflow pattern.
  • MCP — Model Context Protocol — the open protocol both Cursor and Claude Code speak as MCP clients, and the reason MCP servers built for one generally work in the other.
  • Claude Surfaces Decision Framework — this wiki’s closest existing “which tool for which task” framework; read alongside this article when deciding whether Cursor belongs in a WEO Marketly toolchain at all.
  • Claude Fable 5 and Claude Mythos 5 — the model Cursor added to its roster within days of launch; also the model an independent Cursor-bench score (72.9%, per aggregated launch-week reporting) was measured against.

Try It

  1. If you’re already a Claude Code user, don’t treat this as either/or. Install Cursor’s free Hobby tier alongside your existing Claude Code setup and try the same real task in both — a multi-file refactor is the clearest side-by-side test.
  2. Use the model-agnostic angle deliberately. If a task needs 1M-token context or a specific non-Claude model’s strengths, Cursor is the fastest way to try GPT-5.5, Gemini 3.1 Pro, or Grok Build 0.1 against the same codebase without leaving an editor.
  3. Point Cursor at Claude models you already pay for. Cursor’s Pro plan (20 of included API usage) can run Claude Fable 5 or Claude Opus 4.8 directly — useful for testing whether an in-editor Claude experience changes your workflow versus the terminal.
  4. If evaluating for a team, read the Teams tier carefully (Standard 120/user/mo for 5x the agent limits) against Claude Code’s own team pricing before committing — cost-per-accepted-change, not the sticker price, is the number The New Stack’s reporting says actually matters at scale.
  5. Watch the SpaceX/xAI close (expected Q3 2026) before making a long-term single-vendor bet on Cursor — re-check this article’s Open Questions section after the deal closes for any positioning or pricing changes.

Graph View

Backlinks