Hexal brings Lua plugins to a modal editor with full Helix feature parity

A new modal editor targets Helix's missing plugin story

A developer has announced Hexal, a modal text editor that claims complete feature parity with Helix while adding something Helix has never offered: a plugin system based on Lua. In a post on dev.to, the author positions the project as a direct answer to what many users consider Helix's main limitation.

What Hexal promises

According to the dev.to announcement, Hexal matches Helix's feature set one for one and extends it with Lua scripting, so users can write their own plugins rather than waiting on upstream changes. The scripting layer runs on NLua, a binding that brings Lua into the .NET world, and it is the only meaningful dependency in an otherwise deliberately bare architecture.

Why it exists

The developer's stated motivation is frustration with Helix's direction on extensibility. In their view, the Helix project appears uninterested in building a plugin system, which caps what the editor can do and leaves a number of useful capabilities unimplemented. Rather than lobby for change, the author chose to build a compatible alternative with scripting at its core from the start.

From C++ prototypes to self-contained C# builds

The current design was not the first attempt. The post describes early prototypes written in C++ and in C# using the Terminal.Gui toolkit, before the author settled on the present approach: C# intended to be compiled ahead of time, with no dependencies beyond NLua.

There is a practical caveat. The builds distributed today are not actually AOT-compiled. They ship as self-contained packages that bundle the .NET 9.0 runtime, and the author notes that getting everything working under full ahead-of-time compilation is still unfinished work.

Why it matters

Modal editing has spent years consolidating around two poles. Vim and its descendant Neovim offer unmatched extensibility — Neovim's Lua runtime in particular turned the editor into a platform with a vast plugin ecosystem — while Helix won users over with a polished out-of-the-box experience: tree-sitter-driven syntax awareness, built-in language server support and a selection-first editing model that needs little configuration. What Helix has never provided is an escape hatch for the features it does not ship, and that trade-off has largely defined the choice between the two camps.

Hexal is an attempt to collapse that trade-off: keep the Helix experience users already like, then hand them a scripting runtime to fill the gaps themselves. If the parity claim holds up in daily use, the project becomes a serious option for people who left Helix precisely because they hit its extensibility ceiling.

There are caveats worth stating plainly. The parity and extensibility claims come from a single announcement post by the project's author, not from independent testing, and the project's own description shows it is still young — even the headline technical goal of AOT compilation is not finished. Anyone evaluating it now should treat Hexal as a promising start rather than a battle-tested tool. Still, the underlying bet is sound: the Neovim ecosystem demonstrates how much value a Lua runtime can unlock, and Helix users have wanted exactly that capability for a long time.