← News

Editora 0.23.0: four JVM languages, a terminal, encrypted files

October 19, 2026 · 0.23.0

Editora 0.23.0 is out. Four more JVM languages get the whole treatment, from highlighting to the debugger, there is a terminal inside the editor, Node.js and Python scripts run, test and debug like Java does, and a project can now be deployed to another machine and run there. Download it from the 0.23.0 release page.

Kotlin, Scala, Clojure and Groovy

Each language gets a language server installed in one click, Run File and the gutter ▶, a run configuration type, and Debug. Kotlin, Groovy, Clojure and Scala scripts debug through the JVM debugger built into Editora, so there is no debug adapter to install; a file of a Scala build uses Metals’ own.

Scala and Clojure files are highlighted, fold, indent (Lisp-style for Clojure) and have an outline without a language server too. The Run window shows which Kotlin, Scala or Groovy version ran, beside the Java one. More about the language servers and running files.

A terminal inside Editora

The new Terminal tool window opens shells in tabs, in the project’s folder (Alt+F12 in the IntelliJ keymap, Ctrl+` in VS Code, CUA and Sublime). A focused terminal owns the keyboard, so Ctrl+C, Ctrl+W and Escape reach the shell and vim, while the keys a shell never uses still reach Editora.

More about the terminal.

Node.js and TypeScript

More about Node.js scripts.

Python

More about Python.

Debugging

More about debugging.

Deployments

Develop locally, run on another machine. A run configuration’s Run on setting names a deployment, an SSH host and a folder there. Before the run, Editora copies only what changed to that folder in one compressed stream over its own connection (no rsync or ssh needed here), then builds and runs the program there with the host’s tools. Files Editora put there and the project no longer has are removed, and nothing else on the host ever is. More about deployments.

Encrypted files

GnuPG encryption is built in (the gpg-tools plugin is retired). An encrypted file opens as the text inside it, in that text’s language, with a lock on its tab and a status-bar item that says who can read it. Encrypt File… picks the recipients or a passphrase, and saving encrypts it again for the same people. While it is open its text gets no crash-recovery copy or Local History, language servers do not read it, and agents, MCP clients and AI actions are refused. A tab that cannot be opened stays locked and says why. More about encrypted files.

SSH logins

More about authentication.

Settings

More about the Settings window.

Plugins

Plugins ask before anything changes: consent belongs to a plugin’s folder and to what you were shown, an install or update is staged and only put in place once you agree, and MCP clients cannot turn plugins on or install them. --disable-plugins starts Editora without them, and Doctor → Plugins lists any that failed or started slowly. More about plugins.

Also

The full list is in the changelog.