JetBrains shipped its 2026.2 release wave on July 22, and the most consequential change for most developers is not the Java 27 support or the Spring Security updates. It is that GitHub Copilot is now a native agent in every JetBrains IDE — no Marketplace hunting, no ACP Registry configuration, no plugin version mismatches. You still need to pay for Copilot separately, but the friction of getting it into IntelliJ is gone.
What “Native” Actually Means
Before 2026.2, getting GitHub Copilot into IntelliJ required installing the standalone Copilot plugin from the JetBrains Marketplace, then configuring it through the Agent Client Protocol Registry — an extra layer most developers found opaque. If JetBrains AI Assistant and Copilot both wanted to handle a prompt, they would occasionally conflict.
In 2026.2, the plugin step is gone. Copilot appears directly in the AI Chat agent picker alongside JetBrains AI Assistant and the Claude preview. Setup:
- Update to IntelliJ IDEA 2026.2 via Toolbox App, snap, or the in-IDE updater
- Open the AI Chat panel
- Click the agent picker dropdown
- Select GitHub Copilot
- Complete OAuth with your GitHub account
If you had the old Copilot plugin installed, disable or uninstall it to avoid conflicts. The native integration replaces it. An active GitHub Copilot subscription is still required — the change is about access friction, not pricing.
The Subscription Math Is Awkward
Here is where JetBrains has a problem they have not solved. The native Copilot integration is convenient, but it does not reduce what you pay. A developer on an All Products Pack pays roughly $28.90/month for the IDE. Add GitHub Copilot Pro and you are at $38.90/month. Add Copilot Pro+ and you are at $67.90/month.
| Setup | Monthly Cost |
|---|---|
| VS Code + Copilot Pro | ~$10/month |
| IntelliJ + JetBrains AI Pro | ~$38.90/month |
| IntelliJ + Copilot Pro | ~$38.90/month |
| IntelliJ + Copilot Pro+ | ~$67.90/month |
JetBrains’ answer to the obvious comparison with VS Code is that IntelliJ’s Java and Kotlin intelligence operates in a different category: framework-aware inspections for Spring and Quarkus, deep refactoring, built-in database tooling, and static analysis that goes well beyond what VS Code offers. That case holds for Java-heavy shops. But it requires developers to consciously decide the IDE depth justifies the premium — a harder sell as VS Code closes the tooling gap. JetBrains still has not announced a bundled AI+Copilot tier.
What Else Shipped in 2026.2
The Copilot integration is the headline, but 2026.2 delivers across the board. A few features that will actually affect your daily work:
AI-Assisted Logpoints
During a debug session, AI now suggests what expressions to log based on context — no source modification, no recompilation, no leftover print statements to clean up afterward. It is one of those small-sounding features that changes how you debug in practice.
Java 27 and Kotlin 2.4 Day-One Support
JetBrains consistently ships language support on release day. Java 27 and Kotlin 2.4 are fully supported in 2026.2, including new language features in completion, refactoring, and code analysis. No waiting two weeks for inspections to catch up.
Spring Security Insights
The editor now shows security indicators inline next to controller endpoints. You can see at a glance which roles protect a method, whether an endpoint is publicly exposed, and where the Spring Security configuration is rooted — without leaving the code to chase annotation chains.
Gradle 10 Migration Prep
Projects on Gradle 9.7+ can now sync even when build scripts have errors. The IDE surfaces API deprecations ahead of Gradle 10 with updated code assistance. If you manage a large Java project, this matters now — not when Gradle 10 forces your hand.
The Full 2026.2 Wave
The native Copilot integration applies across the entire JetBrains lineup. Rider 2026.2 gets Copilot plus agent skills covering .NET testing workflows and refactoring. WebStorm 2026.2 ships with TypeScript 7 support built in alongside the Copilot integration. GoLand 2026.2 adds profiling improvements and goroutine leak detection. PyCharm 2026.2 followed on July 20. All IDEs, same Copilot setup path.
What Is Still Missing
Two announced features are not yet here. Claude as an agent provider launched in preview on June 22 but remains preview-only in 2026.2. Next Edit Suggestions — Copilot’s ability to anticipate what you will edit next across files — was announced but did not make this release. Both are on the roadmap, but there are no committed dates.
Worth the Upgrade?
If you are already on a JetBrains subscription: yes. The 2026.2 update is free, and the native Copilot integration alone removes a real daily friction point. The 1,300+ bug fixes and AI logpoints make this a strong release even without the AI headline.
If you are evaluating IntelliJ specifically because of the Copilot integration: no, this is not the reason to switch from VS Code. The integration removes a configuration headache for existing users — it does not make IntelliJ more compelling versus a Copilot-enabled VS Code setup for developers who do not need deep Java tooling. The subscription stacking remains, and JetBrains has not addressed it.
