Install Temper
temper CLI on their own machine, against ahosted or self-hosted deployment.
temper binary installed and on your PATH,ready to run
temper init and connect to an instance. No Rust toolchain, no system packagemanager, no homebrew tap is required.
Prerequisites
other platforms (Linux arm64, Intel Mac, Windows arm64), see
Building from source below.
you are standing it up yourself, see Self-host Temper.
Quick install
macOS and Linux
curl -fsSL https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.sh | shWindows (PowerShell)
irm https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.ps1 | iexHomebrew (macOS Apple Silicon, Linux x64)
tasker-systems tap— one formula per minor, mirroring the wire-contract pins, so a deploy base can hold a
fleet on a minor the same way a client pins a contract:
brew install tasker-systems/tap/temper@0.6 # pinned to the 0.6 wire contractupgrading) by the full versioned name grants that trust for the one formula, so the
line above needs no
brew trust step.temper alias — always the current minor — is the exception: Homebrew trusts aformula named in full, and an alias is not one, so the alias refuses until its target is
trusted. Trust the tap once and the alias keeps working as it moves between minors:
brew trust tasker-systems/tap # once — covers every formula, and the alias
brew install tasker-systems/tap/temper # alias — always the current minortrusted: true has brew bundle grant the trust,so an unattended run does not stop on it:
0.5.1 → 0.5.2) update the formula in place; brew upgrade carries them.Within a minor the wire contract is additive-only, so an upgrade never strands you.
temper@0.7); moving to it is a deliberateBrewfile edit, at your cadence. Trust is per formula, so install the new one by its full
name (or carry
trusted: true on the new Brewfile line).temper update refuses on a brew install — the install carries a BREW-MANAGEDmarker, and
brew upgrade is the only updater there. temper update --check stillreports what's newer.
at
/opt/homebrew/bin/temper, the script at ~/.local/bin/temper); PATH order decideswhich one runs, and the curl installer warns when a brew-managed temper is already on
your PATH.
temper version --verify works identically on both.irm https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.ps1 | iexIf PowerShell warns about the execution policy, run: powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.ps1 | iex"
What the installer does
1.
2.
3.
.tar.gz on macOS/Linux, .zip on Windows) plus itsSHA256 checksum file.
4.
5.
file (
temper, the bundled libonnxruntime, LICENSE) against it. A mismatch abortsbefore your existing install is touched. See
Release Verification for what this check does and
does not prove.
6.
~/.local/share/temper/ (respects $XDG_DATA_HOME)%LOCALAPPDATA%\Programs\temper\7.
temper entry on your PATH:~/.local/bin/temper → the extracted binarytemper[.exe], a bundled libonnxruntime for the CLI's localembedding pipeline (the CLI embeds locally by default —
embed and extract are itsdefault features, so ingestion posts pre-chunked, pre-embedded text rather than relying
on the server), and a copy of the
project
LICENSE.Pinning to a specific version
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.sh | sh -s -- --version v0.1.0# Windows
$script = irm https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.ps1
& ([scriptblock]::Create($script)) -Version v0.1.0Don't want to pipe to sh?
curl -fsSL -o /tmp/install-temper.sh https://raw.githubusercontent.com/tasker-systems/temper/main/scripts/install/install.sh
less /tmp/install-temper.sh # inspect
sh /tmp/install-temper.sh # rungithub.com/tasker-systems/temper/releases
and unpack it wherever you like.
Upgrading
temper updatetemper update verifies the release before installing and works for curl-script installs onmacOS/Linux. A brew install is not self-updating —
temper update refuses there, andbrew upgrade tasker-systems/tap/temper@<minor> is the updater (see the Homebrew sectionabove). For the verification
temper update performs, seeRelease Verification; for the full flag reference, see
temper update.Uninstalling
macOS / Linux
rm -rf "${XDG_DATA_HOME:-$HOME/.local/share}/temper"
rm -f "${XDG_BIN_HOME:-$HOME/.local/bin}/temper"Windows
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Programs\temper"
# Then manually remove the install dir from your user PATH via:
# rundll32.exe sysdm.cpl,EditEnvironmentVariablesBuilding from source
or you want a custom build, clone the repo and
cargo install:git clone https://github.com/tasker-systems/temper
cd temper
cargo install --path crates/temper-cli --locked --features embed,extractbrew install onnxruntime suffices.Troubleshooting
"temper: command not found" after install (macOS/Linux)
~/.local/bin. Add it:# bash
echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.bashrc
# zsh
echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.zshrc
# fish
fish_add_path ~/.local/binWindows: "temper : The term 'temper' is not recognized"
so the updated user PATH propagates.
Windows: SmartScreen warning
temper.exe binary is currently unsigned. On first run, you may see a SmartScreen"Windows protected your PC" dialog. Click More info → Run anyway.
ONNX Runtime not found
libonnxruntime next to the temper binary for the embeddingpipeline. If you see a library-load error, file an issue at
https://github.com/tasker-systems/temper/issues with the output of:
temper --version
ls -la ~/.local/share/temper/ # macOS / Linux
dir %LOCALAPPDATA%\Programs\temper # WindowsNext: initialize the CLI
temper --help, but the command you actually wantnext is
temper init — it writes your config and points the CLI at an instance:temper initself-hosted deployment. Then continue with Authenticate to sign in and
request access.
Further reading
Release Verification.
The Trust Boundary.
Contexts and Refs.
Modified at 2026-11-15 01:09:09