xplr: A Hackable TUI File Explorer

What is xplr?

xplr is a terminal UI (TUI) file explorer written in Rust, described by its own repository as hackable, minimal, and fast. Rather than standing in for your shell or a GUI file manager, it gives you a keyboard-controlled, real-time visual screen built to sit in front of other command-line utilities that touch the filesystem. The actual file work gets handed off to whatever tools you wire in.

Core Features and Design Principles

• ✓Positions itself as an orchestrator, not a shell replacement: the README is explicit that xplr hands work off to other filesystem-facing CLI tools instead of reimplementing them.
• ✓Runs a keyboard-controlled, real-time visual screen rather than a static file listing, per the project's own framing.
• ✓Ships a dedicated layouts page (xplr.dev/en/layouts) for arranging the interface beyond one fixed panel.
• ✓Documents key-binding configuration on its own page (xplr.dev/en/configure-key-bindings), separate from general docs.
• ✓Has distinct Hacks and Plugins sections in its documentation nav, matching the 'hackable' label in its GitHub description.
• ✓Links to an integrations guide (xplr.dev/en/awesome-integrations) for wiring xplr into tools beyond the defaults.
• ✓Built in Rust and distributed under the MIT license.

Who is xplr for?

xplr fits developers and sysadmins who already spend most of their day in a terminal and want a keyboard-driven front end for the CLI tools they already use, rather than a from-scratch file manager. It's also a reasonable pick if you work over WSL or on a Raspberry Pi, since both show up in the project's own topic tags. Skip it if you want something productive the moment you install it, without reading the layouts, key-binding, or plugin docs first.

Getting Started with xplr

The facts available here don't include actual install commands; the project's own navigation just points to a separate Install page rather than listing steps in the README body, so treat exact install steps as not clearly documented from this source. What is documented: xplr ships as a Rust project, carries topic tags for use over WSL and on Raspberry Pi, and directs package maintainers to a RELEASE.md file for packaging guidance.

Navigating and Orchestrating Files

Day-to-day usage isn't spelled out in the README excerpt either; it defers to a documentation site instead of walking through keystrokes inline, so specific commands are not clearly documented from what's provided. The model the README does establish is this: you work from a real-time, keyboard-controlled screen, and that screen is meant to call out to other command-line utilities rather than reimplement file operations itself. Layouts and key bindings live on their own doc pages if you want to change how the screen behaves.

Other Terminal File Managers

Frequently Asked Questions

The problem it solves

Terminal users tend to pile up separate command-line tools for file work: an archiver here, a fuzzy finder there, each with its own syntax and none of them sharing a screen. xplr's README frames the project's reason for existing around exactly that gap. It isn't pitched as another shell replacement or another GUI file manager; it's pitched as the keyboard-driven front end that ties those existing tools together into one visual interface.

Best use cases

• •Driving a set of existing CLI utilities, like archivers, previewers, or search tools, from one keyboard-controlled screen instead of memorizing each tool's own invocation.
• •Building a custom layout or key-binding scheme for a specific workflow, using the dedicated layouts and key-binding docs instead of the defaults.
• •Running on a Raspberry Pi setup, since the GitHub repo carries a 'raspberry-pi' topic tag alongside 'terminal' and 'rust'.
• •Working over WSL, per the 'wsl' topic tag on the repository.
• •Vim users who want navigation habits that carry over from other vim-flavored tools, given the 'vim' topic tag.

Related repositories