brew install tigrisdata/tap/tigrisbrew uninstall tigrisRequires Node.js 18+.
npm install -g @tigrisdata/clinpm uninstall -g @tigrisdata/cliNo dependencies required. Downloads a self-contained executable.
curl -fsSL https://github.com/tigrisdata/cli/releases/latest/download/install.sh | sh| Environment Variable | Description |
|---|---|
TIGRIS_VERSION |
Install a specific version (e.g., v2.9.0) |
TIGRIS_INSTALL_DIR |
Custom install directory (default: /usr/local/bin) |
Example:
TIGRIS_VERSION=v2.9.0 curl -fsSL https://github.com/tigrisdata/cli/releases/latest/download/install.sh | shRemove the binaries from the install directory:
sudo rm /usr/local/bin/tigris /usr/local/bin/t3If you used a custom TIGRIS_INSTALL_DIR, remove from that directory instead and clean up the PATH entry from your shell config (~/.zshrc, ~/.bashrc, etc.).
irm https://github.com/tigrisdata/cli/releases/latest/download/install.ps1 | iex| Environment Variable | Description |
|---|---|
TIGRIS_VERSION |
Install a specific version (e.g., v2.9.0) |
TIGRIS_INSTALL_DIR |
Custom install directory (default: ~\.tigris\bin) |
Example:
$env:TIGRIS_VERSION = "v2.9.0"; irm https://github.com/tigrisdata/cli/releases/latest/download/install.ps1 | iexRemove-Item -Recurse -Force "$HOME\.tigris\bin"Remove PATH entry (run in PowerShell as Administrator):
$installDir = "$HOME\.tigris\bin"
$userPath = [Environment]::GetEnvironmentVariable("Path", "User")
$newPath = ($userPath -split ';' | Where-Object { $_ -ne $installDir }) -join ';'
[Environment]::SetEnvironmentVariable("Path", $newPath, "User")After installation, verify it works:
tigris --version
tigris helpYou can also use t3 as a shorthand:
t3 --versionAfter installation, authenticate with your Tigris account:
# Interactive login via browser (recommended)
tigris login
# Or use access key credentials directly
tigris configure --access-key <key> --access-secret <secret>Verify your authentication:
tigris whoamiSee AUTHENTICATION.md for all supported authentication methods including environment variables and AWS profiles.
For more information, visit the documentation.