evil-helix is a soft fork of the Helix editor, written in Rust, that adds Vim keybindings and configurable built-in features for developers who want a more Vim-like experience within the Helix ecosystem.

What it is

evil-helix is a soft fork of Helix, the terminal-based code editor, and is written in Rust under the MPL-2.0 licence. It lives in the Helix ecosystem and remains compatible with upstream by regularly rebasing its changes onto the upstream master branch. The project describes itself as bringing Helix "to the evil side" by introducing Vim keybindings and more, while implementing added functionality as configurable parts of the editor rather than as plugins.

The concrete problem it solves is the gap between Helix's core editing model and the Vim keybindings many developers expect. It adds Vim commands such as "a", "c", "d", "y", and "x"; the "i" modifier; motions including "w", "W", "e", "E", "b", "B", "0", and "$"; and visual line mode through "V". It also renames Helix's "SEL" mode to "VIS", disables smart tab by default, and adds basic Vim modeline support. For users who would otherwise choose Vim or Neovim solely for those bindings, or who do not want to wait for upstream Helix's future Scheme-based plugin system, evil-helix replaces the upstream Helix build with a Vim-oriented alternative that keeps the soft-fork relationship.

Key capabilities

• evil-helix provides Vim keybindings for the commands "a", "c", "d", "y", and "x", plus the "i" modifier and the motions "w", "W", "e", "E", "b", "B", "0", and "$".
• It supports visual line mode via "V" and renames Helix's "SEL" mode to "VIS".
• It adds basic Vim modeline support.
• The "editor.evil" option is true by default and can be set to false in TOML under the [editor] table to deactivate evil-helix behavior without using a different build.
• It offers opt-in colored or rainbow indentation guides, and it colors the statusline file type when "color_modes" is enabled.
• It adjusts defaults such as disabling smart tab by default and uses a minimalistic window separator.
• Its soft-fork architecture regularly rebases on upstream Helix master and isolates features to avoid conflicts.

Who uses it and how

• Developers installing a release archive on Linux extract it in /opt and symlink /opt/helix/hx into /usr/local/bin.
• Users on systems where a package is available can follow the README's preferred method and install through the system package manager.
• Helix users who want Vim commands, motions, and visual line mode can adopt it without switching to Vim or Neovim.
• Developers who prefer configuration in Rust, TOML, or Lua can use it without having Scheme or Lisp forced onto them.
• Users who want functionality implemented directly in the editor as configurable features can avoid plugins that add performance costs and compatibility risks.

Getting started

Download a package from the releases page and extract it in /opt, then symlink the hx binary into /usr/local/bin; if a package is available for the system's package manager, the README recommends that method instead.

How it compares

Within this registry, evil-helix sits alongside Helix, Vim, and Neovim in its topic list, but it is a soft fork of Helix rather than a separate editor lineage. Compared with upstream Helix, it implements Vim keybindings and other features directly in the editor as configurable options, while upstream limits its scope to core functionality and defers further work to a future Scheme-based plugin system.

When to use it — and when not to

Choose evil-helix if you want Helix's core editor with Vim keybindings and built-in configurable features, particularly if you prefer Rust, TOML, or Lua over Scheme or Lisp. When no package is available, expect to install manually by extracting into /opt and symlinking into /usr/local/bin, and note that releases are tagged on-demand rather than on a fixed cadence. It is not the right choice if you want to stay strictly with upstream Helix's feature scope or its planned Scheme-based plugin system; setting editor.evil to false disables the Vim behavior, but the fork's added defaults and features still distinguish it from upstream.

cd /opt
sudo curl -Lo helix.tar.gz https://github.com/usagi-flow/evil-helix/releases/download/release-<VERSION>/evil-helix-<ARCH>-<OS>.tar.gz
sudo tar -xf helix.tar.gz
cd /usr/local/bin
sudo ln -sv /opt/helix/hx .

[editor]
evil = true # Default; set this to `false` to disable evil-helix behavior