This is a real guide, generated for an example user. Yours is built from a short interview about how you actually work — your saved prompts, your projects, your do-not-break workflows. Free during beta.
How to move from Claude Code to Cursor.
A step-by-step playbook to move Claude Code workflows into Cursor — copy-ready, checkable, and checked against each tool’s own docs.
- Prepared for
- An example 3-person marketing team
- Sources
- 16 verified sources
9 steps (7 core), 4 paste-ready assets, 13 to confirm in Cursor.
- CLAUDE.md repo context
- Custom slash commands
- MCP server integrations
- Subagents for parallel work
Setup steps
Work through these in order. Check each off as you go; your progress is saved on this device.
Install Cursor (a VS Code fork). On first launch, open the integrated terminal (Ctrl/Cmd+` ) so you keep a terminal-native surface, and open the Agents Window: Cmd/Ctrl+I for the Composer/agent pane, Cmd/Ctrl+L for the chat sidebar, and Cmd/Ctrl+Shift+M for the full-screen tab view (Cursor 3.4+). Keep the integrated terminal docked alongside the full-screen agent tab to most closely reproduce the Claude Code REPL feel. If you want a literal CLI surface, install the Cursor CLI and run `cursor` headlessly in the terminal. Verify in the UI: the version-specific shortcuts (3.4 full-screen tab) should be double-checked against your installed build.
Interactive chat replTerminal shell accessTerminal ai commands
A few things to confirm
We flag these up front so nothing surprises you — a short list to double-check in Cursor as you go.
- 13 items are flagged to confirm in Cursor — check the menu paths and field names as you go.
- Note: the daily, high-criticality 'Terminal agentic loop' workflow means this guide should get a human review before you rely on it for production work.
Paste-ready assets
Workflows from Claude Code, rewritten to paste straight into Cursor.
CLAUDE.md — project conventions and architecture notes the agent reads each session.
# AGENTS.md > Cross-tool project context. Read automatically by Cursor (and Claude Code) out of the box. > Ported from CLAUDE.md. Keep this as the single source of truth. ## Project conventions - <paste your conventions from CLAUDE.md here verbatim> - Code style, naming, and formatting rules - Commit / branch conventions ## Architecture notes - <paste your architecture overview here> - Key modules and their responsibilities - Data flow and integration points ## How the agent should work here - Prefer multi-file, end-to-end edits; stage diffs for review. - Use Plan mode (Shift+Tab) for non-trivial tasks before editing. - Reference files/folders with Cursor @-symbols (@file, @folder, @codebase, @Git) instead of bare @path. ## Memory layering (was CLAUDE.md tree) - User-level prefs (was ~/.claude/CLAUDE.md) -> set as Cursor User Rules - Project context (this file) -> AGENTS.md at repo root - Local-only notes (was ./CLAUDE.local.md) -> keep out of version control
Same-day walkthrough
This sample was built for an example user. Yours gets built around how you work.
A 15–25 minute interview captures your workflows, then the guide is generated for you — same structure, your prompts, your projects, your gotchas. Nothing in your stack is changed or cancelled by any of it.