JetBrains shipped version 2026.3 of its Scala plugin for IntelliJ IDEA and Android Studio on November 6, 2026. The update adds Scala 3.10 support, sharpens the plugin's own analysis of Scala 3 code, and rewrites the editor support for Twirl, the template language of the Play Framework.
The release follows IntelliJ IDEA 2026.3 by a day. It also removes several older features, including Ammonite script support, Fastpass imports and the experimental IntelliJ Scala Bundle, so teams with older setups should read the change list before they upgrade.
Scala 3 Analysis Gets More Accurate
The headline change for most users is better handling of Scala 3 code inside the editor. JetBrains says the goal was fewer false error marks and more precise inferred types, which are two of the most common complaints from Scala developers who use the IDE.
- Scala 3.10: the plugin now recognizes the newest Scala 3 release.
- Extension methods: calls now pick the right overload even when receivers are generic or differ, or when type parameters and implicit conversions are involved, and right-associative extension operators are fixed.
- Given instances: contextual arguments are chosen with help from explicit type arguments and method arguments, so generic code shows fewer bogus ambiguity and missing-implicit warnings.
- Type inference: transparent traits, higher-kinded type parameters with bounds, and anonymous classes are inferred closer to what the compiler itself produces.
Completion, navigation and Quick Documentation also separate extension methods by receiver type more clearly, and the completion list shows fewer repeated entries.
Twirl Templates for Play Framework Rewritten
Twirl support was rebuilt from its architecture up. After the rewrite, JetBrains reworked how template files are parsed, completed, formatted and searched.
In practice, Find Usages can now point to the Scala code that renders a given template, and renaming a template updates every reference to it across the project. The plugin also reports fewer bogus errors in HTML, CSS, JavaScript and JSON that sit inside templates.
Build Tools, Debugger and Highlighting
For sbt projects, separate main and test modules are now the only supported layout. This layout first arrived in plugin 2024.3, and the switch to turn it off is gone. Importing sbt 2.x projects handles compiler plugin paths better, and build scripts that use .value or slash expressions no longer show false unresolved errors.
Slow imports with Scala 3.8 and a BSP import regression are fixed. Editing the body of a Scala 3 macro now triggers a rebuild of the code that uses it, so stale macro output does not linger. Completion of library coordinates is back for sbt files and for Scala CLI dependency directives.
Scala CLI scripts get better shebang handling, and a new inspection warns when a script with a shebang line lacks execute permission, with a quick-fix to set it.
In the debugger, breakpoints now work on one-line conditional return statements and inside Future callbacks and for comprehensions in Scala 3 top-level methods. Freezes during watch evaluation and expression completion are fixed too.
Compiler-based highlighting does less repeated work. It reuses valid results, batches pending checks for several files into one compile run, and explains which module's errors are blocking highlighting, with a link to them.
Removals and Changes to Check Before Upgrading
- Ammonite: dedicated script support, run configurations and import helpers are removed; scripts can still run outside the IDE.
- Fastpass: it can no longer be used to import projects.
- sbt layout: projects always use separate main and test modules.
- IntelliJ Scala Bundle: the experimental standalone download is retired; install IntelliJ IDEA and the plugin separately.
The plugin itself is now written in Scala 3. This does not affect user projects, but authors of IntelliJ plugins that compile against Scala plugin APIs must rebuild against the 2026.3 build and check for changed signatures and bundled dependencies.
What It Means for Developers
For teams on Scala 3, the analysis fixes matter most. Red underlines on code that compiles fine waste time and push people toward compiler-only highlighting, which is slower. Fewer false errors around givens and extension methods make the default mode more trustworthy for library-heavy code.
Play Framework teams should see the biggest day-to-day gain. Reliable rename and Find Usages for templates make it safer to restructure views, a task many teams avoid because the old support missed references.
The removals deserve a quick audit. If your team still uses Ammonite scripts inside the IDE, or relies on Fastpass for very large builds, plan another path before you upgrade. Moving those scripts to Scala CLI is a natural option, since this release adds tooling for it.
If you work with Java in the same IDE, our IntelliJ IDEA 2026.3 release story covers the platform changes that ship alongside this plugin.
How to Upgrade
Update IntelliJ IDEA to 2026.3, then install or update the Scala plugin from the Plugins section of the settings. Android Studio users get the plugin through the same marketplace. After the update, re-import sbt projects so the module layout and compiler options refresh, and report problems to JetBrains through YouTrack.
Conclusion
Scala plugin 2026.3 is a cleanup and accuracy release. It adds Scala 3.10, cuts false errors in Scala 3 code, rebuilds Twirl support for Play, and trims older integrations such as Ammonite and Fastpass.
Most Scala developers should upgrade soon, after checking that none of the removed features are part of their daily workflow.
Sources
See my articles more often when you search Google.
