Kotlin Notebook Sunset

Marco Behler

Starting from IntelliJ IDEA 2026.2, JetBrains will sunset Kotlin Notebook as a product and will no longer maintain it.

The plugin will remain available on an open-source model so the community can continue its development. 

Below, we explain why we’re making this change, how it affects current Kotlin Notebook users, what comes next, and how Kotlin DataFrame will continue to exist beyond Kotlin Notebook.

Why we’re making this change

Demand for built-in interactive tooling has shifted since we launched the plugin, and Kotlin Notebook didn’t reach the level of adoption we expected. AI tools have changed how developers explore code, prototype, and iterate, and many of the workflows that originally drove notebook adoption have evolved along with that shift.

After reviewing usage trends, we’ve decided to move Kotlin Notebook out of our internal roadmap and into the open. Going forward, our team will devote its time to projects with a broader impact on Kotlin developers.

Timeline and what to expect

Here’s what to expect during the transition:

v2026.1 and earlier:

• Kotlin Notebook remains bundled with IntelliJ IDEA.

v2026.2:

• Kotlin Notebook will be unbundled from IntelliJ IDEA.
• JetBrains will no longer develop new features for Kotlin Notebook.
• The Kotlin Notebook plugin will still be available for installation from the marketplace. It is compatible with v2026.2. However, we do not maintain it anymore. Future development will happen in the open-source repository only. 
• The plugin source will be published on GitHub under the Apache License 2.0. Users can build the plugin from GitHub and install it manually. The README walks you through the steps.

V2026.3 and further:

• JetBrains won’t publish a compatible plugin for v2026.3 and beyond.

During the transition to community ownership:

• We plan to continue maintaining the Kotlin Jupyter kernel on a best-effort basis, as capacity allows.
• If you’re interested in maintaining or contributing to Kotlin Notebook, please share your interest in the Kotlin Slack #notebooks channel. 
• Our Support team will be available during the transition for compatibility questions.

Kotlin DataFrame beyond notebooks

If you’re using Kotlin DataFrame, recent releases have made it much easier to bring notebook-style, type-safe data transformations into regular Kotlin projects. With the Kotlin DataFrame compiler plugin, schema-aware APIs and generated column accessors are now available directly in Gradle and Maven projects and can be used in ordinary .kt files.

To get started, see the setup guides for Gradle and Maven:

• Gradle: https://kotlin.github.io/dataframe/setupgradle.html
• Maven: https://kotlin.github.io/dataframe/setupmaven.html

We also recently released Kotlin DataFrame 1.0.0-Beta5, with numerous improvements across the library. See the release notes here.

If you have questions about migrating existing workflows or adopting Kotlin DataFrame in your projects, feel free to reach out in the Kotlin Slack #datascience channel.

Thank you note

We’re grateful to everyone who used Kotlin Notebook, filed issues, and shared feedback over the years. Thank you!

The JetBrains team