GitHub Copilot Is Done Being a VS Code Exclusive

GitHub Copilot has spent its entire technical preview, going back to June, living inside VS Code. That made sense as a starting point — Microsoft owns both products, so the integration was always going to be tightest there. But it also meant a huge chunk of working developers were locked out simply because of editor preference. That’s finally changing.

Late last month Copilot picked up a public Neovim plugin (October 27), followed two days later by a JetBrains marketplace plugin (October 29). If you live in IntelliJ, PyCharm, WebStorm, or any of the other JetBrains IDEs, you can now get the same Codex-powered suggestions that VS Code users have been testing for months. Same story if you’re a terminal-and-Neovim purist who has been watching this whole AI-pair-programmer thing from the sidelines.

I think this matters more than it might look on the surface. A lot of the early discourse around Copilot has centered on whether the suggestions are any good, whether it’s going to replace junior devs, whether the training data situation is legally sound — all fair questions. But the more mundane issue was distribution. An AI coding assistant that only works in one editor is a novelty. An AI coding assistant that works in the editors people actually use for their day jobs is a habit, and habits are what change how software gets written.

JetBrains users in particular are a big unlock. IntelliJ alone has an enormous footprint in enterprise Java and Kotlin shops, places that are generally slower to adopt anything labeled “AI” for code that ships to production. Getting Copilot in front of that audience, even in preview form, is a real test of whether the tool holds up outside the relatively AI-friendly crowd that self-selected into the VS Code preview.

The Neovim plugin is a different kind of signal. Neovim users tend to be the type who configure everything by hand and resent anything that feels like magic happening behind the curtain. If Copilot can win over that crowd — or at least get them curious enough to try it — that’s a good sign the underlying suggestions are useful enough to overcome some deep-seated skepticism about IDE bloat.

What I’ll be watching for over the next few months: usage patterns. Does completion quality hold up across languages the way it does for Python and JavaScript, which seem to be Copilot’s strongest suits? Does latency stay reasonable once GitHub isn’t just serving a smaller pool of VS Code beta testers? And does GitHub start talking pricing, since “technical preview” free access can’t last forever if this becomes a real product line.

For now, if you’ve been curious but didn’t want to switch editors just to try it, that excuse is gone. Worth ten minutes to see whether it actually speeds up your day-to-day, or whether it’s still more sizzle than steak.