Cursor for the change you type. Claude Code for the change you describe.

Cursor and Claude Code run the same coding-agent loop; the difference is where you supervise it. Cursor puts the agent in a VS Code-based editor, where you steer each change as it lands. Claude Code starts in the terminal, built for long, scripted, guarded runs. Pick by how much supervision the task needs, and hold both to one verification gate. AI Developer Toolkit teaches all three tools side by side: 400+ guides and 100+ recipes, each showing when it was last updated.

$59.99 once for 12 months of access. Nothing renews on its own. 30-day refund on a first purchase.

Compare data, updated
2026-10-16
Cursor docs
2026-08-28
Claude Code 2.1.283
2026-09-26
List prices captured
2026-09-26

Each cell below repeats its own date. Where a feature is not in the docs we read, the cell says so.

Which one fits how you work?

Tick the lines that are true for you. Each one is a verdict line from the toolkit’s compare data, checked 2026‑10‑16.

Pick Cursor if

Editor-first: you steer each change as it lands

Pick Claude Code if

Terminal-first: you review the result

  • EvidenceLoop
  • EvidenceHarness
  • EvidenceLoop

0

Cursor lines ticked

0

Claude Code lines ticked

Tick what is true for you.

The count and the lean update as you tick. Nothing is sent anywhere.

Verdict lines and the use-both advice: the toolkit’s compare data for Cursor vs Claude Code, last updated 2026‑10‑16.

Station by station.

The jobs a coding-agent workflow has to do, with what each tool names for them. The note beside each station says whether the difference should change your choice.

Intent

Project instructions, skills, plan mode

Same shape Both read a project instruction file and install skills the same way. Claude Code reads CLAUDE.md (and by default AGENTS.md only when there is no CLAUDE.md, v2.1.277+); Cursor reads Rules and AGENTS.md.

Cursor

  • Rules
  • Cursor's docs: AGENTS.md in the project root and in subdirectories (nested files combine, the more specific one wins), and CLAUDE.md read the same way and always applied; .cursorrules is legacy Cursor token management guide, 2026-10-12
  • The agent runtime in @cursor/sdk 1.0.32 loads a root and nested AGENTS.md unconditionally, and CLAUDE.md only with third-party config loading on, while Cursor's docs say CLAUDE.md is always applied Cursor token management guide, Cursor SDK 1.0.32, 2026-09-26
  • Agent Skills
  • Plan Mode

Cursor docs, 2026-08-28

Claude Code

  • CLAUDE.md; by default reads AGENTS.md only when there is no CLAUDE.md (v2.1.277+), and the /config Project instructions setting loads both
  • Skills in .claude/skills/; bundled /code-review, /batch, /simplify
  • Plan mode: /plan, Shift+Tab, --permission-mode plan

Claude Code 2.1.283, 2026-09-26

Harness

Permissions and approvals, sandbox, MCP, hooks, organisation policy

Differs Both run hooks that can block and both can refuse reads of chosen files: Claude Code with Read deny rules, Cursor's agent runtime with .cursorignore. Claude Code documents 33 hook events; Cursor's hooks exchange JSON over stdio, and its run modes are Auto-review, Allowlist and Run Everything (Cursor docs, checked 2026-10-12).

Cursor

  • Run modes: Auto-review (the recommended default), Allowlist and Run Everything Cursor docs, Cursor 3.24, 2026-10-12
  • Auto-review runs shell commands in a sandbox when possible; sandbox.json configures it Cursor docs, Cursor 3.24, 2026-10-12
  • Hooks: JSON over stdio, before or after agent-loop stages; can block
  • MCP
  • Organisation policy: Team and MDM settings layers (SDK 1.0.32)
  • File deny rules: the agent runtime refuses reads of paths in .cursorignore, passes the list to the shell sandbox and blocks the agent from editing the file Cursor privacy and security guide, Cursor SDK 1.0.32, 2026-09-22
  • Starting mode: Auto-review, the recommended default since 3.6 (2026-05-29) Cursor docs, Cursor 3.24, 2026-10-12

Cursor docs, 2026-08-28

Claude Code

  • Permission modes: Manual (default), acceptEdits, plan, auto, dontAsk, bypassPermissions; interactive sessions start in auto mode from v2.1.283, claude -p in Manual (auto mode there only on third-party providers or with telemetry off, from v2.1.285)
  • Sandboxed Bash: macOS Seatbelt, Linux and WSL2 bubblewrap
  • Hooks: 33 events; command, http, mcp_tool, prompt and agent handlers
  • MCP client: claude mcp add (--scope project writes .mcp.json); runs as an MCP server with claude mcp serve
  • Read deny rules in .claude/settings.json, for example Read(./.env)
  • Organisation policy: managed settings (availableModels, permissions.disableAutoMode, deniedModels; v2.1.283)

Claude Code 2.1.283, 2026-09-26

Loop

Stop conditions, /goal, /loop, scheduled runs, headless

Differs Both have /goal and a /loop skill, and both run headless (claude -p, Cursor print mode). Claude Code judges /goal with a separate evaluator model each turn; Cursor's is marked "Rolling out" (Cursor docs, checked 2026-10-12), and no evaluator is documented (checked 2026-08-28).

Cursor

  • /goal, marked "Rolling out" Cursor docs, Cursor 3.24, 2026-10-12
  • /loop bundled skill since 3.5
  • Scheduled runs: Automations, which start Cloud Agents
  • Headless: print mode (agent -p) Cursor docs, Cursor 3.24, 2026-10-12
  • Machine-readable output: --output-format text is documented Cursor docs, Cursor 3.24, 2026-10-12
  • Other output formats: not verified for this page (checked 2026-10-12) Cursor docs, Cursor 3.24, 2026-10-12

Cursor docs, 2026-08-28

Claude Code

  • /goal, judged by a separate evaluator model each turn
  • /loop bundled skill (alias /proactive)
  • Scheduled runs: Routines in the cloud (/schedule, research preview)
  • Headless: claude -p; --output-format json or stream-json; --json-schema

Claude Code 2.1.283, 2026-09-26

Graph

Subagents, worktrees, background sessions

Differs Both have subagents, worktrees and background runs, but the loop lives in different places. Claude Code starts in the terminal, uses --worktree and --bg sessions and runs the same session in the IDE, desktop and web; Cursor keeps the agent in the editor, with Worktrees and Cloud Agents in isolated VMs.

Cursor

  • Subagents, including on their own cloud VMs
  • Worktrees
  • Background sessions: Cloud Agents in isolated VMs

Cursor docs, 2026-08-28

Claude Code

  • Subagents: built-in Explore, Plan and general-purpose; custom ones in .claude/agents/
  • Worktrees: --worktree [name] (-w)
  • Background sessions: --bg, then claude attach, logs, stop
  • Cloud: web sessions (claude --cloud)

Claude Code 2.1.283, 2026-09-26

Verification

Diff review, review agents, security review, checkpoints and rewind

Same shape Both review in the session and rewind. Claude Code has /code-review, /security-review and checkpoints with /rewind; Cursor has Agent Review, /review, /review-security and checkpoints that restore files only (Cursor docs, checked 2026-10-12), plus Bugbot on the pull request.

Cursor

  • In the session: Agent Review (/agent-review) and /review, which runs /review-bugbot Cursor code review guide, 2026-09-15
  • Bugbot on the pull request
  • Security review: /review-security before the push; Security Agents on the pull request Cursor code review guide, 2026-09-15
  • Rewind: checkpoints, stored locally and separate from Git; restoring one reverts files only Cursor docs, Cursor 3.24, 2026-10-12

Cursor docs, 2026-08-28

Claude Code

  • In the session: /code-review (--fix, --comment)
  • From the shell or CI: claude ultrareview (cloud, multi-agent); managed Code Review (Team and Enterprise; generally available per Anthropic) Code review automation guide, 2026-10-16
  • Security review: /security-review
  • Rewind: checkpoints and /rewind (Esc Esc)

Claude Code 2.1.283, 2026-09-26

Release

CI and GitHub Actions, repo-event triggers, pull-request routing

Differs Cursor reviews pull requests with Bugbot and routes reviewers with PR Routing & Approval. Claude Code reviews through anthropics/claude-code-action@v1 or managed Code Review, and routes through your own CI and CODEOWNERS.

Cursor

  • GitHub Actions: Cursor CLI in GitHub Actions (documented)
  • Review on the pull request: Bugbot
  • Hand-offs: Automations triggered from Slack, Linear, GitHub, GitLab, webhooks, Sentry and PagerDuty
  • Reviewer routing and approval: PR Routing & Approval (can approve low-risk PRs)
  • Start a cloud run from code: Cloud Agents API and webhooks

Cursor docs, 2026-08-28

Claude Code

  • GitHub Actions and review on the pull request: anthropics/claude-code-action@v1
  • Hand-offs: Slack (Claude Tag for Team and Enterprise); others through MCP
  • Reviewer routing and approval: through your own CI and CODEOWNERS
  • Start a cloud run from code: Routines with an API trigger (research preview)

Claude Code 2.1.283, 2026-09-26

Editor

Tab completions, inline edit, extensions and keybindings

Differs Tab completion and inline edit (usually Cmd+K) are documented for Cursor. For Claude Code they are not found in the docs (checked 2026-09-26): the docs describe an agent, not a completion engine.

Cursor

  • The Cursor editor itself, with Tab completion and inline edit
  • Inline edit is usually bound to Cmd+K (macOS) or Ctrl+K (Windows, Linux); shortcuts move between builds Inline edit guide, 2026-09-26
  • Shortcuts are VS Code keybindings attached to Cursor's AI commands; pin them in keybindings.json Cursor shortcuts reference, 2026-09-26
  • VS Code extensions IDE migration guide, 2026-09-26

Cursor docs, 2026-08-28

Claude Code

  • VS Code and JetBrains extensions: agent panel, diffs, checkpoints
  • Tab completions and Cmd+K inline edit: not found in the docs (checked 2026-09-26). The migration guide calls Claude Code an agent, not a completion engine, and keeps your editor's completion beside it IDE migration guide, 2026-09-26

Claude Code 2.1.283, 2026-09-26

Read a gap as a gap in what we read. A line that says “not found in the docs” means we could not source it on that date. A Cursor cell with no later stamp comes from docs read before cursor.com could not be reached on 2026‑09‑26. Re-check a Cursor cell before you automate against it.

Drawing
Cursor vs Claude Code
Source
The compare data, 2026‑10‑16. Each cell above names the page and the day it was read.

Models and what they cost.

Claude Code is included in Claude Pro at $20/month, with Max 5x at $100 and Max 20x at $200. Cursor Pro lists at $20/month, Pro+ at $60 and Ultra at $200 (cursor.com/pricing, read 2026-10-12). The seat buys an allowance, and what you pay on top depends on the tool.

US list prices, 2026‑09‑26 CursorClaude Code
Models Several vendors in one picker. No single default model: Hobby uses Auto. Cursor's own pool is Grok 4.7 (which Cursor calls its flagship model), Grok 4.6, Grok 4.5 and Composer 2.5; Claude Opus 5.5, Fable 5.1, Sonnet 5.5 and Haiku 5.5 are third-party models billed at API rates; no GPT-6 model is listed (Cursor, checked 2026-10-12) Default Claude Opus 5.5 (v2.1.280+, on both release channels on 2026-10-17: stable v2.1.292, latest v2.1.302). Claude Fable 5.1 by hand with /model fable; Claude Sonnet 5.5 and Claude Haiku 5.5 when cost dominates (the haiku alias needs v2.1.293, latest channel only on 2026-10-17). Switch mid-session with /model
Context window Set by the model: Grok 4.7 has a 256K standard window and 500K long context, and Claude Sonnet 5.5 up to 1M (Cursor model pages, checked 2026-10-12) 1M tokens on Claude Opus 5.5, Fable 5.1, Sonnet 5.5 and Haiku 5.5
Entry plan $20/month Cursor ProUnlimited Tab completions, extended Agent usage limits on all models, Bugbot and Cloud Agents (cursor.com/pricing, read 2026-10-12) $20/month Claude ProOr $17/month billed annually ($200 up front); Claude Code included
Middle plan $60/month Cursor Pro+The same individual-plan features as Pro; Cursor recommends Pro+ for daily Agent users (cursor.com/pricing, read 2026-10-12) $100/month Claude Max 5xClaude Code; five times Pro usage
Top individual plan $200/month Cursor UltraThe same individual-plan features as Pro; Cursor recommends Ultra for Agent power users (cursor.com/pricing, read 2026-10-12) $200/month Claude Max 20xClaude Code; twenty times Pro usage
Team seat Teams Standard $40/user/month ($32 billed annually); Teams Premium $120/user/month ($96 billed annually), "5x the usage of a Standard seat"; Enterprise custom (cursor.com/pricing, read 2026-10-12) Team Standard $25/seat monthly ($20 annual); Team Premium $125/seat monthly ($100 annual); Enterprise $20/seat/month billed annually, plus usage at API rates

Public US list prices before tax, captured 2026‑09‑26. Regional prices, negotiated contracts, mobile-store billing and promotions can differ, so check the vendor page before you buy.

Use both, if each one earns its seat

The split follows how much supervision a task needs, not which tool is "smarter": the same model can run in both. Many teams use both on the same repository.

Make the gate identical for both, so that "which agent wrote this?" stops mattering: tests, type check and lint run in CI whichever tool opened the pull request.

Run one pull-request review bot per repository, not both: Bugbot or the Claude Code GitHub Action.

$59.99 once for 12 months of access. Nothing renews on its own. 30-day refund on a first purchase.

In the editor

A small edit in the file you have open

Tab and inline edit keep you in the file; there is nothing to delegate.

On screen

A UI component you judge by looking at it

You review each change visually while the dev server reloads.

Across the repo

A change across 10 or more files, with tests as the oracle

It runs long with hooks enforcing the gate after every edit, and you review the outcome.

In scripts

A batch job or a CI step

claude -p exposes the permission model on the command line and returns JSON.

Shared by bothOne set of project instructions (CLAUDE.md and Cursor Rules, one generated from or pointing to the other), the same MCP servers, skills installed with npx skills add <owner/repo>, and one gate: hooks, test commands and CI.
Left to each developerModel choice and editor settings.

Cursor vs Claude Code guide, Claude Code 2.1.283, 2026-09-26

“Using several of them can feel messy. I switch between Claude Code, Cursor, VS Code, GitHub, and other agents, and often have to explain the same project or problem again.”
A reader, July 2026 survey

Questions before you choose.

Something else? Write to support@developertoolkit.ai.

Does Claude Code have Tab completions?

Not that the docs we read describe (checked 2026-09-26). They call Claude Code an agent, not a completion engine, and keep your editor's completion running beside it. Tab completion and inline edit are documented for Cursor (Cursor docs, 2026-08-28).

Which one handles a large multi-file refactor better?

The docs send a change across 10 or more files with tests as the oracle to Claude Code: it runs long with hooks enforcing the gate after every edit, and you review the outcome. Cursor fits changes you judge by looking at them. Both have /goal, subagents and worktrees; Cursor's /goal is marked "Rolling out" (Cursor docs, checked 2026-10-12).

Do both support MCP servers and Agent Skills?

Yes. Claude Code adds MCP servers with claude mcp add or .mcp.json; Cursor has MCP too. Both install Agent Skills with npx skills add <owner/repo>, and a SKILL.md folder works in both once it sits in the right directory.

Which is cheaper?

The seat prices do not settle it. The entry plans list at the same price, $20/month for Claude Pro (read 2026-09-26) and for Cursor Pro (cursor.com/pricing, read 2026-10-12); above that, Claude Max 5x is $100 and Max 20x $200, against Cursor Pro+ at $60 and Ultra at $200. Both meter agent work beyond the seat, and Cursor's included-usage amounts per plan are not verified here, so price a team from your own usage.

Does this page answer your questions?

One tap, no sign-in.

not at all fully

Pick one. Learn the workflow once.

The guides cover Cursor, Claude Code and Codex side by side, in the same order, so a move to the other tool later costs you little.

$59.99 once for 12 months of access. Nothing renews on its own. 30-day refund on a first purchase.