weave
Install

Get weave on your machine

One command on macOS, Linux, or Windows. The installer is the same bootstrap pattern as uv, rustup, and Bun.

One-liner

irm https://weavewhatever.com/install.ps1 | iex

That's it. Open a new shell and run weave --help.

What the installer actually does

  1. Checks that Python 3.11+ is available on your system.
  2. Bootstraps uv if you don't already have it.
  3. Runs uv tool install git+<repo>, which creates an isolated virtualenv and shims the weave binary into ~/.local/bin (macOS / Linux) or %USERPROFILE%\.local\bin (Windows).
  4. Prints next steps and surfaces any PATH adjustments needed.
No sudo. weave installs entirely under your home directory — no system-wide changes, no admin prompts, no global Python pollution.

Other ways to install

With uv directly

If you already use uv, skip the wrapper script: 

uv tool install git+https://github.com/andy-broyles/weavewhatever.git

With pipx

Prefer pipx? It works just as well: 

pipx install git+https://github.com/andy-broyles/weavewhatever.git

From source

For contributors or local hacking: 

git clone https://github.com/andy-broyles/weavewhatever.git
cd weavewhatever
uv sync --dev
uv pip install -e .

Pin a version

The installer reads WEAVE_REPO and WEAVE_REF (or WEAVE_VERSION) from the environment. With no pin, it installs the latest release tag when one exists, otherwise main. 

# macOS / Linux — install v0.2.0 (tag v0.2.0)
curl -fsSL https://weavewhatever.com/install.sh | WEAVE_VERSION=0.2.0 bash

# Windows — same release
$env:WEAVE_VERSION = "0.2.0"; irm https://weavewhatever.com/install.ps1 | iex

# Or pin an explicit ref (branch, tag, SHA)
curl -fsSL https://weavewhatever.com/install.sh | WEAVE_REF=v0.2.0 bash

Use WEAVE_REPO if you've forked weave or you mirror it internally.

Upgrade & uninstall

Both are one liners through uv:

# upgrade to latest main
uv tool upgrade weave

# remove cleanly
uv tool uninstall weave

First run

weave does not bundle a secrets manager. After install:

  1. weave setup — pick your first module and how you inject API keys (weave init is the same)
  2. Inject env vars (export, .env, or your team's wrapper — not tied to one vendor)
  3. weave secrets check then your first weave <module> command

Full walkthrough: Getting started · Secrets backends

Don't trust me, read the script

Piping the internet to a shell is a fine habit once you've read what's in the pipe. Both scripts are short, MIT-licensed, and live in this repo:

Or download and inspect before running: 

curl -fsSL https://weavewhatever.com/install.sh -o install.sh
less install.sh
bash install.sh