Zellij 0.44.0 Adds Windows, Remote Sessions

Zellij 0.44.0 lands with a feature set that changes how terminal power users will think about sessions. The biggest headline is native Windows support, which means Windows users no longer need WSL to run the Rust-written terminal multiplexer.

That matters because Zellij has been quietly building a serious workflow layer around terminals: session management, plugins, multiplayer collaboration, and now remote attach over HTTPS from the terminal itself. This release also deepens CLI automation and gives plugin authors much more control over what happens inside a pane.

Native Windows support finally lands

Zellij maintainer Aram Drevekenin announced the release on March 23, and the Windows work came from a community contribution by developer divens. Drevekenin thanked them directly in the release note, which is a good sign for a project that has leaned heavily on community input from the start.

For Windows users, this is more than a checkbox feature. Before 0.44.0, Zellij was mainly a Linux and macOS tool unless you were willing to run it through WSL. Native support now brings the same core workflow to Windows terminals without that extra layer.

• Native Windows build, no WSL required
• Session management works the same way as on Linux and macOS
• Workspace automation and plugin support are included
• Multiplayer features are available on Windows too

The practical effect is simple: Zellij is no longer a tool you recommend with a caveat for Windows users. That alone widens the audience a lot, especially for developers who split time between corporate Windows laptops and Linux servers.

Remote sessions now work from terminal to terminal

The other big addition builds on the built-in web server introduced in version 0.43.0. In 0.44.0, that server powers HTTPS attach from one terminal to another, so a user can run zellij attach and connect to a remote session without opening a browser.

The built-in web client handles authentication against the Zellij web server, which means the terminal client behaves like the browser client would. That is a smart design choice because it keeps the remote workflow consistent whether you are attaching from a local shell, a jump box, or a remote workstation.

“Special thanks to divens for the implementation and hard work.” — Aram Drevekenin, Zellij release note

Zellij also adds read-only session sharing through read-only tokens. That is useful for pair debugging, demos, or letting someone inspect a live session without giving them full control. It is a smaller feature on paper, but it removes a lot of friction in real collaboration.

Compared with older terminal-sharing setups, Zellij is trying to make the experience feel first-class instead of bolted on. You are not stitching together screen sharing, browser tabs, and ad hoc SSH tricks. You are attaching directly to a session that already knows how to present itself securely.

Plugin APIs get much more expressive

This release is also a big one for plugin authors. Zellij’s new Rust plugin APIs can read a pane’s viewport and scrollback either on demand or as a live subscription. That means plugins can react to what is visible in the terminal instead of guessing from raw output.

Plugins can now highlight text on mouse hover, receive events when a user Alt-clicks highlighted text, change pane foreground and background colors, and render in a borderless mode that removes visible pane boundaries. In practice, that opens the door to terminal UIs that feel much closer to integrated apps than simple text add-ons.

• Viewport and scrollback access on demand or as a live subscription
• Hover highlighting and Alt-click event hooks
• Pane color control for foreground and background
• Borderless rendering for deeper visual integration

One Reddit user described the sort of workflows these APIs could enable: selecting git status output with the mouse before staging changes, handling compiler errors with custom interactions, or clicking IP addresses and hostnames to open SSH connections. That is exactly the kind of practical automation that makes terminal tools sticky.

If you want a sense of where this is headed, compare Zellij with older terminal multiplexers such as GNU Screen and tmux. Those tools are powerful, but their extension stories are much narrower. Zellij is pushing toward a terminal that can expose state to plugins in a more structured way.

Session management gets simpler, and automation gets better

Zellij 0.44.0 also revisits the everyday stuff that people touch constantly. The session manager now gives you one screen for creating, attaching to, and resurrecting sessions, with fuzzy finding across the same namespace. You can open it with Ctrl o + w, or start Zellij directly into the welcome screen with zellij -l welcome.

That kind of polish matters because terminal multiplexers live or die on small workflow details. If session switching takes too many commands, people stop using the feature. If the session picker is easy to reach, they start treating sessions like workspace tabs instead of hidden infrastructure.

• Single session manager screen for create, attach, and resurrect
• Fuzzy search across all sessions in one namespace
• Mouse-based pane resizing
• Click-to-open file paths
• Expanded CLI automation for scripts

The release also includes what Drevekenin called an infrastructure overhaul, which usually means the sort of internal work users feel indirectly through fewer rough edges and better behavior under load. It is the kind of release that combines visible features with plumbing changes that make future work easier.

For developers who use terminals all day, the comparison is straightforward. WezTerm is strong on terminal emulation and GPU rendering, while tmux remains the default for many server workflows. Zellij is carving out its own space by mixing multiplexing, collaboration, and plugin-driven interaction in one package.

What this release says about Zellij’s direction

Zellij 0.44.0 is a sign that the project is moving from “nice terminal multiplexer” toward “terminal workspace platform.” Native Windows support removes a major adoption barrier. Remote attach over HTTPS makes collaboration easier. The plugin APIs make the terminal more interactive without forcing users into a browser.

If you maintain developer tooling, the lesson is pretty clear: the next wave of terminal adoption will come from tools that treat sessions, collaboration, and automation as one system. Zellij is making that case with concrete features rather than marketing.

My guess is that the next release cycle will focus on plugin ecosystems, remote workflow polish, and more Windows bug fixing as real users start pushing the new build. If you already use tmux or Screen, this is a good time to test Zellij on your main machine and see whether its session model fits your day-to-day work better.

For readers following Rust tooling more broadly, this release also fits the trend covered in our recent rust-analyzer changelog coverage: Rust projects are getting more ambitious about developer experience, not just performance. The question now is whether Zellij can turn this feature burst into a habit-forming workflow for more than just early adopters.