[0.23.0] - 2026-10-19
Security
-
Encrypted files are a core feature, and their text stays encrypted everywhere Editora writes. Opening a
.gpg,.pgpor.ascencrypted file decrypts it with GnuPG (thegpgyou have installed, on this machine), and saving encrypts it again for the same people, in the same format. A save that cannot be encrypted (a recipient’s public key missing, GnuPG failing) writes nothing and says why in a banner. While an encrypted file is open, its text gets no crash-recovery copy and no Local History, bookmarks and breakpoints keep only line numbers, no personal notes can be added, language servers do not read it (a setting turns them on), agents, MCP clients and AI actions are refused, and diagrams are not rendered through temporary files. Save As to a plain name, export, print and external tools ask first. Settings schema 136. -
Plugins: consent belongs to a plugin’s folder and to what you were shown. A plugin’s id must be its folder’s name (a folder that copies another plugin’s id is listed with an error and never loads), and plugins.json stores a fingerprint of the disclosure with each consent: a plugin whose code, commands or chords changed since does not load until you enable it again. Entries of plugins whose folder is gone are dropped at start. plugins.json schema 2 carries existing consents over.
-
Plugins: nothing is replaced before you agree. An install is unpacked beside the plugins and put in place only on Enable; a registry archive must be the plugin and version its entry names; installing a different plugin under an installed plugin’s id asks “Replace A with B?” first. Remove deletes the row you clicked.
-
The plugin consent dialog cannot be forged. Manifest text is escaped (line breaks, control and bidi characters are shown, not obeyed) and capped, the capability list scrolls in a fixed box, and it lists the main class and every jar, each command’s exact argv and folder, and what each chord replaces. A plugin whose plugin.json cannot be read can no longer be ticked.
-
MCP clients cannot switch plugins on, change the signed-registry requirement, install or remove plugins, or trust a folder. The registry URL setter refuses anything but https for every caller.
-
AI API keys are kept in the system keychain (macOS Keychain, Windows Credential Manager, the Secret Service on Linux). Keys in settings.json move there on first start, and Settings → AI Actions says where each key is. Where no keychain answers, keys stay in settings.json and the page says so. Keys in the keychain are never exported.
-
Export Configuration never includes a password or token stored in the Settings Sync repository URL, and the Sync page offers to remove one stored there before the URL check existed.
-
Switching the AI provider no longer sends one provider’s API key to another provider’s server. Anthropic and the OpenAI-compatible provider shared one endpoint and model, so after a switch to Anthropic the Anthropic key went to the OpenAI-compatible server set up before (and the other way round), within seconds and again on every Settings open. The OpenAI-compatible provider now has its own endpoint, model and inline-completion model. Settings schema 127 moves an existing OpenAI-compatible endpoint and models to the new fields.
-
Export Configuration leaves the AI API keys out by default. The export dialog has an “Include AI API keys” checkbox, and the Advanced page and the status line say when they were left out.
-
The Settings Sync repository field refuses a URL with a password or token in it (
https://user:TOKEN@…) and suggests a credential helper (gh auth setup-git) or SSH, so the token is not stored in settings.json, the export or the clone.
Added
-
Kotlin: JetBrains’ Kotlin LSP, Run and Debug. Kotlin’s language server is now JetBrains’ Kotlin LSP: one click installs a pinned release (about 370 MB with its own Java runtime, which Editora says before it starts), and it imports the Gradle build for completion, navigation and diagnostics. A configured command is kept, so fwcd’s kotlin-language-server still works. Run File, the gutter ▶ and a new Kotlin run configuration run a
.ktsscript withkotlinc -script, and compile a.ktfile with a top-levelmaininto a cached jar that runs withjava -jaron the Settings JDK (compiled again only when the file changes); the Run window shows the Kotlin and Java versions. Debug stops at breakpoints in programs, scripts and lambdas through Editora’s own debugger, names frames as Kotlin does (Hello.main { lambda }), and steps over the standard library and coroutines machinery. Debug via Build Tool and Attach to JVM work from a Kotlin file too. -
Groovy: language server, Run and Debug. Groovy files get completion, diagnostics, outline, rename and formatting from the gvy language server, installed in one click (a pinned jar, run on the JDK chosen in Settings). Run File, the gutter ▶ and a new Groovy script run configuration run a script with
groovyon that JDK, and the Run window shows the Groovy and Java versions. Debug stops at breakpoints in scripts, classes and closures, steps over Groovy’s own runtime, shows locals and fields, and stops on uncaught exceptions — through a new debugger built into Editora, so there is nothing else to install. Settings schema 138. -
Run File runs Node.js scripts. A
.js,.mjs,.cjs,.ts,.mtsor.ctsfile, or a script with anode(ordeno,bun,tsx) shebang, gets a gutter ▶ and runs in the Run console under the Node.js Editora resolves (the Node.js setting, the project’s.nvmrc/.node-version, elsenodeon PATH), from its package folder, with--enable-source-mapsand colours on. TypeScript runs on plain Node 22.18+; an older Node says so. The ▶ of a test file (*.test.*,*.spec.*,test/,__tests__/) runsnode --testinto Test Results, with Rerun Failed and Rerun This Test. Run configurations gain a Node.js script type (script, Node.js arguments, interpreter, arguments, environment). -
One Node.js for everything. Settings → Debugging → JavaScript has a Node.js field used by Run, run configurations, Debug, npm scripts, the TypeScript language server and (when its own field is blank) HTTP response handlers. Left blank, Editora uses the version a project’s
.nvmrcor.node-versionnames when nvm has it, elsenodeon PATH. Doctor has one Node.js row saying which Node runs and why. -
Debugging JavaScript and TypeScript.
.ts,.mtsand.ctsfiles can be debugged on Node 22.18+, and a breakpoint in a compiled project’s.tssource stops there through source maps. Debug ▸ Attach on a JS/TS file connects to a Node started with--inspect. Debug Test at Caret runs the node:test test at the caret. Node.js and npm run configurations can be debugged, started the way Run starts them. -
TypeScript server settings: Download type definitions automatically (off), and inlay hints and code lenses now work for JavaScript and TypeScript.
-
A Node.js Script template (New ▸ Scripts ▸ Node.js), and an npm icon on
package.json,package-lock.jsonand.npmrc. -
Test Results reads node:test’s default output, so
"test": "node --test"fills the tree without a TAP reporter flag, and node:test results can be rerun one by one or failed-only. -
Encrypted files (Tools ▸ Encryption; ADR 0017). An encrypted file opens as the text inside it, in that text’s language (
notes.md.gpgis Markdown), with a lock on its tab and an “Encrypted · 2” item in the status bar that opens the details: who can read it (you, verified or not), its format, its signature.- Locked tabs instead of hex or errors: a cancelled prompt, a file none of your keys opens, or GnuPG not installed shows what happened and the next step. Restored tabs stay locked until you decrypt them, so startup never asks for a run of passphrases.
- Encrypt File… (also on the Project tree and tab menus, and Save As to a
.gpg/.ascname) opens a recipient picker: searchable, several people at once or a passphrase instead, your own key included by default, unverified keys warned about with their fingerprint, expired and sign-only keys shown with the reason. It can write the folder’s.gpg-id(thepassformat) so new files there get the same people. The plain original stays until you move it to the trash from the banner. - Change Recipients… (applied on the next save), Remove Encryption…, Lock File, Decrypt to
File…, Encrypt Selection… and Decrypt Block at Caret (an armored message pasted into a note opens
in a read-only card), Import Public Key… (and an opened
.asckey offers it), Clear-Sign, Sign File (Detached) and Verify Signature. - Passphrases go to gpg-agent’s own prompt; when it cannot show one (a terminal pinentry), Editora asks and hands the passphrase straight to GnuPG. A passphrase-only file is asked once and saves without asking again.
- Settings ▸ Encryption (gpg path, always include my key, who asks for passphrases, language servers) and two
Doctor rows (GnuPG, passphrase prompt). Samples in
samples/encrypted/(passphraseeditora).
-
Clojure: language server, build tools, Run and Debug. Clojure, ClojureScript and EDN files get completion, diagnostics (clj-kondo’s), navigation, rename and formatting from clojure-lsp, installed in one click (a pinned native binary, checked by its SHA-256) or found on PATH. A
deps.edn,project.cljorbb.ednproject gets a Clojure CLI, Leiningen or Babashka toolbar button: the CLI’s runnable aliases (-M:test,-X:build,-T:build), Leiningen’s common tasks, abb.edn’s tasks. Run File, the gutter ▶ (on(defn -main, else the top of a script) and a new Clojure script run configuration run a namespace withclojure -M -min its project, throughlein runin a Leiningen project, a script withclojure -M, and a Babashka script withbb; an uncaught exception’s whole trace is printed (not left in a temporary file), and its frames are links. Debug stops at breakpoints in a namespace’s functions or a script’s top-level forms, under the Clojure CLI or Leiningen, with locals kept visible and frames named as Clojure names them (my-app.core/greet); Babashka, a native program, cannot be debugged and says so. Settings schema 139. -
Scala: Metals, sbt, Mill, Scala CLI, Run and Debug. Scala files get completion, diagnostics, navigation, rename and formatting from Metals 1.6.9, installed in one click (a pinned coursier resolves it into Editora’s folder; it runs on the JDK chosen in Settings). Language servers’ questions are now asked — Metals’ “Import build?” among them — and Metals’ input boxes, pick lists and status items work. sbt (
build.sbt), Mill (build.mill,build.sc) and Scala CLI (project.scala) projects get a toolbar button, actions popup and console like Gradle’s, with each sbt subproject’s or Mill module’s tasks loaded on demand. Run File and the gutter ▶ (on an@main def, anobject … extends App, adef main, or a.scscript) run a file of an sbt or Mill build through it (sbt "runMain …",./mill <module>.runMain …) and any other file with Scala CLI, with the Scala CLI and Scala versions in the Run window; a new Scala run configuration runs files with Scala CLI. Debug uses Metals’ debug adapter for a file of a build, and Editora’s own debugger over Scala CLI for a script, stepping over the standard library. Settings schema 140. -
Scala and Clojure editing.
.scala,.sc,.sbt,.milland.clj,.cljs,.cljc,.cljx,.edn,.bbfiles are highlighted (grammars from tm-grammars 1.32.22), as are#!scripts run byscala,scala-cli,kotlin,clojure,cljorbband files with ascala/clojuremodeline. Comment toggling (;;in Clojure), folding (Scala 3’s indentation blocks through theirendmarker; every multi-line Clojure form), Lisp indentation (to the first argument, two spaces for a body form), Go to Symbol without a language server, a Structure outline, snippets, brand file icons, and New ▸ Scala, Scala CLI script, Clojure and Babashka script. Groovy gets its own icon and a server-free symbol index too, and stack-trace lines from Kotlin, Groovy, Scala and Clojure code are links (including Clojure’sat my-app.core/f (core.clj:4)). -
--disable-pluginsstarts Editora with no plugin loaded for the session: the way out of a plugin that hangs or breaks startup. Settings and Doctor say when it is on. -
Doctor → Plugins lists what runs and every plugin that failed to load or start, started slowly, or changed since it was enabled.
-
Plugin chords per keymap: a manifest’s
keymapsgives chords for one keymap (emacs,cua, …) in place ofkeymap. -
Plugins: Restart now on a Settings row whose change waits for a restart, and status and errors shown on the Plugins page itself.
-
Settings shows what you changed. A row whose value differs from the default carries a marker, the sidebar counts them per page, each row has Reset to default, and the Modified toggle (or
@modifiedin the search) lists only the changed settings. -
Project settings. In a project window, Settings has a User | Project switch. A project’s
.editora/settings.jsoncan set indentation, tab size, rulers, wrap, trimming trailing whitespace, the final newline, the spelling dictionary, build commands, debugger paths and language servers. The values apply in that project’s windows once the folder is trusted;.editorconfigstill wins where it sets something. Rows say when a project sets or overrides them. -
Import Configuration… (Settings → Advanced, or Configuration: Import from Zip) reads a zip made by Export Configuration. It shows each part and what it would replace, lets you untick parts, backs up the current configuration to
backups/first, applies what it can at once and offers a restart for the rest. It refuses a zip that is not an export, unsafe entry names and oversized entries. -
Restart Now. Settings that apply at startup (language, merged title bar, plugins) show “Restart Editora to apply N changes.” with Restart Now (also Application: Restart), which quits the usual way and starts Editora again.
-
Settings → Sync shows a status pill: green Connected (with when it last synced), amber Not connected (not set up, turned off, or offline and retrying) and red Sync failing (it needs you), with the reason under it.
-
Each Settings page links to its documentation with a ? beside the title.
-
File Watching row in the Doctor: says when the system has no file watcher to give and Editora checks folders by polling instead.
-
Deployments: develop locally, run on another machine. A run configuration’s new Run on setting names a deployment — an SSH host and a folder there. Before the run, Editora copies what changed in the project to that folder over the connection it already uses for remote folders (one compressed stream; no rsync or ssh needed on this machine), then runs the before-launch step and the program there, with the host’s tools.
- Only files whose contents changed are sent; a branch switch that only touched times sends nothing.
- Files Editora put on the host and the project no longer has are removed; nothing else on the host is ever
removed. A file changed on the host since it was sent is asked about, a first deploy into a folder with other
files asks first, and
/, system folders and the home folder are refused. - Java builds on the host with its Maven or Gradle. Debug starts the program on the host and attaches the debugger here through a tunnel; breakpoints are the local files’.
- Run → Deployment: Deploy Now, Compare with Deployed, Open Terminal in Deployment, Edit Deployments. A deployment can also upload a file when it is saved. Deployments are exported and imported with the run configurations.
-
A Terminal tool window: shells on this machine, in tabs, inside Editora. Open it with Tool Window: Terminal (Alt+F12 in the IntelliJ keymap, Ctrl+` in VS Code, CUA and Sublime). It starts in the project’s folder; Terminal: New Terminal adds a tab.
- A focused terminal owns the keyboard: Ctrl+C interrupts, Ctrl+W deletes a word, Escape reaches vim. The
tool windows, the command palette and Search Everywhere still reach Editora, but only on keys a shell does
not use: a plain Ctrl+letter, Alt+letter, Alt+digit or F-key always goes to the shell, whatever the keymap
binds to it (IntelliJ’s Ctrl+K, VS Code’s Ctrl+B and F1). The terminal’s own commands and the Emacs
keymap’s M-x pass on any key, and a key typed into Settings → Terminal → Commands that reach Editora (say
M-1) passes too. Every Cmd shortcut on macOS reaches Editora. Copy and Paste are Ctrl+Shift+C/V (Cmd+C/V on macOS), shown in the terminal’s menu. Shift+Escape returns to the editor and leaves the terminal open; Shift+PageUp/PageDown/Home/End scroll the history. - On macOS, Option types the characters your keyboard layout puts on it (@ [ ] { } on many layouts); Settings → Terminal → “Option key as Meta” makes it readline’s Meta instead. Alt is Meta on Linux and Windows.
- Tabs can be renamed, moved (drag, Ctrl+Shift+PageUp/PageDown, or the tab’s menu) and closed from a tab menu; Ctrl+PageUp/PageDown switch between them, and tabs with the same title are numbered. A bell in a tab out of sight marks it.
- The terminal is in the Window menu (Terminal, New Terminal) and the File menu (Open Terminal Here); the Emacs keymap opens it with M-0. It follows the editor’s text zoom. It hides when its last shell exits.
- Pasting several lines into a program that would run each at once (sh, a REPL) asks first; a paste can no longer carry control characters or end bash’s bracketed paste early.
- Closing a window or quitting asks when terminals are running programs, in one question.
- Its colours follow the editor theme: the keyword colour is its red, the number colour its blue, and so on. Its font is the editor’s.
- Build Output’s stripe icon is now the tools glyph; the terminal glyph is the Terminal’s.
- Closing a terminal that is running a program asks first.
- Open Terminal Here (tab menu, Project tree, breadcrumb, command) opens a tab there instead of the system’s terminal; Settings → Terminal → “Open Terminal Here uses the system terminal” brings the old behaviour back.
- Ctrl+click (Cmd+click on macOS) a
path:line:colin the output to open the file at that place, or a URL to open it in the browser. - Settings → Terminal: the shell, text size, cursor, bell, scrollback, and which commands reach Editora.
- In a remote project, terminals run on the host: a real terminal (vim, htop and resizing work) over the project’s own SSH connection, starting in the project’s folder. Its tab is labelled with the host. If the connection drops, the tab keeps its text and offers Reconnect.
- A folder whose tools run in a dev container or a WSL distribution gets its terminal there too: a login
shell in the container (
docker/podman exec -it) or the distribution (wsl.exe), in the folder, labelled with the container’s or distribution’s name. Closing the terminal ends the shell inside. - Shell integration (bash and zsh, on this machine and on hosts, containers and WSL): the terminal knows the shell’s folder, so relative paths in the output open the right file and New Terminal Here opens a tab where the shell is. Ctrl+Shift+Up/Down (Cmd+Up/Down on macOS) jump between prompts, and Copy Last Command Output copies what the last command printed. Closing a remote terminal that is running a program asks first. Settings → Terminal → Shell integration turns it off.
- Find in the terminal (Ctrl+Shift+F, Cmd+F on macOS, or Terminal: Find) highlights every match in the scrollback; Enter goes to older ones.
- OSC 8 hyperlinks (
ls --hyperlink, gcc, git and other tools that mark links) open with a Ctrl/Cmd click; hovering one whose text is not its address shows the address. - Type-ahead shows what you type at once over a slow SSH connection, dimmed until the shell echoes it. It starts only when echoes take over 100 ms (Settings → Terminal → Type-ahead).
- Run in a Terminal tab: a run configuration’s Console option runs its program in the Terminal (programs that draw on the screen or read single keys), locally or on the project’s host. The tab stays when it ends, with the exit code; closing it while the program runs asks first. Run’s Stop button and stripe follow it, the next run of the same configuration reuses its tab, the configuration’s variables win over the login profile’s, and a missing working folder fails the run as in the console.
- Debug in a Terminal tab: Settings → Debugging → Java → “Run the program in a Terminal tab instead” does the same for a debugged Java or Python program.
- A terminal on a host or in a container opens without freezing the window: its tab says “Connecting to …” until the shell is there.
- The terminal is Termina’s (github.com/adriandeleon/Termina), ported.
- A focused terminal owns the keyboard: Ctrl+C interrupts, Ctrl+W deletes a word, Escape reaches vim. The
tool windows, the command palette and Search Everywhere still reach Editora, but only on keys a shell does
not use: a plain Ctrl+letter, Alt+letter, Alt+digit or F-key always goes to the shell, whatever the keymap
binds to it (IntelliJ’s Ctrl+K, VS Code’s Ctrl+B and F1). The terminal’s own commands and the Emacs
keymap’s M-x pass on any key, and a key typed into Settings → Terminal → Commands that reach Editora (say
-
The Run and Debug tool windows say which runtime the program runs under, in a small chip beside the state:
Java 25.0.4 (Temurin),Python 3.13.5,Node.js 24.18.1,Bash 5.2.37,GNU Make 4.4.1. Hover it for the runtime’s own version banner and, for Java, the JDK’s folder.- It asks the very executable the run starts, in the run’s folder and environment — so a run configuration’s
JDK, a virtualenv’s
python, a pyenv.python-versionand a remote host’s own runtime are what it reports. - The program doesn’t wait for the answer: the chip fills in a moment after the launch. It stays after the
program exits and is replaced by the next run. A runtime it can’t ask (a plain
sh, a compiled binary) and an attached debug session show no chip.
- It asks the very executable the run starts, in the run’s folder and environment — so a run configuration’s
JDK, a virtualenv’s
-
Settings search ranks its results. A hit in a setting’s title beats one in its description, a whole word beats part of a word, and the page with the best row opens; matching rows are tinted. Synonyms find settings known by another name (zoom, line endings, encoding, hotkey, colour scheme, soft wrap, gutter), and the search also finds commands in the Keymaps list. Ctrl+F (⌘F) focuses the search, typing on the sidebar starts one, and the sidebar scrolls to the page that opens.
-
Saving
settings.jsonin an Editora tab applies it in every window, and the Advanced page lists anything in the file that was ignored or changed on load (unknown keys, wrong types, out-of-range values). -
Restore from Backup… on the Advanced page brings back settings from a backup that Reset to Defaults wrote.
-
AI Actions: Test connection. Opening Settings no longer sends a request to the AI provider. The connection is checked while the AI Actions page is shown, a result is reused for three minutes, and Test connection checks again.
-
Keymaps: Remove (and the Delete key) unbinds a command. The filter finds words in any order, and a query that reads as a chord (Ctrl+Shift+S, C-S-s, ⇧⌘S, Ctrl+K Ctrl+W) lists the commands on that chord.
-
Tool Windows page: rows are grouped Left / Right / Bottom in stripe order, and Restore Default Layout puts the tool windows back where they start.
-
Editor theme “Automatic” follows the app theme again after you picked an editor theme.
-
Remote page: Connect… opens the Connect form for the selected site; host, port and user are checked as you type; a missing key file is flagged.
-
MCP page: shows whether the server runs and where, with Copy Endpoint Command and New Token.
-
Debugging page: an Install… button on each adapter card.
-
Web page: choose the browser HTML preview opens in; a Found / Not found row for Node.js.
-
LSP page: a card says when the project’s
.editora/settings.jsonoverrides its server command. -
Appearance: while text zoom is not 100% a row says so, with Reset zoom, and the live preview uses the zoomed size. A “Your own themes” row opens the themes folder and reloads themes.
-
Settings Sync: Cancel while Connect looks at the repository; the page says what is not synced.
-
23 more bundled file templates (New File From Template), 32 in all:
- Code: JUnit 5 Test (in the folder’s package), Java Shebang Script (an extensionless file the
javalauncher runs directly), pytest Test Module, and a Node.js TypeScript Project (module,node:testtest,tsconfig.json, README). - Files Editora previews or runs: Typst Document, Typst Document + Template (
template.typplus a document that imports it), Mermaid Diagram, Markwhen Timeline, and HTTP Requests + Environments (a.httpfile with@assert/@capturechecks plus dev/prodhttp-client.env.jsonandhttp-client.private.env.json). - Containers: Dockerfile (Java), a multi-stage Maven build that runs the jar on a JRE as a non-root user,
and the same with a
compose.yamland a.dockerignore. - Writing: README, Changelog (Keep a Changelog), Architecture Decision Record, Blog Post (YAML front matter, dated file name) and Meeting Notes.
- Project files: License: MIT (this year and your author name), License: Apache 2.0 (verbatim),
.gitignorefor Java, Python and Node,.editorconfig, and GitHub Issue + PR Templates under.github/. - The multi-file ones are also offered by New Project From Template.
- Code: JUnit 5 Test (in the folder’s package), Java Shebang Script (an extensionless file the
-
Remote: logins ask what they need, while they run. The connect form no longer has a Secret field. A password, a key’s passphrase, and a server’s own questions — a 2FA or one-time code, a Duo answer — are asked for in a login dialog when the server or the key needs them, as
sshdoes. A wrong answer is asked for again; a cancelled passphrase skips that key and the login goes on.- Password logins no longer try your default SSH keys first, and a key login uses only that key.
- A failed connect says why: the host could not be reached, did not answer, its host key has changed (with
the
ssh-keygen -Rline to remove the old entry), or the login was refused. Cancelling only says so in the status bar.
-
Remote: SSH agent. An Automatic login uses the keys your SSH agent holds —
ssh-agent, 1Password, Secretive, gpg-agent, or Windows’ OpenSSH agent — before any key file, so a key on a security key (FIDO) or a smartcard, or one kept in a password manager, logs in.IdentityAgentin your SSH config chooses the agent (noneturns it off). Waiting for a security key’s touch does not time the login out. The agent is never forwarded to the server. -
Remote:
~/.ssh/config. The connect form offers the hosts your SSH config names, and for the host you type shows where it really goes (HostName, ProxyJump, IdentityFile) and fills in its User and Port. Logging in follows the config assshdoes: itsIdentityFilekeys,IdentitiesOnly, andProxyJumpthrough a jump host. “Default SSH keys” is now Automatic (like ssh): the agent’s keys, then the config’s, then your default ones.Includelines are followed, globs too (Include conf.d/*, on Windows as well).ProxyCommandis not supported. -
Python: one interpreter for Run, Debug and code intelligence. Editora now finds a project’s own Python: an activated environment (
$VIRTUAL_ENV,$CONDA_PREFIX), else a.venv/venv/envfolder in the project, else Settings → Debugging → Python interpreter, else the system Python (py -3on Windows, never the Microsoft Store stub). Run, run configurations, Debug, Pyright, Doctor and the formatter all use the same answer.- A status-bar item on Python files shows the interpreter and why (
Python 3.13.5 (.venv)); click it (orPython: Select Interpreter) to pick one of the project’s environments, a Python on PATH, or any file, per project. “Detect automatically” goes back to the rules above. - Pyright is told the interpreter, so a venv’s packages resolve without a
pyrightconfig.json. - On SSH hosts, WSL and containers the project’s venv is found on that machine; a new
pythonhost tool sets the host’s Python.
- A status-bar item on Python files shows the interpreter and why (
-
Python tests: a pytest runner. Test files (
test_*.py,*_test.py) get a gutter ▶ on every test function, class and method and one for the whole file; results fill the Test Results window, with Rerun, Rerun Failed and run-one-row. It uses pytest when the interpreter has it, elseunittestforTestCasetests, else says how to install pytest. Debug Test works from a test line and from a Test Results row. -
Python: Format Document runs Ruff or Black (the project venv’s first, then PATH), also with language servers off. Doctor shows which one it will use.
-
Python run configurations: an Interpreter and Interpreter options field, and a new Python module type that runs
python -m <name>. -
Debugging: a hit count for breakpoints (Edit Breakpoint), an exception breakpoint picker that lists what the debugger offers (Python: raised, uncaught, user-uncaught), Debug File next to Run File in the editor’s menu, and the exit code at the end of a Python debug session.
-
Python editing: folding by indentation (so sticky scroll pins Python scopes), and highlighting for pip requirements files.
-
“Turn on Python code intelligence?” — a one-time offer when the first Python file opens while language servers are off.
-
Java debugging: hot code replace. Saving a
.javafile during a Java debug session rebuilds it with the Java language server and loads the new code into the running program. The Debug console says which classes changed, or why they could not be (adding a method or field still needs a restart). Settings → Debugging → “Apply code changes to a running Java program”: automatically (default), on command only, or off; and Debug: Apply Code Changes. -
Java debugging: Restart Frame (call-stack right-click menu and a command) and Smart Step Into… (pick which call on the line to step into).
-
Debug: Breakpoints… lists every breakpoint: Enter jumps to it, Alt+E enables or disables it, Alt+D removes it, Alt+M mutes them all. Also Mute Breakpoints, Enable/Disable Breakpoint at the caret, and a right-click menu on a breakpoint glyph (Edit…, Enable/Disable, Remove, Breakpoints…).
-
Completion while debugging. Ctrl+Space, or typing
., lists what the debugger can complete in the Debug console’s evaluate field, the watch prompt and a breakpoint’s condition and log message (while the program is paused). -
The value popup unfolds. Hovering a variable, or Show Value at Caret, shows an object, array or collection as a tree (big arrays a page at a time), with Copy Value and Add to Watches; arrow keys, Enter and Shift+Enter work it from the keyboard.
-
Exception breakpoints: Caught and Uncaught are two toggles, checked in the Run menu and shown in the Debug window, kept per project. Settings → Debugging can limit them to some exception classes.
-
Java step filters and static fields. Step Into skips JDK classes and synthetic methods, and a class’s static fields show among the variables; both are on by default and can be turned off in Settings → Debugging.
-
Show Value at Caret (keyboard), Copy Value, Copy Name and Add to Watches (filled in from the selected variable) in the Variables tree; Up/Down history in the evaluate field.
-
Debugger keys in every keymap. CUA and Sublime get VS Code’s F-keys (F5, Shift+F5, Ctrl+Shift+F5, F6, F9, F10, F11 = Step Into while paused and Full Screen otherwise, Shift+F11); IntelliJ, VS Code and Emacs gain the missing ones. The Run menu lists every debugger action, and the editor’s right-click menu has Toggle/Edit Breakpoint, and while paused Run to Cursor, Show Value and Add to Watches.
-
JDK and library frames show their source (read-only) when you step into them or click them.
-
HTTP Client: Run All lists every request. After Run All the response view used to show one response and a line like “Run All: 3 of 10 failed”. Now a results list sits above the tabs: a title (“Run All · 3 of 10 failed · 4.1 s”), then one row per request in run order with its status, name, method and path, time, and tests (
✗ 2/3in red when one failed). The first failure is selected and shown; selecting another row shows that response in the tabs. Only failures hides the rest, the chevron collapses the list, and the list scrolls on its own so the tabs keep their room. Enter or a double-click goes to the request in the editor; right-click a row to run it again or copy it as cURL. A cancelled Run All lists the requests that finished. The list stays until the next run or Clear. -
HTTP Client: results on the request lines. After a request in a
.httpfile runs, its method/URL line shows how it went, in muted text:200 OK · 83 ms · ✗ 1 of 3 tests,404 Not Found · 1 ms,Connection refused. The status is in the outcome’s colour, failed tests are red, and the request’s ▶ takes the colour too (amber for a 4xx, red for a 5xx, a failure or failed tests).- Click the result to show that response in the response view; hover it to see when it ran.
- The results come from the response history, so they are back when the file is reopened, and Clear removes them. A request whose line you edit loses its result.
- The text is not part of the file: it is never copied, searched, saved or undone.
- Settings → Web → HTTP Client → Show results after each request line (on), or
HTTP: Toggle Results After Request Lines.
-
Run Configurations → Main class has a Browse… button: pick the
.javafile and the fully qualified class name is filled in (src/main/java/test/App.java→test.App), from the file’smainmethod or else its package and name. A configuration still called “New Configuration” is renamed after the class.
Removed
- The GnuPG registry plugin (
gpg-tools): GnuPG is built in now. An installed copy is removed at startup (its gpg path and last recipient are kept), and it can no longer be installed.
Changed
-
What a session runs is what it started with. Every window applies the plugins that loaded at launch; an install, update, enable, disable or removal takes effect at the next start, as the Settings page says. An update or removal of a running plugin is applied at the next start before anything loads (Windows cannot replace an open jar), and a declined update keeps the installed version, enabled.
-
Plugin commands and tool windows are always in the plugin’s namespace (
plugin.<id>.…), so a plugin can no longer replace a built-in command; an untitled one shows the plugin’s name, and tool-window toggles read “Tool Window: …”. -
activeEditor()stays on the buffer it was asked for: a plugin that finishes on a worker writes into the file it started on, never the tab in front by then (format-runner overwrote another file). Plugin API reads off the JavaFX thread throw; writes are handed to it. -
Plugin feedback is visible and translated: start and main-class failures go to the Message Log and the Settings row, a failed start’s commands, chords and segments are taken back, failing plugin commands name the plugin, declared commands show their output, and install and registry errors are sentences in your language in a dialog titled “Plugins”.
-
Settings → Plugins: installed plugins come first, Browse comes back to Settings when its picker closes, Browse and Install from file are greyed while plugins are off (Simple mode says it is the reason), Remove names the plugin and its saved data, and “Require signed plugins” is now “Require a signed registry”.
-
Export Configuration asks before including the data plugins saved, and never includes the installer’s staging folders.
-
The example plugin uses chords that are free in every keymap (Ctrl+Alt+Shift+E / Y).
-
Changing tab size or another view setting with many files open is about nine times faster; tabs that are not shown catch up when you show them.
-
Codex has its own model setting instead of sharing Anthropic’s.
-
Sync Now can be cancelled until it starts writing files on this computer.
-
Plugin load errors are translated; the parser’s own text is in the tooltip.
-
View: Toggle Word Wrap changes the project’s value in a trusted project that sets wrap. The Doctor’s build and debug rows and Markdown lint’s tab handling use the project’s values too. The trust command is named Project: Trust This Project’s Settings.
-
Installing the Java language server gets Eclipse JDT LS 1.62.0 (was 1.60.0): Java 27 support, per-parameter signature help, a quick fix to change a field’s access modifier, and Javadoc rendering fixes. An existing install keeps its version until it is installed again.
-
Doctor tells the truth about a healthy machine and puts problems first. A missing tool is red only when something in the window needs it: a file of that language is open, the project has its marker file (
pom.xml,go.mod,Cargo.toml,package.json…), or you set its command. Everything else is a neutral “Not installed” that keeps its Install… button and is not counted. Turning LSP on used to show about fifteen red rows for languages never opened.- Problems and warnings move to a “Needs attention” group at the top; a section that is all OK folds to one line, and the not-installed tools of a section fold together. The summary counts in words (“1 problem”) and its counts jump to the group.
- Rows show a status pill like the Settings pages, the tool with its command under it, and the version or path in one column. Settings… sits on every row (shown on hover where nothing is wrong); a turned-off feature has Turn on; the Python formatter has How to install; right-click copies a row or its path, or reveals the path.
- Copy Report puts a plain-text report (Editora version, OS, Java, every row) on the clipboard.
- Rows update in place, so the keyboard focus no longer jumps to the toolbar as each result arrives. Refresh and Install… keep the last results on screen while checking again, the summary shows the progress, the header says when the check ran, and an install’s button reads “Installing…”.
- Tips match the problem: Java debugging with LSP off offers Turn on (not Install…), a server with no command
says so, and debugpy is named as a Python module with its
pip installline. - Build-tool rows check the command set in Settings or the project’s wrapper, not just
mvn/go/… on PATH. - Graphviz and PlantUML show their versions (
dot -V,plantuml -version). - New rows: the AI provider (is a key set), the container engine, and WSL on Windows. New sections: Formatting & Linting, HTTP Client, Remote & Containers.
- In a project on an SSH host, WSL or a container, the header says the rows describe this computer.
- The message log has an Open Doctor button.
-
The Welcome page was reworked after a UI review:
- Recent Projects are listed above Recent Files, newest first, each opening (or focusing) its project’s window. A project whose folder is gone is not offered.
- A recent row keeps the file name whole and shortens the folder from its start; a long path no longer
widens the page or pushes it off-centre. Folders are relative to the project (whose chip already names it)
or start with
~; a remote file names its host. Right-click a row to copy its path or remove it. - 1–9 open the numbered entries, and the page focuses the first one when it opens, so Enter opens it.
- A Customize block names the keymap and theme and changes them; with the Emacs keymap it explains the
C-/M-notation. On a first run it sits right under Start. - Open File shows its own chord (Ctrl+O in the VS Code keymap, not Quick Open’s Ctrl+P; C-x C-f in Emacs).
- Text zoom scales the whole layout, so labels and chords no longer clip at 150 %. Links underline on hover and keyboard focus only, action rows highlight on hover, “Show 7 more” says what it does, the footer link matches the footer, and saved sites no longer repeat their name or print port 22.
- Doctor moved to a Help row with Documentation and What’s New (this build’s release notes).
-
Closing the last tab leaves a hint in the editor area (Open File, Open Folder, Command Palette, Welcome Page, with their chords) instead of a blank panel, and keeps focus there rather than on the toolbar.
-
Groundwork for an integrated terminal (ADR 0014): the app now carries JediTerm core (the terminal emulator), pty4j (pseudo-terminals on macOS, Linux and Windows), JNA and the Kotlin standard library, about 7.5 MB more in the installed app. Nothing uses them yet apart from
editora --check-terminal, which starts a shell on a pseudo-terminal and says whether it answered. -
The technical dictionary knows over 900 more terms: Git (worktree, unstaged, rebasing), editor and UI words (submenu, breakpoint, strikethrough, monospace), shell tools (ripgrep, fzf, cwd), Unix and C (inode, glibc, malloc, cgroup, ncurses), cryptography (cryptographic, kerberos, keyring), fonts and graphics (harfbuzz, colormap, grayscale), the Java toolchain (jlink, jpackage, Temurin), language servers, web, devops and AI names, -ed and -ing forms of the words it already had (deserialized, symlinking, canonicalized), and British spellings (tokenised, rasterising). It no longer lists “nat”, “elt”, “os”, “io” or “gan”, which hid typos of “not”, “let”, “so”, “to” and “can”. The file is sorted by section and explains what not to add; plurals it listed twice are gone, since spell check accepts the plural of any listed word.
-
Debug variables use the editor’s syntax colours. Names, values and types in the Debug tool window’s variables and watches are coloured like code in the current editor theme — strings, numbers,
true/null/Noneand type names — including each element of a list or dict value, instead of the app’s status colours. -
Settings: every external tool row looks and reads the same — language servers, debug adapters, Mermaid, Diagrams, Typst, build tools, Node.js and AI agents show “tool: found (path)” or “tool: not found”, then Install… or a link. Diagrams links to its install help, and Build Tools says whether the command it would run exists.
-
The theme pickers group themes under Light and Dark headings, with your own themes in a group of their own.
-
Keyboard chips read on every app theme, whatever the editor theme: the shortcut colour follows the app theme everywhere (palette, Welcome, menus, Keymaps), with at least 4.5:1 contrast on all bundled themes.
-
Macros: the step reorder buttons are labelled Move Up / Move Down and grey out at either end.
-
Python Run:
- The script runs in its own folder with the project root and
src/onPYTHONPATH, so package imports work. - A saved run configuration writes that folder into Working directory.
- Output streams as the program prints (
PYTHONUNBUFFERED) and is UTF-8 on every platform. - A specific shebang (
python3.12,pypy3,uv run --script) is honoured. - Stop sends Ctrl-C first, so
finallyblocks andatexithandlers run, and the console’s first line shows the command that ran.
- The script runs in its own folder with the project root and
-
Python Debug runs the program in the same folder, with the same interpreter and
PYTHONPATHas Run.- A program that reads
input()gets the program console. - An uncaught exception stops the debugger, as in VS Code.
multiprocessingchildren run instead of waiting for a debugger.
- A program that reads
-
Python typing:
else,elif,except,finallyandcaseline up with their statement as you type the:.- Enter after
return,pass,raise,breakorcontinuesteps out a level. - Wrapped statements and open brackets indent as PEP 8 shows.
- In Python and YAML, Backspace in the indentation removes one level and no longer joins the line above.
-
Python code intelligence:
- Unused names are faded and deprecated calls struck through.
- Go to Definition into the standard library or site-packages stays on the project’s server and opens the file read-only.
- Organize Imports works for Python and for any server with a
source.organizeImportsaction. - Python keeps its server up to 50,000 lines.
- Untitled Python buffers get it too.
-
Python highlighting: generics (
def f[T],class C[T]),typealiases, t-strings,matchused as a name, and0x/jnumbers.__init__and other methods named like builtins are back in Structure. -
Python snippets: Enter after a keyword such as
tryends the line instead of inserting thetrysnippet; Tab still expands it. -
Python indentation: a file’s indent size is guessed from its statements only, so PEP 8 hanging indents no longer make it 8 spaces.
-
Language names: the status bar and the language picker show readable names (“pip requirements”).
-
Quotes:
f",rb"and the other string prefixes auto-close in Python, and"""closes itself. -
File types:
Pipfile,poetry.lock,uv.lockandpdm.lockopen as TOML;Pipfile.lockand.ipynbas JSON.uv run,pipx run,pypyand free-threadedpython3.14tshebangs are Python.- Toggle Comment in an INI file uses the comment character the file already uses.
-
Java Debug builds the project first. A Maven or Gradle debug launch asks the Java language server to build the project; compile errors stop the launch and are listed in the Debug console as links. Before, Debug ran whatever was in
target/classes(ClassNotFoundException on a new project, old code after an edit). -
Debug ▶ and Debug on a file use the class’s run configuration (arguments, VM options, environment, working directory, JDK), as Run ▶ does, and every unsaved Java file of the project is saved before a Java debug launch.
-
The Debug window never takes the keyboard. Starting a session or stopping at a breakpoint leaves focus in the editor; a stop reopens a closed Debug window. In the Debug window, Stop and Restart need Shift (Shift+K, Shift+R).
-
The stopped line is easy to see: amber with a gutter arrow, never hidden under the sticky header; the line an exception was thrown from is red, and the exception is the top row of Variables.
-
Inline values stop at the stopped line, and a lambda parameter no longer shows an outer variable’s value. Hover waits for the mouse to rest and skips comments and strings.
-
Breakpoint kinds differ by shape (a diamond for a logpoint, ”=” marks for a condition), and their hover says the condition, log message and hit count. A breakpoint on a blank or comment-only line is refused.
-
Debug window: opens taller, Variables is the widest column, JVM housekeeping threads are hidden and the stopped thread is marked, lambda frames read
<lambda>, frames without source are muted, stack-trace links open on one click, “Exited with code N” stays after the program ends, and setup messages say which piece is missing (LSP off, Java server off, jdtls or java-debug missing), with an Install button on the Java card. -
Debug Test and Debug via Build use a free JDWP port for Maven test JVMs and Spring Boot, attach every forked JVM in turn, and Stop ends the test or build run too.
-
Before-launch steps of a Java run configuration run in the project root (Run and Debug).
-
Settings schema 129 adds the hot code replace, step filter, static fields and exception class settings; workspace schema 19 keeps the exception toggles per project.
-
Mute Breakpoints is kept per project, fades every breakpoint glyph while on, and is checked in the Run menu. Workspace schema 20.
-
Gradle Debug Test and Debug via Build give every forked JVM a free debug port (through an init script) instead of
--debug-jvm’s fixed 5005, and attach each one in turn. -
Syntax highlighting for C#, CSS, dotenv, PowerShell and SQL is updated to the shiki tm-grammars 1.32.22 grammars (from 1.31.15).
- CSS colours nested rules (
&,> h2inside a rule),@layername lists,@import … layer(…)and the operators insidecalc(). - C# knows
uniondeclarations and the#:refdirective of file-based apps, and an interpolation that opens at the end of a line no longer ends the string. - SQL colours a
[bracketed identifier]and its]]escape; a numeric dotenv value (PORT=8080) is a number. - PowerShell colours automatic variables (
$Error,$Host,$PSHome…) as variables, not constants.
- CSS colours nested rules (
-
IBM Plex Mono is updated from 2.3 to 2.5. The ASCII control pictures (␀ ␉ ␊ ␛, U+2400–2421) now come from Plex itself instead of a fallback font, so they keep the editor’s column width, and Plex covers more transliteration letters and combining marks. The four font files add about 145 KB to the package.
-
Remote: one login per connect. Connecting to a remote folder from another window no longer logs in a second time for the project’s own window: that window takes over the session you just logged in with. A password or passphrase is asked for once, and a server that wants a one-time 2FA code no longer needs two of them. Closing the window you connected from leaves the project’s window connected.
-
Settings switches that only change the editor view (line numbers, minimap, rulers, wrapping, tab size…) no longer rebuild the rest of every window; with many files open they apply about five times faster.
-
Reset to Defaults keeps your AI API keys and the Settings Sync connection. Its question lists what is reset and what is kept and names the backup it writes, and Cancel is the default button.
-
Number fields refuse a value out of range (shown in red with the range) instead of quietly clamping it.
-
Off switches are visible in every theme, and a disabled switch is grey.
-
Changing the language shows “Restart Editora to apply” on its row instead of a dialog at every step.
-
The Settings window stays where you put it for the rest of the session, and says once that changes apply as you make them.
-
Beta pages carry one Beta pill beside the page title; Settings text grows with the app’s font size.
-
List editors apply as you type. Snippets, Templates, Abbreviations, External Tools and Remote sites no longer have a Save button; every change is saved as you make it, as on every other page. Macros keeps Save / Revert.
-
Deleting asks first on every list editor (“Delete “x”?”, Cancel is the default). Removing a Remote site also offers to forget that commands may run on its host.
-
Settings that depend on a switch grey out while it is off, with a note naming the switch, on every page (AI, AI Agent, LSP, Debugging, Mermaid, Diagrams, Typst, Git, Remote, Spell Check, rulers, plugins).
-
Bad input is shown, not thrown away. A ruler list, a TODO pattern, a Remote port or host, a plugin registry URL or a sync branch that cannot be used turns its field red with the reason and keeps what you typed.
-
The Editor page is regrouped into Display, Editing and Clipboard, with Saving right after Indentation; the LSP switches on Code Completion are titled “Language server features”. Updates and Trusted folders moved to Advanced.
-
Every page has a one-line subtitle, and help text names the pages that really exist.
-
Shortcuts recorded in Settings show in the active keymap’s notation, in the recorder, the conflict question and the status line. A bare letter is refused as the first key of a shortcut.
-
Macro, external-tool and run-configuration shortcuts follow a keymap switch. Other custom shortcuts are kept per keymap, and the Keymap row and “Reset all shortcuts” say so.
-
Snippets can be added for every language, and snippet and template bodies use Emacs keys only under the Emacs keymap.
-
The font list drops weight variants and math/symbol fonts and marks the bundled fonts; themes are tagged (light) or (dark).
-
Simple UI mode trims the right-click menus too, as it already trimmed the menu bar.
- Tab menu: keeps Save, Save As, Print, Export to PDF, Close, Close Others, Close All, Reveal in File Manager, Copy Path and Rename. Unpin stays on a tab that was pinned before.
- Editor menu: keeps Comment / Uncomment, the spelling suggestions, Cut, Copy, Paste, Undo, Redo, Select All, Print and Export to PDF. Run, Debug, the LSP, build, AI, Markdown and Typst submenus, Add Bookmark and Add Personal Note are hidden.
- Project tree menu: keeps New (a file or a folder), Rename, Undo Move, Delete and Reveal in File Manager.
- Preview menu (Markdown, Typst, Markwhen, diagrams): keeps the copy actions, Go to Source, Enlarge, Export to PDF and Print. Copy HTML and the Word, OpenDocument, PNG, SVG and Markwhen JSON exports are hidden.
- Git, Local History, the compare actions, Open Terminal, Pin and the bookmark and note entries are hidden on the tab, editor and Project tree menus. Turning Simple mode off brings every entry back.
-
HTTP Client: the response view gives the body the room. The Request, Tests, warnings and headers used to stack above the body, which a normal Split left three lines. Now one header row and a tab strip come first.
- One header row: Run (with its shortcut from your keymap), the status as a coloured pill (green 2xx, blue 3xx, amber 4xx, red 5xx and failures), the time and size, then History. Its tooltip has the full status line and when the request was sent.
- Tabs: Body · Headers · Tests · Request · Notes, with counts: the number of headers, tests passed of total (red when one failed), and warnings plus files written (amber when there is a warning). Body is shown by default. A run switches to Tests on its own only when a test or a script failed; warnings never switch tabs. The tab you pick stays across runs while a response has it. Tab reaches the tabs, and the arrow keys, Home and End move between them.
- Headers are a name/value list: right-click to copy a value, a header, or all of them. Request shows
the request as sent, highlighted like a
.httpfile and filling the tab. - The actions are icons at the end of the tab strip (Wrap, Copy as cURL, Open in tab, Save response), with their shortcuts in the tooltips; Clear is in the ⋯ menu.
- In a narrow panel History narrows first, then the time and size hide, then History moves to a second row. The icons fold into the ⋯ menu, then the counted tabs show only their counts.
-
HTTP Client: the environment is chosen beside the editor. A
.httpfile shows its environment on a pill beside the Editor/Split/Preview toggle (“Env: dev”, or “No environment”), in every view mode and as soon as the file opens, and in the status bar. Clicking either opens the file’s environments;HTTP: Select Environmentopens the same menu from the keyboard (arrow keys and Enter; Escape goes back to the editor). The first run of a file no longer goes out without an environment because the response view was not open yet. The Environment picker in the response view is gone; each file keeps the environment it had.-
Use environment dev: an unresolved
{{variable}}that an environment of the file defines offers that environment as a quick fix — right-click it, or use the Code Actions chord with the caret on it. Its tooltip names the fix, and with another environment selected it says which ones define the variable. -
A variable sent empty is reported with the environments that define it. Each response in History records the environment it was sent in, and the response view shows it beside the time and size (“env dev”).
-
The menu says when no
http-client.env.jsonwas found for the file, and opens the env files it has. -
In a narrow panel History narrows first, then the time and size hide, then History and the environment move to a second row. The icons fold into the ⋯ menu, then the counted tabs show only their counts.
-
-
HTTP Client: the response view says what is going on between responses.
- Before the first run (and after Clear) it shows which request Run will send — the one at the caret, by its
###title — your Run shortcut, that the gutter’s ▶ runs a request, and the file’s requests: click one (or press Enter on it) to run it. - While a request is sent, the status says “Sending Get one user… 1.2 s” (“Sending 3 of 10: …” in a Run All) over a thin progress line, and the response shown before is one “Previous: 200 OK · 16:42:31 · getUser” row, which you can click to see it. Its body no longer disappears without a trace, nor shows under the new run.
- While a trust prompt is open it says “Waiting for your answer…” without a clock; the time counts from when the request is sent.
- After Cancel it says how long the request ran, and the previous response’s row comes back, selected in History.
- A request that got no response shows a card in the Body tab naming what went wrong (Connection refused, Host not found, Timed out, Certificate problem, Not sent…) with the explanation and Run again and Copy as cURL buttons; a pre-request script that did not run also offers its output. The view opens on that card.
- Before the first run (and after Clear) it shows which request Run will send — the one at the caret, by its
-
HTTP Client: response bodies read like other tools show them. JSON is laid out as
"id": 42, two spaces per level, every field and array element on its own line, and[]/{}for empty ones (it was Jackson’s"id" : 42with[ {on one line). HTML responses, such as a one-line 404 page, are indented one element per line, with text and inline tags kept together and the contents of<pre>,<script>,<style>,<textarea>and comments left as they are; a page the server already indented, or one too irregular to format safely, is shown as received. Only the view changes: Save response and Open in tab still write the body exactly as it arrived. -
HTTP Client: image responses say what they are. A caption line gives the format, the size in pixels and the size in bytes (“PNG · 160 × 160 · 858 B”), the picture sits on a checkerboard so transparent parts show, and Fit (the default, which scales a large picture down to the panel’s width but never enlarges a small one) and 100% switch between fitting and the actual size.
Fixed
-
File Information and the status bar show the same word count. File Information counted “well-known” and “repo’s” as two words each and skipped numbers; it now counts as the status bar does.
-
Debugging a Kotlin script with Kotlin 2.4.10: once the script had run, adding or removing a breakpoint failed with “Internal error”. Two classes in that compiler carry source-map data (an SMAP) the JDK’s debugger cannot read; the JVM debugger now treats such a class as one without source information, in breakpoints and in the call stack, instead of failing.
-
JavaScript editing without a language server:
- JSX in a
.jsfile no longer turns the rest of the file into a comment or string (.jsuses the TSX grammar, as VS Code does), and JavaScript is in the status-bar language picker. - A regex such as
//or/{/` no longer removes every fold, sticky-scroll header and Structure entry below it. - Structure lists one-line methods and arrow functions; Go to Symbol finds class and object methods and
exports.x =; Go to Definition picks the nearest declaration;$and#are part of names. - Enter continues a
/** */comment; Toggle Comment never touches a#!shebang and lines its markers up. - Smart indent handles
casebodies, brace-lessif/for/while, open argument lists and call chains (in every brace language). - A quote typed inside a string, comment or regex is not paired.
- Template literals,
.length,import.metaand BigInt literals get the right colours. npx/pnpm exec/bunxandzxshebangs and React modelines are recognised;.mocharc,.nycrc,.lintstagedrcand similar open as JSON.
- JSX in a
-
A minified file with many long lines no longer stalls highlighting in every JavaScript tab for about 45 s: it opens in long-line mode, and the tokenizer gives long lines a time budget. Typing in a one-line bundle is about 30% faster.
-
The TypeScript / JavaScript language server did not start on a fresh install. npm’s latest TypeScript is now 7, which has no tsserver; Editora’s install step (and the Node.js TypeScript Project template) now take TypeScript 6. When no usable TypeScript is found the server is not started and the message says why, instead of three crashes and “keeps crashing”; Doctor and Settings no longer show it as OK, and opening more tabs no longer starts it again.
-
An untrusted folder’s own
node_modules/typescriptno longer runs when a JS/TS file opens: the TypeScript installed beside the server is used until the folder is trusted, and the trust prompt lists the folder’s copy. -
The TypeScript server no longer downloads type definitions silently (
npm installagainst the registry into~/.cache/typescript), and loose scripts in different folders share one server (about 320 MB instead of 550 MB each). -
Organize Imports works on JavaScript and TypeScript, and the code-action menu offers Fix all, Add missing imports and Remove unused. Quick fixes follow the file’s indentation. A monorepo without a project open roots at its tsconfig/jsconfig.
-
Debugging JavaScript:
process.stdout.write/process.stderr.writeoutput andreadlineprompts reach the Debug console, and the program reads typed input; the program runs from its package folder; node-internal frames are skipped; errors in the console and watches say what went wrong instead of “Unset error message.”; a js-debug that cannot start (or a Node older than 18) says so instead of stopping silently; function values take one line; a bad breakpoint condition marks the breakpoint as rejected, once; child processes and workers list all their threads; js-debug is pinned to v1.117.0. -
node_modulesno longer floods search. Find in Files, the symbol index, Go to File, Search Everywhere, TODO and the Project filter skipnode_moduleseven without a.gitignore(a 60,000-filenode_modulesused to push every project file out of the index);!node_modules/in a.gitignore, or an include glob naming it, looks inside. Find in Files also says when it stopped at its 5,000-match limit exactly at a file boundary. -
Run console after a flood: the newest output on screen no longer has gaps when a program printed faster than the console could show, and the status line says when output was skipped.
-
npm scripts: a workspace member runs its workspace’s package manager (pnpm, yarn, bun), not npm; an npm run configuration uses the project’s manager too, and the npm command setting no longer replaces a different manager. Settings → Build Tools names the detected manager and why (“pnpm (pnpm-lock.yaml)”). A file inside
node_modulesno longer turns the npm tool window into the dependency’s. A missing node, npm, pnpm, yarn or bun says how to get it instead of showing the Java error; a script that fails with nonode_modulessuggests installing first. The Output console draws colours, names the runtime (“Node.js 24.18.1”), and its tab is named after the manager. Stop sends Ctrl+C (SIGINT) first to Node and its package managers. A malformed package.json says where. Script rows show their command. -
Test Results with TAP: a
describeblock is no longer counted as a failed test, and a failure shows its error and stack instead of the YAML block. -
Node.js stack-trace links work for ESM
file://frames (spaces, Windows drives), paths with spaces,.jsx/.tsx/.mts/.ctsfiles and tsc errors, and jump to the column. -
Run and Output consoles say when the oldest output was dropped to stay under the size cap.
-
Closing a window no longer keeps it in memory (about 21 MB each, plugin panes included): the Settings Sync listener of every closed window was never removed.
-
A plugin thread can no longer keep Editora running after quit, where the next launch was “handed to” an editor with no window.
-
Chords a plugin bound in code survive a keymap switch or a key-binding edit, and a keymap rebuild in Simple mode no longer turns plugin chords on.
-
A plugin’s
start()is timed; one that holds up window opening is named. -
Registry and download reads have an overall deadline, a second Browse while one is fetching joins it, a picked file over the size cap is refused before it is read, and an install worker that fails always reports back.
-
Removing a plugin deletes its plugin.json last, so a folder that cannot be fully deleted stays listed and removable; staging folders a crash left behind are swept at start; concurrent rescans can no longer close class loaders in use.
-
Plugin versions compare by semver:
rc10 > rc2,+buildis ignored,v2.0 < 10.0; the install question says Update, Reinstall or Downgrade where that is what an install would do, and Browse marks a newer installed version. -
The palette shows plugin chords, plugin right-click items have their own separator, a plugin status segment is reachable by keyboard and names its plugin, and
caretLine()is right in a narrowed buffer. -
The minimise, maximise and close buttons were nearly invisible with a dark theme and the menu bar in the title bar. They followed the desktop’s light or dark setting rather than Editora’s theme, so a dark theme on a light desktop drew them dark on dark. They now follow the app theme, and change with it.
-
When the system had no file watcher to give (Linux: inotify instances used up), the project tree and language servers silently stopped following the disk. They now check folders every 2 seconds, and on Windows also notice a save that replaces a file with one of the same size and time.
-
Plugins: Set Registry URL accepted an address that is not https; it now refuses it like the Settings field.
-
A submenu’s › arrow sat in the middle of its menu (VCS → Changes, Branches, …), just past the longest submenu name. It now sits at the menu’s right edge, past the shortcut column.
-
A Markdown code span after a stray double backtick rendered as plain text (
`` `a` `c`showed`c`literally): commonmark-java 0.30.1 fixes the regression 0.30.0 brought in. -
With a dark UI theme and a light editor theme, the Welcome and Doctor tabs were white blocks with near-invisible titles; their selected tab now takes the page’s own background.
-
Spell check accepts the possessive of any dictionary word, such as “someone else’s” and “another’s”. Only words the dictionary lists with a possessive were accepted.
-
Settings scrolled sideways at its 900 px minimum width in German, French, Spanish and Portuguese (Snippets, Templates, Remote), and controls sat a scrollbar’s width apart on short and long pages.
-
A
.httpfile saved as Markdown kept its{{variable}}squiggles until Markdown lint’s first result replaced them, and for good with Markdown lint off. -
A snippet trigger with a space in it was saved and never expanded. It is now refused with the reason shown.
-
Python:
- Run used
python3from PATH whatever the project or the Debug setting said. - Output arrived only when the program ended, with stderr ahead of stdout.
- On Windows the Store stub ran, and
print('✓')raisedUnicodeEncodeError. - Changing a Python configuration’s working directory broke its target.
- ▶ on a test file reported exit code 0 without running a test.
- Run used
-
Python Debug:
- Debugging a
multiprocessingprogram hung. input()raisedEOFError.- An interpreter with arguments or an
envprefix hung or lost them. - A breakpoint the debugger moved onto a conditional one silently dropped its condition.
- Hovering
p.xshowed the localx. - A Python row in Test Results had no Debug This Test item.
- A file with a
uv run --script(or pipx, Poetry, PDM) shebang handed debugpy the runner instead of a Python; Debug runs it under the project’s Python. - debugpy installed without Node and is no longer fetched again while debugging is off.
- Debugging a
-
Python code intelligence:
- A new module created outside Editora never resolved until a restart.
- Windows with no project saw no file changes at all.
- A nested
requirements.txtsplit the project’s server. - A missing custom server command was offered the Pyright installer.
- An empty ”…” stayed in the status bar.
- The hover cut off Pyright’s signature block.
- Structure showed return types with a trailing colon.
-
Python console links:
- Extensionless scripts, warnings and pytest/mypy/ruff
file.py:12:lines are now links. - So are pdb’s
> file.py(12)lines and paths containing quotes.
- Extensionless scripts, warnings and pytest/mypy/ruff
-
Python Project template: its README commands work on a fresh project.
-
Spell check: it now checks the first word of an f-string. Common Python terms (kwargs, asyncio, noqa) are no longer flagged.
-
Go to Symbol without a language server: Python methods show their class.
-
Java Debug:
- A class with a
packageline in a folder with nopom.xmlor Gradle build could not be debugged (“Could not find or load main class Main”). Editora now corrects the Java server’s source folder. - Debug on a file could run a different program: another
mainof the project, or a class never compiled. - Editing a file during a session moved its breakpoints and the stopped line off the code the program runs; lines are now matched to the launched code, and a stop in an edited file says the program runs the old code.
- Breakpoints in other unsaved files were silently not hit.
- Starting a session moved focus into the Debug window, where typing
rorkrestarted or killed the program. - With “Run the debugged program in the Debug console” off, a crashed Java language server left the program running; a lost connection to the debugger now ends the program at once and says so.
- A breakpoint set while the session was starting flashed “Empty debug session.” as invalid.
- Run to Cursor ran past a line that had a false conditional breakpoint or a logpoint.
- Every stop fetched the whole call stack (thousands of frames in deep recursion); it is now paged.
- Stop and Restart froze the window for up to a quarter of a second, and logged a “Socket closed” stack trace.
- Hover and inline values showed the wrong variable for
obj.field. - A compile error of a loose file showed only in the status bar; it is now in the Debug console with links.
- A slow evaluation timed out with a raw Java exception name, and a Step pressed meanwhile fired seconds later.
- Install Java Support downloaded java-debug again while debugging was off; with
--config-dirthe installed plugin was not found. - Restart of a run configuration used its old arguments; F5 in another tab stopped a running session without asking; Attach, configurations and Debug via Build of a remote file checked this machine’s tools instead of the host’s; remote launch arguments were quoted for this machine’s OS.
- java-debug’s “different versions of JVMs” warning no longer clutters the console, and a program java-debug started now ends with “The program ended.” instead of a made-up exit code 0.
- Debugger launch, connect and adapter errors were English in every language and could start with Java class
names (
org.eclipse.debug.core.DebugException: …); they are now translated and plain, and a report of several lines goes to the Debug console with its first line in the status bar. - With “Run the debugged program in the Debug console” off, the console now shows the program’s real exit code (Linux and macOS, programs on this machine); java-debug always reported 0.
- Emoji and other characters outside the Basic Multilingual Plane showed garbled in Java string values (a bug in Eclipse’s debugger inside jdtls); Variables, watches, hover and inline values now show them as written.
- A class with a
-
“Snippets: Manage”, “Sync setup” and the Doctor links opened an empty page when a search was left in the Settings search box.
-
What Settings search found depended on which pages you had opened before searching.
-
A change in another window wiped text you were typing in an open Settings window, and every reopen ran
git --version. -
Shortcut chips in Settings used the editor theme’s colours instead of the app theme’s.
-
A multi-line abbreviation was saved flattened when you clicked into it and out again. The expansion is now a multi-line field, and nothing is saved unless you change it.
-
With one saved Remote site, the first edit emptied and greyed out the form.
-
Escape in a macro’s Key step closed Settings instead of recording Escape.
-
Reset on a shortcut whose default chord another command took did nothing. It now offers to take the chord back.
-
A blank template Id discarded every other edit in the form.
-
Two macros could share a name, and a duplicate abbreviation key (ignoring case) overrode the other silently.
-
“Add pattern” on the TODO page matched every TODO a second time.
-
The TODO part-colour pickers showed old colours after Reset or a change made elsewhere.
-
Tool Windows ▲ / ▼ sometimes did nothing visible.
-
“Rulers by language” accepted names that never matched, and a mistyped ruler list was silently replaced.
-
“Enable plugins” left every plugin’s checkbox greyed until Reload.
-
A wrong git or gh path said “install git” and locked the Enable Git switch on.
-
Browse… beside the API key and model fields opened a file chooser.
-
A server, agent or debugger path with a space in it never started.
-
The AI status pill stayed “Connected” after turning AI off.
-
The Markdown page split the pasted-image rows, had a scroller inside the page, and a blank gap.
-
A broken plugin.json showed the parser’s internals; Browse plugins… hid Settings before the picker opened.
-
Java debug-adapter detection ran on the UI thread.
-
Remote: an SSH config with a
Matchsection no longer stops every connect. Editora skipsMatchsections (it cannot evaluate them) and reads the rest of the file; before, anyMatchmade every connect fail with “Currently not able to process Match sections”.