APOLLO TERMINAL v1.0 –
> █type '/help' for commands
Skip to main content
0200 / 00:00:00 / 1970.01.01
×
HOME ABOUT NEWS PROJECTS REFERENCES LINKS

JETBRAINS PUT INTELLIJ'S JAVA BRAIN IN VS CODE

A solid navy sphere lifted out of one open shell and hovering above a second, different shell

JetBrains sells IDEs. In August 2026 it also started giving away, in preview, the exact Java and Kotlin intelligence that its IDEs have always used to justify the licence. I build JetBrains plugins for a living, so I read that announcement more carefully than most people will.

The VS Code extension

“IntelliJ IDEA Goes LSP” is a preview extension that brings IntelliJ’s Java and Kotlin code intelligence into VS Code and its forks, Cursor and Antigravity included, over the Language Server Protocol. It is free while it is a preview. JetBrains says an Ultimate licence will be required once it is not.

Separating the two is the actual news. Java and Kotlin completion, navigation, and inspection quality inside IntelliJ have never been portable. They lived inside the IDE process, tied to IntelliJ’s own indexing and PSI machinery, and you got them by opening IntelliJ. Now the engine talks LSP, which means in principle it can sit behind any editor willing to speak the same protocol on the other end. A preview extension for three specific VS Code forks is not “any editor,” and free-during-preview is not “free.”

The licensing model is intact and stated up front: the eventual Ultimate requirement means the business still runs on the same thing it always ran on. The extension also sits next to a second, quieter move on the same protocol, going the other direction.

The IntelliJ side: LSP client API

IntelliJ’s LSP client API, the part that lets an IntelliJ plugin consume an external language server instead of writing its own PSI-based language plugin from scratch, became generally available to all plugin developers in September 2025. JetBrains open sourced that client API during the IntelliJ IDEA 2026.2 development cycle. So in under a year, JetBrains formalised both sides of the LSP conversation: IntelliJ as a client that reaches out to a language server, and now IntelliJ’s own engine as a server that something else reaches into.

Flexible Julia, my own JetBrains plugin, is an LSP client. It can drive three completely different Julia language server backends: LanguageServer.jl, the newer JETLS, and Fatou, which is a standalone Rust binary that never runs Julia at all. Three different runtimes, one plugin, because LSP is the thing they all agree on.

I built that client by hand. Looking at my own code, there is no sign of an official client API in it, just raw process I/O, Content-Length headers parsed manually, and a comment I left myself after finding out the hard way that reading those headers with a character-based reader instead of a byte-based one silently corrupts the stream. That is the exact plumbing the now-open-sourced client API exists to hand you for free. I do not know yet whether moving Flexible Julia onto the official path is worth the migration cost.

Why LSP

JetBrains has decided LSP is the seam to expose Java and Kotlin intelligence through, on both sides of the wire, while the rest of the editor market is full of forks competing on that kind of interoperability.

The VS Code side is here: blog.jetbrains.com/idea/2026/08/intellij-idea-goes-lsp. A plugin built on the client side of that protocol is Flexible Julia.

Background
EducationEBS Business School, SFSU, HSG
Experience20 Years Enterprise Systems
BuiltScipio ERP - ERP & Ecommerce System
Author"Start/Up - Set the net on fire"
JetBrains5x Plugins Published
Tech Stack
LanguagesJava, Python, JS, TS, Rust, Go, Swift, PHP
FrontendReact, Vue, Angular, HTML/CSS
DatabasesPostgreSQL, MySQL, MongoDB
CachingRedis, Memcached
Key Clients
EnterpriseL'Oréal, Amadeus, Konica Minolta, Orange
Digital1&1 Internet, Sedo.com, Creditsafe
PublicDRK, Kanton Basel, Aktion Mensch, Börsenverein