Released: Jul 16, 2026

Aggiornamenti in 2026.2

Funzionalità

AI

• Agent skills - Skills give your agents reusable domain knowledge and instructions, making them more accurate and efficient when working with a given tech stack or topic. To help you get started quickly, IntelliJ IDEA now allows you to discover, install, and manage custom agent skills directly in the IDE. Some of the most useful skills are already bundled in the IDE and marked accordingly in the skills manager.
• Debugger - The ij-debugger skill allows the agent to use the debug run configuration, logpoints, and other suitable tools to debug issues. It uses runtime information to identify the root causes of problems, eliminating guesswork. As an open platform for AI, IntelliJ IDEA allows you to install skills not only from the built-in library, but also from local projects and directories, public GitHub repositories, or projects you have configured in other editors. Codex and Claude Code projects are currently supported.
• Support for third-party providers in AI-based code completion - AI-based code completion is an in-editor code suggestion experience that combines inline completion and next edit suggestions that go beyond the cursor. Available to all JetBrains AI users out of the box, it's powered by JetBrains-trained models and does not consume AI credits. With the latest update, you can now connect your own OpenAI-compatible model providers for AI completion.
• GitHub Copilot, natively integrated - As the result of a direct partnership between JetBrains and Microsoft, GitHub Copilot is now a natively integrated agent in IntelliJ IDEA. Expanding the previous ACP Registry setup, Copilot is available out of the box and provides a more cohesive experience.
• You can access Copilot directly from the agent picker in the AI chat. Authentication is handled through OAuth with your GitHub account, and an active GitHub Copilot subscription is required.

Productivity enhancements

• Logpoints and extended debugging experience - Every developer has used println for debugging at least once. But sometimes it is not the best approach. It can pollute the code, fail to get enough context from the print, and make identifying where it came from difficult. On top of all that, it doesn't work inside libraries. Logpoints offer a clean alternative and deliver dramatic UX and performance improvements. Built on top of non-suspending breakpoints, logpoints allow you to inspect internal application states and execution context, as well as send custom messages at runtime without modifying the source code. This approach also makes it possible to diagnose code behavior inside compiled third-party libraries. Additionally, when you run a debugger, you will always be able to navigate from the output to the place in the code that produced it - no matter whether it comes from a logpoint, a regular logger, or a simple println.
• Dependency completion - Adding a proper dependency usually requires looking up the exact library name and available versions on an external resource - but not anymore. IntelliJ IDEA 2026.2 simplifies this process with cloud-based dependency search. Just start typing the name of the library in the relevant section of a Maven or Gradle build script, and you'll have all the matching artifacts, their versions, and their recommended scopes right at your fingertips.
• Early Gradle 10 support and migration assistance - Allowing you to take advantage of the latest versions of relevant JVM technologies is one of the core commitments. JetBrains are working to ensure that IntelliJ IDEA supports Gradle 10 ahead of its release, expected in the second half of 2026. To help with early adoption and simplify migration to the new version, JetBrains has partnered with Gradle Technologies. As a result of this collaboration, IntelliJ IDEA 2026.2 can properly sync projects with Gradle 9.7 or later, even when build scripts contain errors. It also provides proper code assistance based on the new Gradle version API to help you fix those issues.

JVM and language support

• Java 27 - IntelliJ IDEA continues to provide support for the latest Java releases from day one, as well as early support for upcoming Java releases, for example, by allowing you to install early access builds directly from the IDE.
• Kotlin support: 2.4 Stable features - IntelliJ IDEA 2026.2 brings support for the latest language features in Kotlin 2.4.0, most notably explicit backing fields and explicit context parameters.
• Scala - The new release of the Scala plugin brings support for Scala 3's clause interleaving, introduces command completion for Scala code, and improves support for BSP⁠-⁠based build tools in WSL and Docker.

Spring

• Updated DB migration workflows - Flyway and Liquibase migrations are often seen as just SQL scripts, but they are actually a history of DB evolution. The main pain point is that developers often lack the context to understand this evolution. IntelliJ IDEA 2026.2 addresses this by bringing the migration context to SQL symbol resolution, displaying visual indicators that show whether schema changes have been successfully applied or failed, and allowing you to execute Flyway configurations directly from the IDE. No false-positive error highlighting, and easier to troubleshoot.
• Spring Security insights - With the Spring Debugger plugin in IntelliJ IDEA, it is now easier to verify endpoint behavior without changing your Spring Security configuration or restarting the application. You can see Spring Security inlays near Spring MVC endpoints. They show how a route is protected, allow you to inspect where the effective rule comes from, and let you navigate to the corresponding security configuration. During a debug session, you can also test an endpoint with custom user details and roles or temporarily unlock it in the running debug context.
• Streamlined Git conflict resolution flow - In large projects, merges often result in dozens of file conflicts, many of which are simple import mismatches or formatting differences. IntelliJ IDEA 2026.2 improves the conflict resolution flow, allowing you to invoke the Resolve All Simple Conflicts action, which automatically resolves standard conflicts across the entire changeset instead of opening each file one by one. You can also see a complete overview of resolved and unresolved files, reopen files at any time, and reapply conflict chunks in any order.

Docker Compose improvements

• IntelliJ IDEA 2026.2 provides deeper environmental control in Docker Compose configurations, reducing the friction of managing external dependencies and runtime container states during local development. Now, from a Docker Compose configuration file, you can see the execution status of individual containers in real time, jump to the corresponding runtime output, quickly create database connections, and use completion templates for widely used services like Kafka and PostgreSQL.

Terraform test framework support

• This release extends IntelliJ IDEA's infrastructure-as-code capabilities by introducing native support for the Terraform test framework. This integration rounds out the IDE's ecosystem support, allowing you to validate module behavior and enforce configuration policies early in the development life cycle.
• These additions help ensure your deployment configurations remain highly maintainable, predictable, and clean.

TypeScript 7 support for faster workflows with large codebases

• Large TypeScript codebases don't have to feel slow. TypeScript 7 rewrites the compiler and language server in Go, and the difference is noticeable immediately. In testing, project load time on the Kibana codebase dropped from ~12 seconds to ~3 seconds, which means editor responsiveness has improved roughly fourfold.
• IntelliJ IDEA 2026.2 supports TypeScript 7 as the default for projects already using it, with an opt-in upgrade path for those still on earlier versions. You get the full speed benefit immediately - no full project migration required on day one.
• For teams on large TypeScript monorepos, this is a day-one upgrade.