01Install it
On macOS or Linux, one command puts the runner on your PATH:
curl https://crewbit.sh/install | bash. It works out your machine
(Apple Silicon, Intel, or Linux x64), downloads the matching binary from the latest
release, and tells you where it put it.
A file curl downloads carries none of the quarantine mark a browser
attaches, so this also sidesteps the "is damaged and can't be opened" warning macOS
shows a binary downloaded the other way: nothing to clear by hand first.
crewbit --version confirms it: the script runs it once and prints what it
printed.
02Or, download it by hand
If you would rather see the file before you run it, go to the
latest
release and download the binary for your machine (crewbit-macos-arm64
for Apple Silicon, crewbit-macos-x64 for Intel) or crewbit-linux-x64.
The download needs no account and no sign-in: the release is public, and it ships with
the binaries and the runner's own changelog.
Downloaded this way, the binary does carry the quarantine mark, and macOS refuses to run
it (in the Finder or in a terminal) with "is damaged and can't be opened", the same
message an unsigned download gets whether or not anything is actually wrong with the
file. In a terminal, in the folder you downloaded it to, clear the mark and make it
executable: xattr -d com.apple.quarantine crewbit-macos-arm64 &&
chmod +x crewbit-macos-arm64. ./crewbit-macos-arm64 --version now
prints the version number and exits, in the Finder and the terminal alike. Move it
somewhere on your PATH yourself: the script above is what does that step for you.
03Mint a token
Once you are signed in, open /runners and click "Mint a token". Give it a
name (the machine's hostname is a reasonable one) and copy the secret it shows you.
It is shown once; there is no way to see it again after you leave the page, only to mint
a new one.
04Connect it
On the machine that has Claude Code installed, run crewbit runner --token <the secret
you copied> --slots 1. It connects to Crewbit's socket by default (nothing
else to configure) and sits waiting for work.
Back on /runners, the token's row gains a "live" badge, and a card appears
for the connection itself: the machine's id, an "idle" badge, and "Holding nothing.
Ready for the next Job." That card is what tells you the runner is actually reachable,
not just that a token exists.
--slots is how many Jobs it runs at once. One is the right number until you
have a reason to raise it.