Trill

Installation

Trill is a single statically-compiled binary. The same binary runs workflows on your laptop, and — with a runner token from app.trill.build — connects as a runner agent that claims jobs from the hosted service.

Download

Download the latest Linux amd64 binary:

curl -LO https://dl.trill.build/linux/amd64/trill
chmod +x trill
sudo mv trill /usr/local/bin/

Verifying the download

Each binary ships with a .sha256 checksum. Verify before running:

curl -LO https://dl.trill.build/linux/amd64/trill
curl -LO https://dl.trill.build/linux/amd64/trill.sha256
sha256sum -c trill.sha256

Pinning to a specific build

Every build is also published at an immutable path under its content hash, useful for reproducible CI setups:

curl -LO https://dl.trill.build/b3/<hash>/linux/amd64/trill

Verify

trill --version

Running an agent

If you want jobs from trill.build to execute on your own hardware — your laptop, a home server, a VM — run the agent with a runner token from the Settings page at app.trill.build:

trill agent --server https://app.trill.build --token trl_<runner-token>

The agent registers with the service, polls for jobs, executes them locally, and reports results back. You can run as many agents as you need — jobs are distributed across all connected runners in your organization.

Agent flags

FlagEnv varDescription
--server <URL>TRILL_SERVERTrill service URL
--token <token>TRILL_TOKENRunner token (trl_...)
--name <name>—Runner name as it appears in the dashboard (defaults to hostname)
--workspace-dir <path>TRILL_WORKSPACE_DIRRoot directory for per-job workspaces (default: ~/.trill/workspaces)
--keep-workspaces—Don’t clean up job workspaces after completion — useful for debugging

Every flag can be set via environment variable, so a systemd unit or Docker container config is just:

TRILL_SERVER=https://app.trill.build \
TRILL_TOKEN=trl_... \
TRILL_WORKSPACE_DIR=/var/lib/trill/workspaces \
trill agent

Next Steps