Yazelix Nova Beta

Yazelix Nova is a Nix-packaged terminal workspace built around Mars (a Rio-derived fork), a thin Yazelix-owned Zellij fork, Yazi, Nushell (with packaged Bash, Zsh, and Fish alternatives), a lazygit popup (but you can configure other git clients!), and an optional coding agent popup. It uses the Yazelix Helix fork by default (but editor.command can select your preferred terminal editor). yzx launch opens the desktop workspace through Mars, while yzx enter will open Yazelix in any capable terminal emulator (Mars provides tighter Yazelix integration, though) or over SSH. Great defaults out of the box!

Preview

Nova vs Classic

Classic was bloated and built on the wrong ownership model. Its main repository acted as the product runtime, component control plane, configuration repair system, compatibility layer, and maintainer toolbox.

Classic's child repositories did not create firm boundaries. The main repo still carried their maintenance machinery and overlapping runtime logic. Nova gives first-party Yazelix components firm package boundaries. Each component owns its implementation and contract. Nova pins and composes their package outputs.

Measure	Nova	Classic
Code and configuration (Rust, Nix, shell, TOML, etc.)	18,197 LOC	91,545 LOC
Rust	15,215 LOC	80,957 LOC
Ownership model	One owner per concern	Overlapping responsibilities across layers
Yazelix component boundaries	Independent, versioned packages	Child repos mixed with main-repo ownership
Product experience	More features, stronger defaults, tighter integration, and polished UX	Fewer features and a less cohesive workspace
Status	Recommended	Frozen migration and rollback path

Nova owns 73,348 fewer lines, an 80% reduction. Classic's Rust code alone is 4.4 times larger than Nova's entire code and configuration surface.

Nova delivers more features in 20% of the code. It has a clearer configuration model, tighter editor and Yazi integration, stronger diagnostics, and a coherent popup-oriented interface. The smaller architecture makes Yazelix easier to improve and better to use.

Classic proved the idea. Nova is the better product and the architecture Yazelix should have had from the start.

Install and launch

Yazelix requires Nix with flakes enabled. launch opens the packaged Mars window in a graphical session, while enter starts the same workspace in the current terminal or over SSH.

The stable branch advances from a checked and dogfooded main revision at most once per week. Use main for more constant updates or an immutable nova-v* tag for an exact release.

Linux is the dogfooded platform. CI builds all packages and a Home Manager activation on aarch64-darwin, while interactive macOS use and the Mars GUI remain unverified.

Try without installing

nix run github:luccahuguet/yazelix/stable -- launch
nix run github:luccahuguet/yazelix/stable#yazelix-no-mars -- enter

If the one-off launch fails, inspect the owned runtime setup with:

nix run github:luccahuguet/yazelix/stable -- doctor

Install in a Nix profile

nix profile add --refresh github:luccahuguet/yazelix/stable
yzx launch

Install with Home Manager

Use the Home Manager module for a declarative install.

Moving from Yazelix Classic

Classic v17.12 translates mutable Classic settings.jsonc or config.toml files into Nova configuration. It does not rewrite Home Manager declarations or Home Manager-owned files. Run the bridge once when you need to preserve mutable Classic settings:

nix run github:luccahuguet/yazelix/v17.12#yazelix -- launch

If your Classic settings match packaged defaults, start with Nova's packaged defaults and move straight to stable. Home Manager users must replace Classic-only options with Nova's narrow module surface before switching.

The Nova cutover intentionally replaces the old main history. Existing Git clones should be replaced with a fresh clone rather than updated with an ordinary pull. Classic remains available at the frozen classic branch, while the immutable v17.12 tag remains the migration and rollback bridge.

First five minutes

Start the guided tour after launching Yazelix:

yzx tutor begin

yzx help lists every command. yzx doctor checks the owned runtime setup without opening Mars or Zellij. Inside Yazelix, press Alt Shift M to open the command palette, which includes both help and tutor entries.

Ratconfig

Press Alt Shift K to open Ratconfig:

Key	Action
1-9	Jump to a tab
Tab / Shift-Tab, h / l	Change tabs
j / k, /	Move through rows or search All settings
a	Switch between Core and All
e, Enter, Space	Run the selected row's contextual action
u, q	Reset the selected setting or quit

The footer lists the selected row's controls.

Workspace keys

Yazelix extends Helix/Vim's h/j/k/l motion model into a workspace key grid. The Alt and Ctrl Alt layers move focus, tabs, or panes, while Alt Shift groups four workspace surfaces:

Layer	h	j	k	l
Alt	Focus left or previous tab	Focus down	Focus up	Focus right or next tab
Ctrl Alt	Move tab left	Move pane down	Move pane up	Move tab right
Alt Shift	Sidebar	Git	Ratconfig	Agent

Yazi and the menu use their initials:

• Alt Shift Y toggles the full Yazi popup.
• Alt Shift M toggles the command menu.

Press a popup's key again to close or hide it. Other useful bindings are:

Scope	Key	Action
Workspace	Ctrl q	Quit the Yazelix session
Workspace	Alt m	Open a new pane
Workspace	Alt Shift F	Toggle the focused pane fullscreen
Workspace	Ctrl y	Toggle focus between the editor and Yazi sidebar
Workspace	Alt 1-9	Go directly to tab 1-9
Editor	Alt r	Reveal the current editor file in Yazi
Yazi	Alt z	Retarget the tab workspace with zoxide

Managed Helix supplies the editor binding. Terminal editors can bind the same yzx reveal command; see Configuration for Neovim and terminal Emacs examples.

Ratconfig's Keys tab is the complete packaged reference, and defaults/zellij/config.kdl remains the runtime source.

Commands

Command	Purpose
yzx, yzx help	Print command help
yzx --version	Print the exact package-owned Yazelix version
yzx launch [zellij-args...]	Open Mars first, then start managed Zellij
yzx enter [zellij-args...]	Start managed Zellij in the current terminal
yzx run <program> [args...]	Run exact argv inside the prepared Yazelix environment
yzx config	Open the Ratconfig-backed config UI
yzx menu	Open the command palette
yzx doctor	Check owned runtime setup without launching Mars or Zellij
yzx status	Print config/runtime paths and selected settings
yzx status --json	Print the versioned machine-readable status record
yzx env	Open the managed shell without launching the UI
yzx tutor [lesson]	Print guided Yazelix lessons
yzx screen [style]	Show a terminal welcome screen
yzx reveal <target>	Reveal a file or directory in the managed Yazi sidebar

Packages and platforms

Package names follow yazelix[-no-mars][-no-helix][-no-yazi]. Each suffix removes that managed package while retaining the integration around it. no-helix uses the configured host editor; no-yazi requires matching host yazi and ya commands.

Package	Mars	Managed Helix	Managed Yazi
yazelix	Yes	Yes	Yes
yazelix-no-helix	Yes	No	Yes
yazelix-no-yazi	Yes	Yes	No
yazelix-no-helix-no-yazi	Yes	No	No
yazelix-no-mars	No	Yes	Yes
yazelix-no-mars-no-helix	No	No	Yes
yazelix-no-mars-no-yazi	No	Yes	No
yazelix-no-mars-no-helix-no-yazi	No	No	No

See Installation and packages for package variants, platform support, SSH use, measured sizes, Home Manager, and updates.

First-party components

Yazelix assembles focused first-party forks, plugins, libraries, and commands:

Component	Yazelix role
Mars	GUI terminal used by yzx launch, with Kitty graphics, cursor shaders, and Yazelix session integration
Yazelix Zellij	Multiplexer fork with Kitty graphics passthrough for the workspace
Yazelix Helix	Steel-enabled editor fork with isolated configuration and explicit workspace bridge hooks
Yazelix Zellij Pane Orchestrator	Zellij plugin that owns tab-local workspace roots and coordinates panes, focus, popups, the editor, and agent activity
Yazelix Zellij Popup	Zellij plugin that opens, focuses, hides, and closes configured floating TUI panes
Yazelix Zellij Bar	Zellij plugin package for the compact top bar, tabs, modes, session details, and status widgets
Ratconfig	Reusable Ratatui configuration editor and TOML patching and migration library
Yazelix Screen	Terminal welcome animations exposed through yzx screen
Yazelix Cursors	Shared cursor presets and validation for Ratconfig, plus palettes and shader assets for Mars
auto-layout.yazi	Yazi plugin that changes the column layout to match the available pane width
zjstatus	Fork that gives the bar activity-aware tab markers without changing native Zellij tab names

Configuration

yzx config opens Ratconfig over the managed tree at ~/.config/yazelix/. Yazelix inherits packaged defaults and persists only explicit overrides. Core shows the settings most users need. All includes the complete inventory.

Set shell.program in Ratconfig or config.toml to choose packaged Nushell (default), Bash, Zsh, or Fish for new panes and sessions. Yazelix initializes Starship, Carapace completions, and zoxide for managed Nushell. Bash, Zsh, and Fish use their normal interactive startup files.

See Configuration for settings, popups, native files, Yazi plugins, cursor ownership, and editor behavior.

Development

From a local checkout, use:

nix run .#yazelix -- launch
nix run .#yazelix-no-mars -- enter

See Development for CI and local checks, Architecture for ownership boundaries, and Runtime Notes for launch and integration contracts.

LOC Scorecard

Yazelix owns 20,543 lines of tracked text project files. The reproducible scorecard excludes Beads, lockfiles, and binary assets.