The modal text editor battle in 2026
Helix reached 46,040 stars on GitHub in September 2026, signaling a shift toward zero-config tools with built-in tree-sitter integration. Teams choosing between Helix, Neovim, and Kakoune must weigh Helix's immediate functionality against Neovim's massive Lua-based plugin ecosystem.
The rise of zero-config tools
Helix reached 46,040 stars on GitHub in September 2026. This surge signals a shift toward editors that work immediately without massive configuration. Helix is written in Rust and rejects a plugin system. It includes language server client integration, tree-sitter highlighting, and a fuzzy file picker as built-in tools. Because Helix uses a selection-first model where users select text before applying an action, it provides immediate visual feedback that reduces the common problem of accidentally deleting the wrong text during a coding session. Developers often compare the Helix experience to the move from ESLint to Prettier. Neovim is the most-starred text editor on GitHub with 102,043 stars. Neovim is a hard fork of Vim that uses Lua for configuration.
Neovim has a massive plugin ecosystem with tools like Lazy.nvim, which has 26,300 stars. Users can shape Neovim into a full IDE using plugins for Git or AI assistants. Kakoune is the oldest of the three with 11,045 stars. It uses a Lisp-flavored DSL in kakrc for its configuration.
Comparing Neovim and Kakoune
Kakoune relies on a client-server architecture where a daemon runs the editing session. This model allows remote work to feel local because the server keeps the buffer state on the remote machine. You can attach or reattach to a session without losing work when an SSH connection fails. Kakoune also treats multi-selection as a first-class primitive. To delete every occurrence of a word, you select the word, press s to select all matches, and then press d.
Neovim is a tool that you can shape into anything. Its plugin ecosystem includes thousands of options. Neovim v0.12.2 was released on April 22, 2026. This version includes built-in autocomplete and tools like :Undotree and :DiffTool.
Technical trade-offs for teams
Teams must evaluate their specific workflows. Neovim requires manual LSP configuration via nvim-lspconfig or other plugins. Helix includes LSP support for 50+ languages out of the box. Helix also bakes tree-sitter into its core. Neovim needs the nvim-treesitter plugin for syntax highlighting. I would tell you to avoid Helix if you rely on specific plugins for Git blame or custom snippets that the binary does not include. Mac users might struggle with the heavy use of ALT keys in Helix. They must set the terminal to send the left ALT key as ESC+ to make it work.
| Feature | Helix | Neovim | Kakoune |
|---|---|---|---|
| GitHub Stars (2026) | 46,040 | 102,043 | 11,045 |
| Config Language | TOML | Lua | Lisp-flavored DSL |
| Plugin System | None | Massive | Minimal |
| Selection Model | Selection-first | Verb-object | Selection-first |
Helix 25.07.1 was released on July 18, 2025. Helix lacks persistent undo and does not auto-reload changed files. This is a major issue for developers who switch between their editor and the terminal. Neovim is the better choice if you have deep Vim muscle memory and do not want to spend two weeks relearning motion order. Will the Helix plugin PR change how teams view its limitations? If you already live in Neovim and feel no friction, you probably do not need to read this. I recommend Neovim for users who need stability and a deep plugin ecosystem.