Helix
Helix 25.07.1 is a terminal modal code editor with multi-cursor selections, Tree-sitter syntax processing and an integrated LSP client for keyboard-driven editing.
The Helix editing model
Helix runs in a terminal and uses a selection-first modal workflow. Multiple selections, Tree-sitter syntax and text objects are integrated with an LSP client for diagnostics, navigation, completion and formatting. Users coming from mouse-first or insert-first editors should practice movement, selection, modification, undo and save before opening a critical source tree.
The runtime directory is part of the package
The Windows prebuilt archive contains both the hx executable and a runtime directory with language queries and other resources. Copying only the executable can remove highlighting or language features. hx --health shows the path actually discovered; HELIX_RUNTIME can point to a deliberate location when the default search path is unsuitable.
External language servers and project configuration
Helix ships an LSP client and default language configuration, but language-server binaries generally need separate installation and a command available on PATH. User config.toml, languages.toml and project .helix files can change formatters, commands and root detection, so review unfamiliar commands before allowing them to run.
Review date: 2026-08-06.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Helix to this cloud drive
Baidu Netdisk
Save Helix to this cloud drive
Helix Windows installation and first-edit guide
Keep the Windows `hx` executable together with its runtime directory, verify editor health, practice modal editing in a disposable project and install language servers only for the languages you use.
Before you start
- Prepare a Windows environment with a terminal that renders the editor correctly, and know how to inspect and edit the user `PATH` in PowerShell.
- Use a disposable sample project for learning modal commands instead of the only copy of a source tree.
- Identify the language server needed for each target language before expecting completion, diagnostics or navigation.
Installation steps
- 01
Extract the complete archive
Extract the `hx` executable and `runtime` directory together into a fixed location; do not move only `hx.exe` and discard the remaining files.
- 02
Configure the command and runtime
Add the Helix directory to the user PATH, and set `HELIX_RUNTIME` to the correct directory when the runtime is outside the normal search locations.
- 03
Run the health check
Execute `hx --health`, confirm that the runtime is readable and inspect syntax, queries and language-server status for the languages you plan to edit.
Quick start
- 01
Open a test project
Start Helix from the project root and open a sample file, then practice normal mode, insert mode, movement, selection, undo, save and exit.
- 02
Practice selection-first editing
Select a word, line or multiple matches before changing or deleting them, and check that every selection covers only the intended range.
- 03
Enable language features
Install the target language server separately, put its command on PATH, rerun `hx --health` and then test diagnostics, navigation and completion.
Usage tips
- Back up `config.toml` and `languages.toml`, but start an upgrade with a minimal configuration to isolate compatibility changes.
- Project `.helix` settings can merge with user and built-in language settings. Review commands in an unfamiliar repository before opening or formatting files.
- Automatic formatting can rewrite a whole file, so inspect the version-control diff the first time it is enabled.
Troubleshooting and uninstall
Why does hx --health report an incomplete runtime?
Confirm that the archive's runtime directory was not moved or omitted, inspect the discovered path and set HELIX_RUNTIME before reopening the terminal when needed.
Why is highlighting available but completion and diagnostics missing?
Tree-sitter highlighting and LSP are separate features. Check that the language server is installed and on PATH, and review its name and project-root rules in languages.toml.
- Remove program, runtime and configurationDelete the Helix directory from PATH and HELIX_RUNTIME, remove `hx` and `runtime`, and clear user settings that are no longer needed; language servers are removed separately.
Frequently asked questions
Why does Helix show no highlighting after extraction?
The prebuilt package needs its `runtime` directory as well as the executable. Keep both together or set HELIX_RUNTIME to a readable location, then use hx --health to confirm the path.
Does Helix include every language server?
No. It provides an LSP client and language configuration, while most language-server binaries are installed separately and must be available on PATH. hx --health reports missing components.
How is Helix different from a conventional text editor?
It is modal and selection-first: select an object before applying an action, with multiple selections as a core workflow. Practice the movement, selection, change, undo and save commands before daily use.