Copilot Packs Its Bags: GitHub's AI Pair Programmer Leaves VS Code Behind

GitHub Copilot just stopped being a VS Code exclusive. Today GitHub released a public plugin that brings Copilot into Neovim, and a JetBrains marketplace plugin is slated to follow in just a couple of days. If you’ve been trying Copilot in VS Code since the technical preview opened back in June, this is the first real sign that GitHub wants the tool living wherever developers actually work, not just inside Microsoft’s own editor.

For anyone who’s missed the hype: Copilot is the AI pair-programmer built on OpenAI’s Codex model, trained on a huge swath of public code, that suggests whole lines or blocks of code as you type based on context, comments, and function names. It’s been genuinely useful for boilerplate, test scaffolding, and those “I know this pattern but don’t want to type it out” moments, though it’s also prone to confidently suggesting code that’s subtly wrong or just doesn’t compile. You still have to read what it gives you.

The Neovim plugin is the more interesting move here, honestly. VS Code has built-in extension APIs that make integrating something like this relatively straightforward, and it’s Microsoft’s own product, so that pairing was never a surprise. Neovim is a different animal — it’s the editor of choice for a huge chunk of terminal-first developers who have spent years customizing their workflows with Lua and Vimscript, and getting an AI suggestion engine to feel native there rather than bolted-on is a real engineering lift. Early reports suggest it works over the same completion mechanism, showing ghost-text suggestions inline, which is the right call — nobody wants a popup window interrupting their flow.

JetBrains support matters for a different reason: reach. IntelliJ, PyCharm, WebStorm, and the rest of the JetBrains lineup are the default for a massive population of Java, Python, and web developers, especially in enterprise shops. If Copilot lands cleanly in that ecosystem, GitHub effectively goes from “interesting VS Code extension” to “tool that touches most of the professional developer population” in one release cycle.

What I’ll be watching is whether the experience holds up outside VS Code’s tightly integrated environment. Copilot’s usefulness depends heavily on latency and how well it reads surrounding context, and that’s easier to nail in an editor GitHub’s own engineers use daily than in editors built by entirely different communities with different plugin architectures. If the Neovim and JetBrains versions feel like second-class citizens — laggy, less context-aware, missing settings — that’s going to show up in developer forums fast.

Still, the trajectory is clear. Four months ago this was a limited technical preview available to a lucky few. Now it’s expanding across the two other most popular editor ecosystems in software development. Whether or not you’re sold on AI-assisted coding as a category, it’s getting harder to avoid having an opinion about it.