#Install

#Package managers

#Go

go install github.com/giancarlosisasi/labdash/cmd/labdash@latest

The OAuth client id is a plain value in the source rather than a build-time flag, so a binary from go install logs in exactly like a released one.

#Downloaded binaries

Every release publishes archives for windows, darwin and linux × amd64 and arm64, built by goreleaser with CGO_ENABLED=0. Download the archive for your platform, unpack it, and put labdash on your PATH.

tar -xzf labdash_<version>_linux_amd64.tar.gz
chmod +x labdash
sudo mv labdash /usr/local/bin/

Each release also carries signed checksums and an SBOM, so a corporate build pipeline can verify what it installs.

#Linux packages

sudo dpkg -i labdash_<version>_linux_amd64.deb
sudo rpm -i  labdash_<version>_linux_amd64.rpm
sudo apk add --allow-untrusted labdash_<version>_linux_amd64.apk

#Docker

docker run --rm -it ghcr.io/giancarlosisasi/labdash:latest

The OAuth device flow needs no callback to localhost, so logging in works inside a container. That is why it is the default.

#Verifying the install

labdash --version

#Shell completions

labdash completion bash   > /etc/bash_completion.d/labdash
labdash completion zsh    > "${fpath[1]}/_labdash"
labdash completion fish   > ~/.config/fish/completions/labdash.fish
labdash completion powershell | Out-String | Invoke-Expression

#Man pages

The Homebrew formula and the deb, rpm and apk packages install man pages. man labdash covers the flags and every subcommand.

#Fonts

No patched font is required. labdash draws status with ordinary Unicode glyphs that a terminal font has carried for years, so there is nothing to install.

Every glyph is one cell and every ASCII replacement is one character, so a screen rendered either way has identical column boundaries. Force either mode in appearance settings:

theme:
  icons: ascii   # auto | unicode | ascii

auto reads your locale. On a CJK locale it chooses ascii, because a few of the glyphs are drawn two cells wide there and one cell everywhere else.

#Terminals

Windows Terminal and ConPTY are verified for resize, mouse, Unicode and key handling, because that is where labdash is developed. tmux, SSH, WSL, Ghostty, WezTerm, Alacritty, iTerm2 and the VS Code terminal each have a tested entry in terminal support.