Start here

Installation

Install lla with the script, a package manager or a release download, then set it up and keep it current.

↓ on this page

The install script is the shortest route on Linux, macOS and NetBSD:

curl -sSL https://raw.githubusercontent.com/chaqchase/lla/main/install.sh | bash

It detects your system, downloads the matching release, checks it against the release's SHA256SUMS file and installs it to /usr/local/bin.

On Windows, use PowerShell:

irm https://raw.githubusercontent.com/chaqchase/lla/main/install.ps1 | iex

This installs to %LOCALAPPDATA%\Programs\lla and adds that directory to your user PATH. To use its -Version, -InstallDir or -NoPathUpdate options, download install.ps1 first and run it from there.

Package managers

PlatformCommand
Cargocargo install lla
Homebrewbrew install lla
Arch Linux (paru)paru -S lla
NetBSD (pkgin)pkgin install lla
X-CMDx install lla

Download a release

Pick the asset for your system from GitHub Releases, then put it on your PATH:

wget -c https://github.com/chaqchase/lla/releases/download/<version>/<asset> -O lla
chmod +x lla
sudo mv lla /usr/local/bin/lla

Set it up

lla works as soon as it's installed. To choose your defaults, run the setup wizard:

lla init

It asks about appearance, the default view, permission format, sorting, dotfiles and .gitignore handling, long-view columns, plugins and recursion limits, and writes the result to ~/.config/lla/config.toml.

To write the defaults without any prompts, run lla init --default. Configuration covers every setting.

Plugins and extra themes are separate downloads:

lla install --prebuilt   # the 37 official plugins
lla theme pull           # the 23 official themes

Upgrade

lla upgrade
lla upgrade --version v0.5.1
lla upgrade --path /usr/local/bin/lla

lla upgrade checks the download against SHA256SUMS, then replaces the running executable, or the file at --path if you set one.

Platform notes

BuildAssetsWhat to know
Linux (GNU)amd64, arm64, i686The 32-bit x86 .apk is a GNU-based legacy package.
Linux (musl)lla-linux-amd64-musl, lla-linux-arm64-muslStatic builds. Listing, search, archives, themes and upgrades all work, but dynamically loaded plugins don't. The install script chooses these on musl systems.
NetBSDlla-netbsd-amd64Native plugins work, but WebAssembly plugins don't, because Wasmtime doesn't support NetBSD. There are no prebuilt plugin archives, so build plugins from source.
Windowslla-windows-amd64.exe, lla-windows-arm64.exeNeeds Windows 10, Windows Server 2016 or later. 32-bit x86 isn't supported.

Windows has no Unix ownership, inodes, hard-link counts, extended attributes or mount data, so those columns show - and those JSON fields are null. The permissions column is derived from the file type and the read-only attribute. Creating symlinks may need Developer Mode or an elevated terminal, but listing existing ones works normally.

Next steps