Move your team from Claude Code to Cursor.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Cursor — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Claude Code is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Claude Code is built on the Claude Agent SDK (TypeScript and Python references at docs.claude.com/en/docs/agent-sdk/), so you can lift the same loop — tool use, sub-agents, MCP, skills, hooks — into your own apps and authenticate with a Claude Pro/Max/Team/Enterprise plan or a Console API key. Cursor does NOT publish an equivalent programmable SDK that exposes its agent loop; Cursor's programmatic surface is the Cursor CLI (`cursor` headless mode, GitHub Action) and the MCP Extension API for plugging in tools. Building custom agentic apps that mirror Cursor's behavior is therefore much harder than mirroring Claude Code's.
- Warning: Reverse direction (Cursor -> Claude Code SDK) is N/A — you can't extract Cursor's agent into a redistributable SDK; the closest move is to call Cursor CLI as a subprocess in CI.
- Warning: Tab autocomplete is not exposed in any SDK on either side — it stays inside the Cursor product surface.
- Warning: Anthropic SDK plan-based auth (using a Pro/Max subscription) is documented in a support article; from 2026-06-15 Agent SDK / `claude -p` usage draws from a separate per-user monthly credit instead of counting against the plan's interactive Claude Code limits.