Install

Three ways to get a binary that does not exist.

Wren ships as one static binary, which is easy to promise for a tool nobody has written.

Pick a channel

curl -fsSL https://example.invalid/install.sh | sh

cargo install wren --locked

The --locked matters: it builds against the lockfile in the published crate rather than resolving fresh dependencies, so two people on the same version get the same binary.

brew install example/tap/wren

Then 2 min

Put the binary on your PATH.
Check that the shell can see it:
```
wren --version
```
Start a site:
```
wren init my-site
```

If that prints nothing

The binary is not on your PATH, which is the usual answer and rarely the interesting one.

Edit this pageLast updated 2026-08-12