Why This Matters

If your editor doesn't support Copilot, no amount of plan or pricing will help. And if it does support Copilot but with feature gaps, you need to know which features are missing before you commit — not after you're mid-debug and discover your editor's Copilot Chat lacks slash commands.

Concept Explained

Copilot is officially supported in four editor families: VS Code, JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, RubyMine, CLion, Android Studio, DataGrip, GoLand, Rider, and the rest of the JetBrains suite), Visual Studio (Microsoft's IDE for Windows), and Neovim. Other editors (Sublime Text, Vim, Emacs, Atom, Zed, Cursor — though Cursor has its own AI integration) are not officially supported as of August 2026.

Platform limitation: support is also limited by OS. VS Code runs everywhere; JetBrains runs on Windows/macOS/Linux; Visual Studio is Windows-only; Neovim is terminal-only.

How It Works

Each editor integrates Copilot through a different plugin mechanism, but all four rely on the same underlying GitHub Copilot service and OAuth flow. The plugin is the host; the Copilot service does the work.

• VS Code — official extension from the VS Code marketplace. First-class support; new Copilot features land here first.
• JetBrains — official plugin from the JetBrains marketplace. Slightly behind VS Code on new features but functionally complete.
• Visual Studio — official extension from the Visual Studio marketplace. Windows-only. Especially strong for C#/.NET workflows.
• Neovim — official plugin via the copilot.lua Neovim plugin. Terminal-native; configuration is code-driven (Lua).

Feature parity varies: VS Code has the richest Copilot Chat experience (including custom slash commands and Extensions support); JetBrains and Visual Studio are close behind; Neovim focuses on completions and basic chat, with Extensions support maturing in 2026.

Step-by-Step Tutorial

1. Compare the four editors side-by-side

Use this comparison to pick your primary editor with Copilot:

• VS Code — best overall Copilot experience; first to receive new features; works on all OSes; free.
• JetBrains — best if you already live in IntelliJ/PyCharm/WebStorm; Copilot integrates with their refactoring and project model; paid IDE.
• Visual Studio — best for C#/.NET on Windows; deep integration with MSBuild and debugger; paid IDE.
• Neovim — best for terminal-native developers; Lua-configured; lighter feature set but extremely fast.

2. Install Copilot in VS Code

Open the Extensions view, search "GitHub Copilot", install. Also install "GitHub Copilot Chat". Sign in via device flow (see BE-04). Done.

3. Install Copilot in JetBrains IDEs

Open Settings → Plugins → Marketplace. Search "GitHub Copilot". Install. Restart the IDE. Sign in via the Copilot icon in the toolbar. Also install "GitHub Copilot Chat" plugin for the chat panel.

4. Install Copilot in Visual Studio 2022

Open Extensions → Manage Extensions. Search "GitHub Copilot". Install. Restart Visual Studio. Sign in via the Copilot icon. Note: Visual Studio for Mac has been retired; on macOS use VS Code or JetBrains Rider instead.

5. Install Copilot in Neovim

Neovim uses a Lua plugin. With lazy.nvim as your plugin manager, add to your config:

Real-World Example

A polyglot developer at a research lab uses three editors daily: VS Code for TypeScript, PyCharm for Python, and Neovim for editing config files on remote servers via SSH. They installed Copilot in all three with the same GitHub account. The transition is seamless — same completions, same chat, same credit allowance. The lesson: Copilot follows your account, not your editor. Don't feel locked into one editor to use Copilot.

Example Prompts / Commands / Code

-- lua/plugins/copilot.lua
return {
  {
    "github/copilot.vim",
    lazy = false,
    config = function()
      vim.g.copilot_no_tab_map = true
      vim.g.copilot_assume_mapped = true
      vim.keymap.set("i", "<C-J>", 'copilot#Accept("\<CR>")',
        { expr = true, silent = true, replace_keycodes = false })
    end,
  },
  {
    "zbirenbaum/copilot-cmp",
    dependencies = { "github/copilot.vim", "hrsh7th/nvim-cmp" },
    config = function()
      require("copilot_cmp").setup()
    end,
  },
}

-- After :Lazy sync, run :Copilot auth to sign in via device flow.

Accept suggestion:        Tab
Reject suggestion:        Esc
Next alternative:          Alt+]  (Option+] on macOS)
Previous alternative:     Alt+[  (Option=[ on macOS)
Trigger inline chat:       Alt+\  (Option+\ on macOS)
Open Copilot Chat panel:   Ctrl+Shift+C / Cmd+Shift+C

Accept suggestion:        Tab
Reject suggestion:        Esc
Next alternative:          Alt+.
Previous alternative:     Alt+,
Open Copilot Chat:        Ctrl+Q, type "Copilot Chat"

Common Mistakes

• Installing Copilot in an unsupported editor (e.g. plain Vim, Sublime) via unofficial plugins — these may break or leak prompts.
• Assuming feature parity across editors — VS Code leads, others follow by weeks or months.
• Forgetting to install both the Copilot and Copilot Chat extensions in JetBrains — they ship as two plugins.
• Using Neovim's old copilot.vim without copilot-cmp on newer Neovim setups — completions may not appear in some LSP contexts.
• Visual Studio for Mac — discontinued in 2024; use VS Code or Rider on macOS.
• Expecting Copilot to behave the same in each editor's debugging session — debugger integration varies.

Best Practices

• Pick one primary editor and learn its Copilot shortcuts deeply. Add others later.
• VS Code is the safest default — it gets new Copilot features first.
• If you use multiple editors, sign in with the same GitHub account in all of them.
• Update plugins monthly — Copilot ships often and the plugin updates carry security and feature improvements.
• For Neovim, pin plugin versions in your dotfiles so updates don't surprise you mid-session.
• If your editor isn't supported, use the standalone Copilot CLI (covered in IN-41) — it's editor-agnostic.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Using GitHub Copilot in VS Code
• Using Copilot in JetBrains IDEs
• Using Copilot in Visual Studio
• Using Copilot in Neovim

Official References

• Get started with Copilot in VS Code
• Using Copilot in JetBrains IDEs
• Using Copilot in Visual Studio
• Using Copilot in Neovim

Related lessons: BE-04, BE-06, BE-07, BE-12