How to switch from GitHub Copilot to Cursor without losing your setup

Copilot → Cursor cheat sheet

Step 1: Import your VS Code setup

Cursor is based on the VS Code codebase. Open Cursor Settings (Cmd/Ctrl+Shift+J), go to General → Account, and under VS Code Import click Import. That transfers your extensions, themes, settings and keybindings.

Moving between machines? Export a profile in VS Code (Preferences: Open Profiles (UI) → ⋯ → Export Profile) and import it in Cursor from the same Profiles screen.

Source: Cursor VS Code migration docs.

Step 2: Move your Copilot instructions

Cursor's docs list four rule sources: Project Rules (.cursor/rules), User Rules, Team Rules, and AGENTS.md. copilot-instructions.md isn't one of them, so copy its contents over.

Easiest: one AGENTS.md for both tools

GitHub's docs say Copilot agents use the nearest AGENTS.md in the directory tree, and Cursor reads AGENTS.md in the root and subdirectories. If teammates stay on Copilot, one plain-markdown file keeps both tools in sync.

# AGENTS.md
## Code style
- Use TypeScript for all new files
## Build and test
- Always run npm install before npm test

More control: Cursor project rules

Repo-wide instructions become an always-on rule:

# .cursor/rules/project.mdc
---
alwaysApply: true
---
(paste the contents of .github/copilot-instructions.md here)

Path-specific Copilot files map almost one-to-one. Copy the applyTo glob into globs:

# .github/instructions/models.instructions.md   (Copilot)
---
applyTo: "app/models/**/*.rb"
---

# .cursor/rules/models.mdc   (Cursor)
---
globs: app/models/**/*.rb
alwaysApply: false
---

Gotcha: project rules must use the .mdc extension. A plain .md file in .cursor/rules is ignored. Cursor also suggests keeping each rule under 500 lines.

Keep the Copilot files if anyone still uses Copilot. Copilot code review on GitHub reads repository instructions from the PR's head branch, so deleting them changes those reviews.

Sources: Cursor rules docs · GitHub repository custom instructions.

Step 3: Port your MCP servers

Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project). Cursor's file uses a top-level mcpServers object; VS Code's .vscode/mcp.json uses servers. Don't copy one into the other without checking the format, and don't paste API keys into files you commit.

Sources: Cursor MCP docs · VS Code MCP docs.

Step 4: Keep secrets out of context

Cursor already skips files in .gitignore and a default list that includes .env* and lockfiles. Add a .cursorignore (gitignore syntax) for anything else, and consider global ignore patterns such as **/.env, **/*.pem and **/*.key. Cursor notes that agent terminal and MCP tools can't be blocked by .cursorignore, so it isn't a complete security control.

Source: Cursor ignore file docs.

Step 5: Pick a Cursor plan (check this before you cancel Copilot)

• Plus, $8/mo: Grok models only. Cheaper than Copilot Pro ($10) if Grok and Composer are enough for you.
• Premium, $30/mo: 4x Plus usage, plus Claude, GPT and other third-party models, which are billed separately at API list price from first use.
• Super $100 / Ultra $200: 15x and 50x Plus usage.
• Teams: from $30/seat, vs Copilot Business at $19/seat.

Honest take: if Claude or GPT through Copilot Pro is what you rely on, Cursor will usually cost more for the same models. Switch for Cursor's agent-first IDE and cloud agents, not to save money. Try Cursor Free on a real repo first, and keep Copilot until you're sure.

Sources: cursor.com/pricing · GitHub Copilot plans. Checked Oct 19, 2026. Full breakdown: Cursor vs Copilot.

FAQ

Does Cursor read .github/copilot-instructions.md?

Cursor's rules documentation lists four sources: Project Rules in .cursor/rules, User Rules, Team Rules, and AGENTS.md. copilot-instructions.md is not listed, so copy its contents into AGENTS.md or a .cursor/rules .mdc file. Keep the original if teammates or Copilot code review still use it.

What is the easiest way to share instructions between Copilot and Cursor?

Use AGENTS.md. GitHub's docs say Copilot agents use the nearest AGENTS.md in the directory tree, and Cursor supports AGENTS.md in the project root and subdirectories. One file serves both tools.

Will my VS Code extensions and keybindings work in Cursor?

Cursor is based on the VS Code codebase and has a one-click VS Code Import (Cursor Settings → General → Account) that transfers extensions, themes, settings and keybindings. You can also export a VS Code profile and import it in Cursor.

Why is my rule in .cursor/rules being ignored?

Project rules must use the .mdc extension with frontmatter (description, globs, alwaysApply). A plain .md file in .cursor/rules is ignored. Use AGENTS.md if you prefer plain markdown.

Which Cursor plan should a Copilot Pro user pick?

If Grok and Cursor's Composer models are enough, Plus at $8/month is cheaper than Copilot Pro at $10. If you depend on Claude or GPT, you need Premium at $30/month or higher, and those models are billed separately at API list price, so Cursor will usually cost more than Copilot Pro for that use.

Editorial disclosure

Rankings are not for sale. Sponsored placements and affiliate links are always labeled, and they never change our recommendations, quiz results, or comparison data. None of the links on this page are affiliate links: Cursor and GitHub don't pay us. Editorial policy.