CLI installation
The Tomba CLI, tomba, is a single binary for macOS, Linux, and Windows. After you install it, sign in as described in Authentication.
Install
Release builds are available for macOS (amd64, arm64), Linux (386, amd64, armv6, arm64, ppc64), and Windows (386, amd64, arm64).
Install script (macOS and Linux)
Code
The script downloads the latest release for your platform from GitHub Releases, checks its SHA-256 checksum, installs tomba to /usr/local/bin (with sudo if that directory isn't writable), and sets up completion for bash, zsh, or fish. If it can't download the checksum file or find sha256sum or shasum, it prints a warning and installs without checking; to check the archive yourself, see Verify the download.
To pin a version or install to another directory, pass --version or --dir:
Code
PowerShell (Windows)
Code
The script checks the SHA-256 checksum, installs tomba.exe to %LOCALAPPDATA%\tomba, adds that folder to your user PATH, and adds PowerShell completion to your profile.
Homebrew
Code
Scoop (Windows)
Code
Snap (Linux)
Code
Linux packages
Each release includes .deb, .rpm, .apk, and Arch Linux (.pkg.tar.zst) packages. For example, on Debian or Ubuntu:
Code
The packages depend on git and systemd and recommend golang; --no-install-recommends skips the Go toolchain. They install shell completion, a man page, and a systemd unit, tomba.service, which runs tomba serve as www-data and is enabled at boot. If you don't use the local server, disable the unit:
Code
Go
Requires Go 1.25 or later.
Code
The binary goes to $(go env GOPATH)/bin, which must be on your PATH. Builds from go install report their version as dev.
Verify the download
Every release publishes tomba_checksums.txt with the SHA-256 checksum of each archive and package. To install from an archive and check it first:
Code
On macOS, use shasum -a 256 --ignore-missing -c tomba_checksums.txt and the tomba_darwin_arm64 or tomba_darwin_amd64 archive. The check prints OK next to the archive name; any other result means the file doesn't match the release, so don't install it.
Verify the installation
Code
Code
tomba --version prints the version on one line (tomba version 1.2.3).
Shell completion
The install scripts, Homebrew, and the Linux packages set up completion for you. To load it yourself for the current session:
Code
Code
To load completion in every new session, follow the steps that tomba completion <shell> --help prints for your shell.
Update
Code
tomba update (alias upgrade) looks up the latest release on GitHub, downloads the archive for your platform, checks its SHA-256 checksum when the checksum file is available, and replaces the tomba binary in place. If the binary is in a directory you can't write to, the command fails with Cannot rename current binary (may need sudo); run it with sudo.
If you installed with a package manager, update with the same tool so it keeps track of the version:
| Installed with | Update with |
|---|---|
| Homebrew | brew upgrade --cask tomba |
| Scoop | scoop update tomba |
| Snap | sudo snap refresh tomba |
| Linux package | Download the new package and install it as above |
| Go | go install github.com/tomba-io/tomba@latest |
Uninstall
| Installed with | Remove with |
|---|---|
| Install script | sudo rm /usr/local/bin/tomba, or remove tomba from the directory you passed to --dir |
| PowerShell script | Delete %LOCALAPPDATA%\tomba, remove it from your user PATH, and remove the tomba.completion.ps1 line from your PowerShell profile |
| Homebrew | brew uninstall --cask tomba |
| Scoop | scoop uninstall tomba |
| Snap | sudo snap remove tomba |
| Debian or Ubuntu package | sudo apt remove tomba |
| RPM package | sudo dnf remove tomba |
| Alpine package | sudo apk del tomba |
| Arch Linux package | sudo pacman -R tomba |
| Go | rm "$(go env GOPATH)/bin/tomba" |
The CLI keeps saved credentials in ~/.tomba.json and custom skills in ~/.tomba/skills/. Removing the binary leaves them in place; delete them with:
Code