Installing the CLI

The slasha binary serves a dual purpose: run slasha serve on your server to start the platform, or use all other subcommands as a client that talks to a remote Slasha instance over HTTP. You only need one binary on both machines.

Recommended: install script

The official install script detects your OS and architecture, fetches the latest release from GitHub, verifies the SHA256 checksum, and installs the binary to ~/.local/bin:

curl -fsSL https://slasha.com/install.sh | bash

Supported platforms: Linux (x86_64 and ARM64) and macOS (Intel and Apple Silicon). Running it again on an existing install upgrades it; if the installed version already matches the latest, it exits without re-downloading.

Environment overrides

# install a specific version
SLASHA_VERSION=v0.0.0 curl -fsSL https://slasha.com/install.sh | bash

# install to a different directory
SLASHA_INSTALL_DIR=/usr/local/bin curl -fsSL https://slasha.com/install.sh | bash

Variable	Description
SLASHA_VERSION	Install a specific release tag instead of the latest (default: latest)
SLASHA_INSTALL_DIR	Destination directory for the binary (default: ~/.local/bin)

GitHub Releases

Every version tag produces pre-compiled binaries for Linux and macOS on both x86_64 and ARM64. Browse and download any release directly from the Releases page. Each release ships a SHA256SUMS file for checksum verification.

Cargo

Install from crates.io

# full binary 
cargo install slasha

# CLI only — no server, no embedded frontend, portable binary
cargo install slasha --no-default-features --features vendored

Build from source

git clone https://github.com/slashacom/slasha.git
cd slasha
cargo build --release -p slasha-cli

You can manually also select the features you want while building.

Verifying the install

# print version
slasha version

# print detailed build information
slasha version --verbose

# print diagnostic information for bug reports
slasha --diagnostic

Authentication token for CI

By default, slasha login stores your auth token in the system keychain. In CI environments where there is no keychain, set the SLASHA_TOKEN environment variable instead. The CLI reads it automatically and skips the keychain entirely.

SLASHA_TOKEN=your-token slasha list

Global config file

The CLI stores the server URL and other settings in a global config file. Its location follows the OS default:

OS	Path
Linux	~/.config/slasha/config.toml
macOS	~/Library/Application Support/slasha/config.toml
Windows	%APPDATA%\slasha\config.toml

You can override the server URL for any single command with the --url flag rather than changing the config file. See the CLI Overview for full details.