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 GitHub Copilot to Cursor.
A step-by-step guide to move GitHub Copilot workflows into Cursor — copy-ready, checkable, and checked against each tool’s own docs.
- Prepared for
- An example 3-person marketing team
- Sources
- 15 verified sources
8 steps, 6 paste-ready assets, 14 to confirm in Cursor.
- Copilot Chat in the IDE
- Agent mode multi-file edits
- Curated repo context (Spaces)
- Model selection
Setup steps
Work through these in order. Check each off as you go; your progress is saved on this device.
Download and install the Cursor desktop app from cursor.com. Cursor is a full standalone IDE (a fork of VS Code / Code OSS), not a plugin — so it replaces, rather than layers onto, your current editor. On first launch, run the one-click "Import from VS Code" wizard to bring over your settings, keybindings, and extensions from VS Code (your existing dependency). Sign in / create a Cursor account. Verify in the UI that your familiar keybinds and extensions came across before continuing.
Ide foundationIde vscode forkOpen your project folder in Cursor so it can build its automatic semantic index of the workspace (AST-aware embeddings). Sign in to GitHub from the Source Control / accounts area to keep your existing GitHub dependency working for cloning, commits, and PRs. Let the workspace index finish — this is what powers @codebase search and agentic context retrieval. Verify the repo shows up in Source Control and that the indexing status completes.
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.
- 14 items are flagged to confirm in Cursor — check the menu paths and field names as you go.
- All FPM data here is provisional — verify each step in the UI as you go.
Paste-ready assets
Workflows from GitHub Copilot, rewritten to paste straight into Cursor.
/explain
Explain the selected code @selection concisely. Cover: what it does, key control flow, and any non-obvious edge cases. Code-first — reference exact symbols/lines, no filler.
- Copilot's /explain slash command has no first-class equivalent in Cursor — express the intent as a plain prompt.
- Use @-mentions (@selection / @file) to scope context, replacing Copilot's # context references.
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.