Skip to main content
All install paths produce the same openlit binary. Pick the one that matches your OS.

Install locations & PATH

The CLI binary must be on $PATH for the vendor plugin installs to work. The openlit coding install command rewrites the openlit token in each generated hook manifest to the absolute path of the running binary, which sidesteps the minimal PATH that GUI-launched agents (like Cursor) inherit - but the binary still has to be found at install time.

Linux/macOS script options

The install.sh script downloads the matching tarball from the latest cli-*.*.* GitHub Release of openlit/openlit, verifies its .sha256 sidecar (best-effort), and installs to ~/.openlit/bin/openlit. It detects your OS (macOS, Linux) and architecture (amd64, arm64).

Build from source

If you have the repository checked out and Go installed, build a local binary:
This builds with go build -trimpath -ldflags "-s -w" from cli/cmd/openlit and installs to ~/.openlit/bin/openlit.

Verify the install

Uninstall

The openlit binary is never touched by openlit coding uninstall (which only removes vendor plugin manifests). Remove the binary the way you installed it:
On Windows, run the uninstall script:

Next steps

Configuration

Point the CLI at your OpenLIT collector

Wire your coding agents

Claude Code, Cursor, and Codex in under a minute