If you lean on GitHub Copilot inside a JetBrains IDE, it may be time to check which version you’re actually running. According to a report from Neowin, GitHub Copilot JetBrains support is winding down for some older versions, and the change could land on your workflow sooner than you’d expect.
What’s happening with GitHub Copilot JetBrains support
In short, GitHub Copilot — Microsoft’s AI coding assistant — is dropping compatibility with certain older releases of JetBrains integrated development environments. That family includes IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, RubyMine, Rider, and DataGrip, among others. If your IDE sits in the affected range, the Copilot plugin will eventually stop working until you move to a supported version.
Neowin frames the change as “looming,” which points to something in the near term rather than an overnight switch. The summary doesn’t spell out the exact list of affected versions or a hard cutoff date, so treat those specifics as unconfirmed until Microsoft or JetBrains publishes them officially.
Why JetBrains version support always matters here
Plugins don’t run in a vacuum — they have to stay compatible with the host application, and IDEs change frequently. JetBrains ships major releases on a regular cadence and maintains an “End of Life” policy, meaning older versions eventually stop receiving updates and fall out of support. Copilot’s JetBrains plugin follows the same logic: it targets a rolling window of recent IDE versions and phases out the ones that age out.
That’s a deliberate trade-off. Maintaining compatibility across every historical IDE release would stretch a plugin team’s testing resources thin, so vendors typically support the current version plus a few predecessors. When you see an older version lose support, it’s usually the natural result of that rolling-window model rather than a sudden decision.
What this means for you
The practical impact is straightforward: if you’re still running an outdated JetBrains IDE, your Copilot suggestions could stop appearing without much warning. You wouldn’t lose your code or your settings — you’d just lose the AI pairing until you upgrade the IDE itself.
For most users, the fix is simple. JetBrains makes it easy to check for updates from within the IDE, and newer versions are generally backward compatible with existing projects and plugins. The main thing to watch is that you land on a version GitHub still lists as supported for Copilot.
How to keep GitHub Copilot working
First, verify your current version. In a JetBrains IDE, open the Help menu and look for the “About” option, which displays the exact build and version number. If it’s more than a year or two old, there’s a decent chance it’s already past the support window.
Next, update the IDE. JetBrains prompts for updates automatically, but you can also trigger a manual check. Once you’re on a current release, relaunch and confirm the Copilot plugin is active and signing in properly.
If you manage a team or a fleet of developer machines, coordinate the upgrade so nobody gets caught mid-project when an older build loses support. A quick heads-up and a shared target version will save a lot of scattered “why did my assistant just stop?” tickets.
What this means for you
The bottom line is that this isn’t a reason to panic, but it is a reason to look at your toolchain. AI coding assistants are only useful while they’re connected, and keeping your IDE current is the cheapest insurance against a surprise disconnect. Check your version, update if it’s stale, and you’ll stay on the supported side of the line.
Source: Neowin
Over to you: Which JetBrains IDE are you running, and have you updated to a Copilot-supported version yet?
