I have been a Neovim person for years, and before that a Vim person, and the whole time there has been a low hum of maintenance underneath the productivity. A config that needs pruning. A plugin that broke on an update. An afternoon lost to wiring up a language server that a different editor would have handed me for free. I love the result, but I have never loved the upkeep.
Helix is the editor that asked the obvious question: what if all of that was just built in? A month ago I made it my daily driver for a mix of Rust, Python, TypeScript, and the usual pile of config files. This is the honest report after living in it, not after a weekend of poking.
What Helix Is
Helix is a modal text editor written in Rust. On the surface it looks like a Vim competitor: it runs in the terminal, it is keyboard-driven, it has modes. But it does not try to be Vim. It borrows its editing model from Kakoune, an editor most people have never used, and that single decision shapes everything about how it feels.
The pitch is batteries included. Tree-sitter syntax highlighting, Language Server Protocol support, fuzzy file pickers, multiple cursors, and a discoverable command menu all ship in the box and all work the moment you install it. There is no plugin manager to configure because, as of today, there is no plugin system. That is either the best thing about Helix or the dealbreaker, depending entirely on who you are, and I will get to both.
The Selection-First Model Is the Whole Point
If you take one thing from this review, take this: Helix inverts the grammar of modal editing, and it is better than I expected.
In Vim, you type a verb and then an object. dw means delete a word. You commit to the action, then describe what it acts on, and you find out whether you got it right after it already happened. It works, and after years it is muscle memory, but it is fundamentally blind. You are trusting that d2w grabbed exactly what you meant.
Helix flips it. You select first, then act. You press w to select a word, the word lights up on screen, and then you press d to delete the thing you can already see is selected. The object comes first, the verb second, and crucially the selection is visible before you pull the trigger. Every edit is a two-step of “highlight what I mean, confirm it looks right, then do the thing.” After a week I stopped noticing the inversion and started noticing how often it saved me from an edit that would have been slightly wrong in Vim.
This model also makes multiple cursors feel native instead of bolted on. Select all occurrences of a symbol, and now every one has a cursor, and every subsequent keystroke happens at all of them at once. Neovim can do this with a plugin. Helix does it because the whole editor was designed around selections from the start, and it shows.
Everything Just Works, With No Config
The second headline is the one that actually made me switch: I did not write a config file for two weeks, and everything worked.
Language servers are the clearest example. In Neovim, getting full LSP, meaning diagnostics, go-to-definition, autocomplete, and rename, is a multi-plugin, multi-hour setup that you maintain forever. In Helix you install the language server binary, put it on your path, open a file, and it is all there. Diagnostics underline as you type. Go-to-definition jumps. Autocomplete pops. Rename-symbol works across the project. Zero lines of configuration.
The fuzzy pickers are the same story. space f opens a file picker with fuzzy matching. space b switches buffers. space s jumps to a symbol in the file, and the capital space S does it across the workspace. In another editor each of these is a plugin someone had to choose, install, and configure. In Helix they are just there, consistent, fast, and discoverable.
That discoverability deserves its own mention. Press the space key and a menu pops up showing you every command available and its key. Start a keybinding and Helix shows you the next valid keys with descriptions. You can genuinely learn this editor by using it, without a printed cheat sheet taped to your monitor, which is not something I can say about Vim.
The Rough Edges Are Real
Now the honest part, because this is a review and not an advertisement.
The biggest one is plugins, or the lack of them. As of the 25.07 release, the plugin system, built on a Scheme dialect called Steel, is still in development and not in the stable builds. What that means in practice is stark: if Helix does not ship a feature, you cannot add it. No file-tree sidebar plugin, no custom language integrations beyond what the core supports, no third-party workflow tools. The maintainers have made batteries-included work impressively well, but the day you need something they did not build, you hit a wall with no way over it. For a lot of Vim and Neovim refugees, the plugin ecosystem is the entire reason they stayed, and Helix cannot match that today.
The second edge is the learning curve, and specifically that it fights existing muscle memory. If you have never touched a modal editor, Helix is arguably easier to learn than Vim because of the discoverability. But if you have years of Vim in your fingers, the reversed grammar is actively disorienting for about a week. dw does not do what you expect. You will select and delete in the wrong order a hundred times before it rewires. It does rewire, but budget for the frustration.
Third, there is no AI or inline completion story. If you have come to rely on Copilot-style suggestions as you type, Helix does not have that built in and cannot bolt it on without the plugin system. For some people in 2026 that alone is disqualifying, and it is fair to name it.
Finally, small things. No file-tree sidebar by default, which disorients people coming from VS Code, though the fuzzy file picker genuinely replaces it once you trust it. These are papercuts, not dealbreakers, but they are real on day one.
The Config, When You Do Reach For One
Eventually I did write a config, and it is worth describing because it is the anti-Neovim experience. Helix configuration lives in a single small config.toml file, and the language configuration in a languages.toml. That is the whole surface. There is no plugin manager, no lockfile, no startup profiling to figure out which of forty plugins is costing you 200 milliseconds. My config is about fifteen lines: a theme, a couple of keybindings I remapped, and the editor options I care about like showing a ruler and enabling auto-format on save.
The languages.toml is where you tell Helix which language server to use for a given filetype and any per-language settings, like turning on format-on-save for Rust with rust-analyzer or pointing Python at the language server you prefer. It is declarative and boring in the best way. I set it once and have not thought about it since. Compare that to the living document that a Neovim config becomes, a thing you tend like a garden, and the appeal of Helix’s flat, finite config is obvious. You are not maintaining an editor. You are just using one, and occasionally nudging a setting.
Who Helix Is Actually For
After a month, I have a clear picture of the person Helix is perfect for and the person who should stay away.
Helix is ideal if you want a powerful modal editor without the maintenance tax, if you do a lot of remote work over SSH where a fast terminal editor with built-in LSP is a gift, and if you are either new to modal editing or willing to relearn the grammar. It is a spectacular default experience. Nothing else I have installed does this much with this little setup.
Helix is the wrong choice if your workflow is load-bearing on specific plugins, if you cannot live without inline AI completion, or if your Vim muscle memory is so deep that relearning it is not worth the payoff. None of those are knocks on the editor. They are just honest boundaries.
The Bottom Line
Helix is the most productive editor I have ever installed without configuring, full stop. The selection-first model is not a gimmick; it is a genuinely better way to edit that makes every command visible before it runs, and the built-in LSP and pickers deliver in minutes what other editors make you assemble over an afternoon. For a month it has made Neovim feel like a lot of upkeep for a result Helix hands me for free.
The plugin gap is the one thing standing between “great editor” and “the editor I recommend to everyone.” Until the Steel plugin system stabilizes, Helix asks you to live inside what the maintainers chose to build, and that box, while impressively large, has hard walls. Know what you need before you switch. If your needs fit inside the box, and mine mostly do, Helix is a joy. If they do not, you will feel the walls fast. Either way, it is free, it installs in seconds, and it is worth an afternoon of your time to find out which camp you are in.