weave
Getting started

Your first live command in 5 steps

One path from install to a working command. weave reads API keys from environment variables in the same shell — set them during setup, then run the command weave prints at the end.

  1. 1

    Install weave

    One command. The installer adds weave to your PATH. 

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

    The installer ends with: Next step (required): weave setup (weave init is the same command).

  2. 2

    Run guided setup

    Pick the first system you want to connect and how your team usually loads API keys. Setup writes your setup file so weave only checks what you use. 

    weave setup

    Already ran setup? Run weave setup again and choose Continue setup or Show status. Bare weave also nudges you if credentials are still missing.

  3. 3

    Set credentials in this shell

    Setup prints the exact variable names and copy-paste lines for your OS (PowerShell $env:VAR on Windows, export on macOS/Linux). 

    weave secrets check

    Use 1Password, Vault, Doppler, a .env file, or plain export — weave only needs vars in the process that runs weave …. Secrets backends has per-tool recipes.

  4. 4

    See where files live

    Setup can save snapshots under the project .weave-state or a custom path in config.toml. Override anytime with WEAVE_STATE_DIR. 

    weave config path
  5. 5

    List, then snapshot

    When credentials are set, setup prints a Prove it works section with list and snapshot commands, plus the boxed Next: run this line. 

    weave doctor --missing-only
weave okta list users
weave okta snapshot users   # prints Saved: <absolute path>
weave okta diff users       # review before any apply
weave okta apply users --yes  # after you trust the diff

    Add more systems later: weave enable mosyle meraki. Full catalog: weave modules --all.

Troubleshooting

When auth fails, work through this list:

  • ☐ Vars set in this shell? (weave secrets check)
  • ☐ Module in your setup file? weave setup → Continue setup
  • ☐ Corporate proxy or firewall blocking the vendor API
  • ☐ Token expired or read-only — rotate in the vendor console

From source (optional)

For contributors, or if you want the tree checked out locally: 

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

Where to next

Secrets backends
Per-backend recipes (1P, Vault, Doppler, CI, …).
CLI reference
Every command, flag, and exit code.
Modules
Browse the live integrations and roadmap.